ADSM-L

[ADSM-L] FW: [ADSM-L] DR of a VmWare logical server question

2007-04-11 18:55:21
Subject: [ADSM-L] FW: [ADSM-L] DR of a VmWare logical server question
From: Kelly Lipp <lipp AT STORSERVER DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 11 Apr 2007 15:29:41 -0600
More from my much smarter than me wife!  Sorry about the relay
confusion!
 
Kelly J. Lipp
VP Manufacturing & CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
lipp AT storserver DOT com
 

________________________________

From: Laura Buckley 
Sent: Wednesday, April 11, 2007 3:28 PM
To: Kelly Lipp
Subject: RE: [ADSM-L] FW: [ADSM-L] DR of a VmWare logical server
question



Restoring the system object after restoring the data is sort of out of
order.  I think you could try using the Windows GUI and do the
following:

 

>From the GUI mainscreen on cgotst32b

Pull down utilities

Access another node

Enter cgotst32

Then click restore, and see if you can restore the system object 

 

BUT REALLY - 

 

If it is your desire to bring the entire VM back, I would suggest that
you use take advantage of VMware's inherent portability.  Since the
entire machine is stored in one big image file you could: 

 

a) Install the baclient on the VMware virtualization layer (either Linux
or Windows client) and backup the entire VM (.vmdk) and then restore
that to any VMware host for a really fast BMR.

 

Or 

 

b) follow the same procedure for a bare machine recovery that you would
for any TSM windows client:

 

 

The basic procedure:

Repair or replace the failing hardware.

Reinstall basic operating system support.

Reinstall network connectivity to the TSM server.

Reinstall the TSM client.

Restore, via TSM, the boot and system objects.

Reboot the system.

Restore, via TSM, any non-system data.

 

 

 

Checkout this technote for good details

 

http://www-1.ibm.com/support/docview.wss?uid=swg21164812

 

 

 

 

 

Laura Buckley

 

Vice President, Product Development

 

STORServer, Inc.

 

719-266-8777

 

719-238-5237cell

 

buckley AT storserver DOT com

 

 

-----Original Message-----

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Lamb, Charles P.

Sent: Wednesday, April 11, 2007 1:54 PM

To: ADSM-L AT VM.MARIST DOT EDU

Subject: Re: [ADSM-L] FW: [ADSM-L] DR of a VmWare logical server
question

 

Kelly & Laura.....

 

OK.  That worked. Step #1 thru 10 using restore command -- restore

-fromnode=cgotst32 \\cgotst32\c$\* c:\ -replace=all -subdir=yes  

 

How do you restore systemservices and systemstate from cgotst32 to
cgotst32b??

 

-----Original Message-----

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Kelly Lipp

Sent: Wednesday, April 11, 2007 2:01 PM

To: ADSM-L AT VM.MARIST DOT EDU

Subject: [ADSM-L] FW: [ADSM-L] DR of a VmWare logical server question

 

Laura Buckley has some ideas to solve this one...

 

Give this a try and report back...

 

Kelly J. Lipp

VP Manufacturing & CTO

STORServer, Inc.

485-B Elkton Drive

Colorado Springs, CO 80907

719-266-8777

lipp AT storserver DOT com

 

 

________________________________

 

From: Laura Buckley

Sent: Wednesday, April 11, 2007 11:54 AM

To: Kelly Lipp

Subject: RE: [ADSM-L] DR of a VmWare logical server question

 

 

 

Sounds like maybe he didn't set access on cgotst32 for cgotst32b.  

 

 

 

You have to do the following steps on cgotst32b

 

 

 

To authorize another node to restore or retrieve your files:

 

 

 

1. Click Utilities -> Node Access List from the main window. The Node

Access List window appears. 

 

2. Click the Add button. The Add Access Rule window appears. 

 

3. In the Add Access Rule window, select an item in the Permit Access to

field to specify the type of data that the other user can access. You

can select either Backed up Objects or Archived Objects. 

 

4. Type the node name of the user in the Grant Access to Node field.

Type the node name of the user's host machine in the Grant Access to

Node field. 

 

5. Type the name of a user on the host machine in the User field. 

 

6. In the Filespace and Directory field, select the file space and the

directory that the user can access. You can select one file space and

one directory at a time. If you want to give the user access to another

file space or directory, you must create another access rule. 

 

7. If you want to limit the user to specific files in the directory,

type the name or pattern of the files on the server that the other user

can access in the Filename field. You can make only one entry in the

Filename field. It can either be a single file name or a pattern which

matches one or more files. You can use a wildcard character as part of

the pattern. Your entry must match files that have been stored on the

server. 

 

8. If you want to give access to all files that match the file name

specification within the selected directory including its

subdirectories, click Include subdirectories 

 

9. Click the OK button to save the access rule and close the Add Access

Rule window. 

 

10.  The access rule that you created is displayed in the list box in

the Node Access List window. When you have finished working with the

Node Access List window, click the OK button. If you do not want to save

your changes, click Cancel or close the window.

 

 

 

Then to do the restore on cgotst32b

 

 

 

If you are using commands, use the fromnode option to indicate the node.

You must also use the file space name, rather than the drive letter, to

select the restore-retrieve drive you want to access. Include the file

space name in braces and use it like a drive letter. For example, to

restore cougar's files from the \projx directory on the d-disk file

space to your own \projx directory, enter: 

 

 

 

  dsmc restore -fromnode=cougar  \\cougar\d$\projx\* d:\projx\

 

 

 

Use the query filespace command to display a list of file spaces. For

example, to display a list of cougar's file spaces, enter: 

 

 

 

   dsmc query filespace -fromnode=cougar

 

 

 

 

 

 

 

-----Original Message-----

From: Kelly Lipp 

Sent: Wednesday, April 11, 2007 11:37 AM

To: Laura Buckley

Subject: FW: [ADSM-L] DR of a VmWare logical server question

 

 

 

Some folks struggling with this! 

 

 

 

 

 

Kelly J. Lipp

 

VP Manufacturing & CTO

 

STORServer, Inc.

 

485-B Elkton Drive

 

Colorado Springs, CO 80907

 

719-266-8777

 

lipp AT storserver DOT com

 

 

 

-----Original Message-----

 

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of

Lamb, Charles P.

 

Sent: Wednesday, April 11, 2007 10:32 AM

 

To: ADSM-L AT VM.MARIST DOT EDU

 

Subject: [ADSM-L] DR of a VmWare logical server question

 

 

 

Hi...........

 

 

 

I am having problems with restoring a VmWare logical server (cgotst32)

to another VmWare logical server (cgotst32b).  It just will not restore.

 

Any help from the TSM group which is smarter then myself??

 

 

 

TSM server v5.2.7.3

 

TSM client V5.4.0.2

 

MS W2K3 R2 VmWare logical server

 

 

 

I changed TSM password on cgotst32 to allow cgotst32b to see everything.

 

I have been running the TSM scheduler on cgotst32 for many days. Q f

shows the information I need for restoring cgotst32 onto cgotst32b.

 

 

 

We used the restore command  -- restore -fromnaode=cgotst32

 

\\cgotst32\c$\* -replace=all -subdir=yes

 

 

 

We keep on receiving user action required message ---  File

'\\cgotst32\c$\' is write protected.  We select option#2 to force an

overwrite on all objects that are write protected, however, we just

receive the user action required message over, over and over with

nothing happens??

 

 

 

Thoughts on restoring a VmWare logical server??

<Prev in Thread] Current Thread [Next in Thread>