Thanks. I would have thought there would be a simpler way to retrieve it on
the target server.
----- Original Message -----
From: "William Boyer" <bjdboyer AT COMCAST DOT NET>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Thursday, September 27, 2007 9:16 AM
Subject: Re: [ADSM-L] DR restore of a virtual volume

You would rebuild the ServerA instance with a blank database of the same
size or larger as what ServerA had originally. Then you
would define the server-to-server communication to ServerB. Once that's
done, shutdown ServerA. All the configuration information is
now in the DEVCONFIG file(s). Now you can run the

Dsmserv restore db devclass=<serve-to-server device class>
volumes=<virtual volume name(s)> commit=yes

Your DRM prepare plan should have all the information you need, if you're
using DRM.

Bill Boyer
"Backup my harddrive? How do I put it in reverse?" - ??


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Larry Clark
Sent: Thursday, September 27, 2007 8:56 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: DR restore of a virtual volume

ServerA backups up the TSM DB to a virtual volume on ServerB.

ServerA is lost and the TSM DB on the virtual volume on ServerB is
required to recreate it.

How is that virtual volume restored?