Re: Disaster Recovery

[Richard Sims]

On Jun 21, 2009, at 2:26 AM, madunix wrote:


Can I have please more input about implementing DRM in TSM?


See the prevailing information:

- TSM Admin Guide chapter "Using Disaster Recovery Manager"
- At http://www.redbooks.ibm.com/ search on   disaster recovery
- A wealth of past postings on this subject at 
http://www.mail-archive.com/adsm-l@vm.marist.edu/

Re: Disaster Recovery

[madunix]

Can I have please more input about implementing DRM in TSM?

madunix

On Thu, Jun 18, 2009 at 3:17 PM, madunix wrote:
> I would like to know exact steps on how to take a client data backup
> from the main site and restore it at the DR site using Tivoli Storage
> Manager TSM.
>
> madunix
>
>
> On Thu, Jun 18, 2009 at 1:07 PM, Costa, Justino 
> wrote:
>> I think this document will help you: "Disaster Recovery Strategies with
>> Tivoli Storage Management" ->
>> http://www.redbooks.ibm.com/abstracts/sg246844.html
>>
>> jmC
>>
>>
>>
>> -Original Message-
>> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
>> madunix
>> Sent: quinta-feira, 18 de Junho de 2009 10:38
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: [ADSM-L] Disaster Recovery
>>
>> I have multiple servers (10 servers, running DB with WEB
>> application)located in the production site. I want to transfer the data
>> of these servers from main site to Disaster recovery site, i have
>> alocated in the DR site also the same servers and same library.To do
>> this I have started to look at collocation inside the TSM to update
>> servers in different location. so incase if we need to swap any server
>> in site A to Site B, The best way I found is to export the latest TSM
>> backup directly, by use the "export node node name filedata=all
>> tos=newserver" command, to update the server with actual data, the boxes
>> are located on different network, for the import and export I use the
>> network,  in our calculation 1G = 1hour (time import/export) to
>> back/move/restore the data on different location,as you know by
>> importing/exporting huge data it will take a lot of time.
>>
>> What would be your recommendation to transfer 20GB for different servers
>> from Site A to Site B?
>>
>> Any input would be really appreciated.
>>
>> madunix
>>
>>
>> Please help Logica to respect the environment by not printing this email  / 
>> Pour contribuer comme Logica au respect de l'environnement, merci de ne pas 
>> imprimer ce mail /  Bitte drucken Sie diese Nachricht nicht aus und helfen 
>> Sie so Logica dabei die Umwelt zu schuetzen  /  Por favor ajude a Logica a 
>> respeitar o ambiente nao imprimindo este correio electronico.
>>
>>
>>
>> This e-mail and any attachment is for authorised use by the intended 
>> recipient(s) only. It may contain proprietary material, confidential 
>> information and/or be subject to legal privilege. It should not be copied, 
>> disclosed to, retained or used by, any other party. If you are not an 
>> intended recipient then please promptly delete this e-mail and any 
>> attachment and all copies and inform the sender. Thank you.
>>
>

Re: Disaster Recovery

[madunix]

I would like to know exact steps on how to take a client data backup
from the main site and restore it at the DR site using Tivoli Storage
Manager TSM.

madunix


On Thu, Jun 18, 2009 at 1:07 PM, Costa, Justino wrote:
> I think this document will help you: "Disaster Recovery Strategies with
> Tivoli Storage Management" ->
> http://www.redbooks.ibm.com/abstracts/sg246844.html
>
> jmC
>
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> madunix
> Sent: quinta-feira, 18 de Junho de 2009 10:38
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Disaster Recovery
>
> I have multiple servers (10 servers, running DB with WEB
> application)located in the production site. I want to transfer the data
> of these servers from main site to Disaster recovery site, i have
> alocated in the DR site also the same servers and same library.To do
> this I have started to look at collocation inside the TSM to update
> servers in different location. so incase if we need to swap any server
> in site A to Site B, The best way I found is to export the latest TSM
> backup directly, by use the "export node node name filedata=all
> tos=newserver" command, to update the server with actual data, the boxes
> are located on different network, for the import and export I use the
> network,  in our calculation 1G = 1hour (time import/export) to
> back/move/restore the data on different location,as you know by
> importing/exporting huge data it will take a lot of time.
>
> What would be your recommendation to transfer 20GB for different servers
> from Site A to Site B?
>
> Any input would be really appreciated.
>
> madunix
>
>
> Please help Logica to respect the environment by not printing this email  / 
> Pour contribuer comme Logica au respect de l'environnement, merci de ne pas 
> imprimer ce mail /  Bitte drucken Sie diese Nachricht nicht aus und helfen 
> Sie so Logica dabei die Umwelt zu schuetzen  /  Por favor ajude a Logica a 
> respeitar o ambiente nao imprimindo este correio electronico.
>
>
>
> This e-mail and any attachment is for authorised use by the intended 
> recipient(s) only. It may contain proprietary material, confidential 
> information and/or be subject to legal privilege. It should not be copied, 
> disclosed to, retained or used by, any other party. If you are not an 
> intended recipient then please promptly delete this e-mail and any attachment 
> and all copies and inform the sender. Thank you.
>

Re: Disaster Recovery

[Costa, Justino]

I think this document will help you: "Disaster Recovery Strategies with
Tivoli Storage Management" ->
http://www.redbooks.ibm.com/abstracts/sg246844.html

jmC



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
madunix
Sent: quinta-feira, 18 de Junho de 2009 10:38
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Disaster Recovery

I have multiple servers (10 servers, running DB with WEB
application)located in the production site. I want to transfer the data
of these servers from main site to Disaster recovery site, i have
alocated in the DR site also the same servers and same library.To do
this I have started to look at collocation inside the TSM to update
servers in different location. so incase if we need to swap any server
in site A to Site B, The best way I found is to export the latest TSM
backup directly, by use the "export node node name filedata=all
tos=newserver" command, to update the server with actual data, the boxes
are located on different network, for the import and export I use the
network,  in our calculation 1G = 1hour (time import/export) to
back/move/restore the data on different location,as you know by
importing/exporting huge data it will take a lot of time.

What would be your recommendation to transfer 20GB for different servers
from Site A to Site B?

Any input would be really appreciated.

madunix


Please help Logica to respect the environment by not printing this email  / 
Pour contribuer comme Logica au respect de l'environnement, merci de ne pas 
imprimer ce mail /  Bitte drucken Sie diese Nachricht nicht aus und helfen Sie 
so Logica dabei die Umwelt zu schuetzen  /  Por favor ajude a Logica a 
respeitar o ambiente nao imprimindo este correio electronico.



This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.

Re: Disaster recovery of Windows 2003 Server

[Prather, Wanda]

That information is also included now in the current Windows Client 
installation and use manual, and is a little more current I think - search on 
ASR.



From: ADSM: Dist Stor Manager on behalf of Henrik Wahlstedt
Sent: Mon 3/13/2006 9:58 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Disaster recovery of Windows 2003 Server



There is a Redpapper called "IBM Tivoli Storage Manager: Bare Machine
Recovery for Microsoft Windows 2003 and XP". Search on the Redbooks.

//Henrik

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Doyle, Patrick
Sent: den 13 mars 2006 15:17
To: ADSM-L@VM.MARIST.EDU
Subject: Disaster recovery of Windows 2003 Server

Has there been any updates to the disaster recovery documents for 2003
server?

The following refer to Windows 2000 only,

Disaster Recovery Strategies with Tivoli Storage Management
http://www.redbooks.ibm.com/redbooks/pdfs/sg246844.pdf

Summary BMR Procedures for Windows NT and Windows 2000 with ITSM
http://www.redbooks.ibm.com/abstracts/tips0102.html?Open


In particular, references to "dsmc restore systemobject" seem to be
obsolete. TSM Client 5.3.2.0 now sees "system services" and "system
state" as replacements for "systemobject".

Is anyone aware of an update?

Regatds,
Pat.


Zurich Insurance Ireland Limited t/a Eagle Star is regulated by the
Financial Regulator
**
The contents of this e-mail and possible associated attachments are for
the addressee only. The integrity of this non-encrypted message cannot
be guaranteed on the internet.
Zurich Insurance Ireland Limited t/a Eagle Star is therefore not
responsible for the contents. If you are not the intended recipient,
please delete this e-mail and notify the sender
**


---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

Re: Disaster recovery of Windows 2003 Server

[Henrik Wahlstedt]

There is a Redpapper called "IBM Tivoli Storage Manager: Bare Machine
Recovery for Microsoft Windows 2003 and XP". Search on the Redbooks.

//Henrik

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Doyle, Patrick
Sent: den 13 mars 2006 15:17
To: ADSM-L@VM.MARIST.EDU
Subject: Disaster recovery of Windows 2003 Server

Has there been any updates to the disaster recovery documents for 2003
server?

The following refer to Windows 2000 only,

Disaster Recovery Strategies with Tivoli Storage Management
http://www.redbooks.ibm.com/redbooks/pdfs/sg246844.pdf

Summary BMR Procedures for Windows NT and Windows 2000 with ITSM
http://www.redbooks.ibm.com/abstracts/tips0102.html?Open


In particular, references to "dsmc restore systemobject" seem to be
obsolete. TSM Client 5.3.2.0 now sees "system services" and "system
state" as replacements for "systemobject".

Is anyone aware of an update?

Regatds,
Pat.


Zurich Insurance Ireland Limited t/a Eagle Star is regulated by the
Financial Regulator
**
The contents of this e-mail and possible associated attachments are for
the addressee only. The integrity of this non-encrypted message cannot
be guaranteed on the internet.
Zurich Insurance Ireland Limited t/a Eagle Star is therefore not
responsible for the contents. If you are not the intended recipient,
please delete this e-mail and notify the sender
**


---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

Re: disaster recovery drill: emergency!!!

[Kauffman, Tom]

Let us know how everything works out!

I get to re-confirm my process next week.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 9:31 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: disaster recovery drill: emergency!!!

Hi Tom,

Thanks very much!  I'm going to try it tomorrow morning at disaster
recovery.  : )


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>
To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor
cc
 Manager"
 <[EMAIL PROTECTED]
Subject
     .EDU> Re: disaster recovery drill:
   emergency!!!

 03/07/2005 05:37
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






All I can say is -- this works. TSM 5.1.6.3, actual library is a 3584
with 10 drives (becomes a 3584 with 6 drives at our hot-site, per
contract) We've run this config for three successful recoveries. (And we
may not even need the path definition for the library, but it doesn't
seem to hurt).

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 5:21 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: disaster recovery drill: emergency!!!

Hi Tom,

I'm just wondering how you have a manual library and then have a path
with
desttype=library instead of desttype=drive?  And also, can I just update
my
lto2_offsite device class to point to my drlib manual library definition
since that is what will be asking for the tape mounts?  Thanks again!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>
To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor
cc
 Manager"
     <[EMAIL PROTECTED]
Subject
 .EDU> Re: disaster recovery drill:
   emergency!!!

 03/07/2005 05:09
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






Your 'define drive' commands need to reference the library they're in;
FWIW, here's mine:

DEFINE DEVCLASS NIBLTO DEVTYPE=LTO FORMAT=DRIVE MOUNTLIMIT=DRIVES
MOUNTWAIT=60 MOUNTRETENTION=60 PREFIX=ADSM LIBRARY=ALEX
SET SERVERNAME ADSM
DEFINE LIBRARY ALEX LIBTYPE=MANUAL
DEFINE DRIVE ALEX DRIVE_01 ONLINE=Yes
DEFINE PATH ADSM ALEX SRCTYPE=SERVER DESTTYPE=LIBRARY ONLINE=YES
DEFINE PATH ADSM DRIVE_01 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=ALEX
DEVICE=/dev/rmtX ONLINE=YES

And the 'define path' for the drive is all one line. I've actually got
this set up as my D/R device config file that I load from floppy just
before the database restore. Saves editing on-site.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 4:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: disaster recovery drill: emergency!!!

Hi Tom,

Gotcha!  So I guess my devconfig file could look like this.  And then
when
it's up and it has restored the TSM server it will have the identical
definitions as I have at home and then I will just define more manual
drives, the paths to the drives and move from there?  If I leave the
other
definitions there after the TSM DB restore, will conflicts occur?  Thank
you again!

  DEFINE DEVCLASS DR_LTO2 DEVTYPE=LTO FORMAT=ULTRIUM2C
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=60
  MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=DRLIB
  DEFINE DEVCLASS NASDEV DEVTYPE=NAS FORMAT=DRIVE
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=180
  MOUNTRETENTION=0 PREFIX=ADSM LIBRARY=DRLIB
  SET SERVERNAME TSMPROD
  SET SERVERPASSWORD 1829fecd5fecda74
  DEFINE LIBRARY DRLIB LIBTYPE=MANUAL
  DEFINE DRIVE LTO1
  DEFINE DRIVE LTO6
  DEFINE PATH TSMPROD LTO1 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=DRLIB
  DEVICE=/DEV/RMT#
  DEFINE PATH NAS_SERVER_2 LTO6 SRCTYPE=DATAMOVER DESTTYPE=DRIVE
  LIBRARY=DRLIB DEVICE=C64T0LO





Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




   

Re: disaster recovery drill: emergency!!!

[Joni Moyer]

Hi Tom,

Thanks very much!  I'm going to try it tomorrow morning at disaster
recovery.  : )


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>   To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager"
 <[EMAIL PROTECTED] Subject
     .EDU> Re: disaster recovery drill:
   emergency!!!

 03/07/2005 05:37
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






All I can say is -- this works. TSM 5.1.6.3, actual library is a 3584
with 10 drives (becomes a 3584 with 6 drives at our hot-site, per
contract) We've run this config for three successful recoveries. (And we
may not even need the path definition for the library, but it doesn't
seem to hurt).

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 5:21 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: disaster recovery drill: emergency!!!

Hi Tom,

I'm just wondering how you have a manual library and then have a path
with
desttype=library instead of desttype=drive?  And also, can I just update
my
lto2_offsite device class to point to my drlib manual library definition
since that is what will be asking for the tape mounts?  Thanks again!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>
To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor
cc
 Manager"
     <[EMAIL PROTECTED]
Subject
 .EDU> Re: disaster recovery drill:
   emergency!!!

 03/07/2005 05:09
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






Your 'define drive' commands need to reference the library they're in;
FWIW, here's mine:

DEFINE DEVCLASS NIBLTO DEVTYPE=LTO FORMAT=DRIVE MOUNTLIMIT=DRIVES
MOUNTWAIT=60 MOUNTRETENTION=60 PREFIX=ADSM LIBRARY=ALEX
SET SERVERNAME ADSM
DEFINE LIBRARY ALEX LIBTYPE=MANUAL
DEFINE DRIVE ALEX DRIVE_01 ONLINE=Yes
DEFINE PATH ADSM ALEX SRCTYPE=SERVER DESTTYPE=LIBRARY ONLINE=YES
DEFINE PATH ADSM DRIVE_01 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=ALEX
DEVICE=/dev/rmtX ONLINE=YES

And the 'define path' for the drive is all one line. I've actually got
this set up as my D/R device config file that I load from floppy just
before the database restore. Saves editing on-site.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 4:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: disaster recovery drill: emergency!!!

Hi Tom,

Gotcha!  So I guess my devconfig file could look like this.  And then
when
it's up and it has restored the TSM server it will have the identical
definitions as I have at home and then I will just define more manual
drives, the paths to the drives and move from there?  If I leave the
other
definitions there after the TSM DB restore, will conflicts occur?  Thank
you again!

  DEFINE DEVCLASS DR_LTO2 DEVTYPE=LTO FORMAT=ULTRIUM2C
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=60
  MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=DRLIB
  DEFINE DEVCLASS NASDEV DEVTYPE=NAS FORMAT=DRIVE
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=180
  MOUNTRETENTION=0 PREFIX=ADSM LIBRARY=DRLIB
  SET SERVERNAME TSMPROD
  SET SERVERPASSWORD 1829fecd5fecda74
  DEFINE LIBRARY DRLIB LIBTYPE=MANUAL
  DEFINE DRIVE LTO1
  DEFINE DRIVE LTO6
  DEFINE PATH TSMPROD LTO1 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=DRLIB
  DEVICE=/DEV/RMT#
  DEFINE PATH NAS_SERVER_2 LTO6 SRCTYPE=DATAMOVER DESTTYPE=DRIVE
  LIBRARY=DRLIB DEVICE=C64T0LO





Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>
To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor
cc
 

Re: disaster recovery drill: emergency!!!

[Kauffman, Tom]

All I can say is -- this works. TSM 5.1.6.3, actual library is a 3584
with 10 drives (becomes a 3584 with 6 drives at our hot-site, per
contract) We've run this config for three successful recoveries. (And we
may not even need the path definition for the library, but it doesn't
seem to hurt).

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 5:21 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: disaster recovery drill: emergency!!!

Hi Tom,

I'm just wondering how you have a manual library and then have a path
with
desttype=library instead of desttype=drive?  And also, can I just update
my
lto2_offsite device class to point to my drlib manual library definition
since that is what will be asking for the tape mounts?  Thanks again!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>
To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor
cc
 Manager"
 <[EMAIL PROTECTED]
Subject
     .EDU> Re: disaster recovery drill:
   emergency!!!

 03/07/2005 05:09
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






Your 'define drive' commands need to reference the library they're in;
FWIW, here's mine:

DEFINE DEVCLASS NIBLTO DEVTYPE=LTO FORMAT=DRIVE MOUNTLIMIT=DRIVES
MOUNTWAIT=60 MOUNTRETENTION=60 PREFIX=ADSM LIBRARY=ALEX
SET SERVERNAME ADSM
DEFINE LIBRARY ALEX LIBTYPE=MANUAL
DEFINE DRIVE ALEX DRIVE_01 ONLINE=Yes
DEFINE PATH ADSM ALEX SRCTYPE=SERVER DESTTYPE=LIBRARY ONLINE=YES
DEFINE PATH ADSM DRIVE_01 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=ALEX
DEVICE=/dev/rmtX ONLINE=YES

And the 'define path' for the drive is all one line. I've actually got
this set up as my D/R device config file that I load from floppy just
before the database restore. Saves editing on-site.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 4:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: disaster recovery drill: emergency!!!

Hi Tom,

Gotcha!  So I guess my devconfig file could look like this.  And then
when
it's up and it has restored the TSM server it will have the identical
definitions as I have at home and then I will just define more manual
drives, the paths to the drives and move from there?  If I leave the
other
definitions there after the TSM DB restore, will conflicts occur?  Thank
you again!

  DEFINE DEVCLASS DR_LTO2 DEVTYPE=LTO FORMAT=ULTRIUM2C
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=60
  MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=DRLIB
  DEFINE DEVCLASS NASDEV DEVTYPE=NAS FORMAT=DRIVE
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=180
  MOUNTRETENTION=0 PREFIX=ADSM LIBRARY=DRLIB
  SET SERVERNAME TSMPROD
  SET SERVERPASSWORD 1829fecd5fecda74
  DEFINE LIBRARY DRLIB LIBTYPE=MANUAL
  DEFINE DRIVE LTO1
  DEFINE DRIVE LTO6
  DEFINE PATH TSMPROD LTO1 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=DRLIB
  DEVICE=/DEV/RMT#
  DEFINE PATH NAS_SERVER_2 LTO6 SRCTYPE=DATAMOVER DESTTYPE=DRIVE
  LIBRARY=DRLIB DEVICE=C64T0LO





Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>
To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
         Dist Stor
cc
 Manager"
 <[EMAIL PROTECTED]
Subject
 .EDU> Re: disaster recovery drill:
   emergency!!!

 03/07/2005 04:35
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






Would you believe -- both?

Until the TSM database is restored and TSM started, you live off the
device config file; after the restore, you live off the definition in
the TSM database.

So -- change the device config file -- I usually go with a one-drive
manual library, as that's all I need to get the database restore
running. Once the database is restored, start TSM and make any changes
required to drives/paths/libraries. I've found it simpler to just delete
everything and then re-define to match the D/R environment.

Tom Kauffman
NIBCO, Inc

-Original Message

Re: disaster recovery drill: emergency!!!

[Joni Moyer]

Hi Tom,

I'm just wondering how you have a manual library and then have a path with
desttype=library instead of desttype=drive?  And also, can I just update my
lto2_offsite device class to point to my drlib manual library definition
since that is what will be asking for the tape mounts?  Thanks again!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>   To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager"
 <[EMAIL PROTECTED] Subject
     .EDU> Re: disaster recovery drill:
   emergency!!!

 03/07/2005 05:09
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






Your 'define drive' commands need to reference the library they're in;
FWIW, here's mine:

DEFINE DEVCLASS NIBLTO DEVTYPE=LTO FORMAT=DRIVE MOUNTLIMIT=DRIVES
MOUNTWAIT=60 MOUNTRETENTION=60 PREFIX=ADSM LIBRARY=ALEX
SET SERVERNAME ADSM
DEFINE LIBRARY ALEX LIBTYPE=MANUAL
DEFINE DRIVE ALEX DRIVE_01 ONLINE=Yes
DEFINE PATH ADSM ALEX SRCTYPE=SERVER DESTTYPE=LIBRARY ONLINE=YES
DEFINE PATH ADSM DRIVE_01 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=ALEX
DEVICE=/dev/rmtX ONLINE=YES

And the 'define path' for the drive is all one line. I've actually got
this set up as my D/R device config file that I load from floppy just
before the database restore. Saves editing on-site.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 4:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: disaster recovery drill: emergency!!!

Hi Tom,

Gotcha!  So I guess my devconfig file could look like this.  And then
when
it's up and it has restored the TSM server it will have the identical
definitions as I have at home and then I will just define more manual
drives, the paths to the drives and move from there?  If I leave the
other
definitions there after the TSM DB restore, will conflicts occur?  Thank
you again!

  DEFINE DEVCLASS DR_LTO2 DEVTYPE=LTO FORMAT=ULTRIUM2C
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=60
  MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=DRLIB
  DEFINE DEVCLASS NASDEV DEVTYPE=NAS FORMAT=DRIVE
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=180
  MOUNTRETENTION=0 PREFIX=ADSM LIBRARY=DRLIB
  SET SERVERNAME TSMPROD
  SET SERVERPASSWORD 1829fecd5fecda74
  DEFINE LIBRARY DRLIB LIBTYPE=MANUAL
  DEFINE DRIVE LTO1
  DEFINE DRIVE LTO6
  DEFINE PATH TSMPROD LTO1 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=DRLIB
  DEVICE=/DEV/RMT#
  DEFINE PATH NAS_SERVER_2 LTO6 SRCTYPE=DATAMOVER DESTTYPE=DRIVE
  LIBRARY=DRLIB DEVICE=C64T0LO





Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>
To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor
cc
 Manager"
 <[EMAIL PROTECTED]
Subject
 .EDU> Re: disaster recovery drill:
   emergency!!!

 03/07/2005 04:35
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






Would you believe -- both?

Until the TSM database is restored and TSM started, you live off the
device config file; after the restore, you live off the definition in
the TSM database.

So -- change the device config file -- I usually go with a one-drive
manual library, as that's all I need to get the database restore
running. Once the database is restored, start TSM and make any changes
required to drives/paths/libraries. I've found it simpler to just delete
everything and then re-define to match the D/R environment.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 4:14 PM
To: ADSM-L@VM.MARIST.EDU
Subject: disaster recovery drill: emergency!!!

Hey All!

I'm going to do a DR pre-test to see what I need to do concerning the
devconfig file.  I currently have an External and ACSLS library
configured
with LTO2 tape drives, the device classes, paths, etc.  When

Re: disaster recovery drill: emergency!!!

[Kauffman, Tom]

Your 'define drive' commands need to reference the library they're in;
FWIW, here's mine:

DEFINE DEVCLASS NIBLTO DEVTYPE=LTO FORMAT=DRIVE MOUNTLIMIT=DRIVES
MOUNTWAIT=60 MOUNTRETENTION=60 PREFIX=ADSM LIBRARY=ALEX
SET SERVERNAME ADSM
DEFINE LIBRARY ALEX LIBTYPE=MANUAL
DEFINE DRIVE ALEX DRIVE_01 ONLINE=Yes
DEFINE PATH ADSM ALEX SRCTYPE=SERVER DESTTYPE=LIBRARY ONLINE=YES
DEFINE PATH ADSM DRIVE_01 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=ALEX
DEVICE=/dev/rmtX ONLINE=YES

And the 'define path' for the drive is all one line. I've actually got
this set up as my D/R device config file that I load from floppy just
before the database restore. Saves editing on-site.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 4:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: disaster recovery drill: emergency!!!

Hi Tom,

Gotcha!  So I guess my devconfig file could look like this.  And then
when
it's up and it has restored the TSM server it will have the identical
definitions as I have at home and then I will just define more manual
drives, the paths to the drives and move from there?  If I leave the
other
definitions there after the TSM DB restore, will conflicts occur?  Thank
you again!

  DEFINE DEVCLASS DR_LTO2 DEVTYPE=LTO FORMAT=ULTRIUM2C
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=60
  MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=DRLIB
  DEFINE DEVCLASS NASDEV DEVTYPE=NAS FORMAT=DRIVE
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=180
  MOUNTRETENTION=0 PREFIX=ADSM LIBRARY=DRLIB
  SET SERVERNAME TSMPROD
  SET SERVERPASSWORD 1829fecd5fecda74
  DEFINE LIBRARY DRLIB LIBTYPE=MANUAL
  DEFINE DRIVE LTO1
  DEFINE DRIVE LTO6
  DEFINE PATH TSMPROD LTO1 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=DRLIB
  DEVICE=/DEV/RMT#
  DEFINE PATH NAS_SERVER_2 LTO6 SRCTYPE=DATAMOVER DESTTYPE=DRIVE
  LIBRARY=DRLIB DEVICE=C64T0LO





Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>
To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor
cc
 Manager"
 <[EMAIL PROTECTED]
Subject
 .EDU> Re: disaster recovery drill:
   emergency!!!

 03/07/2005 04:35
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






Would you believe -- both?

Until the TSM database is restored and TSM started, you live off the
device config file; after the restore, you live off the definition in
the TSM database.

So -- change the device config file -- I usually go with a one-drive
manual library, as that's all I need to get the database restore
running. Once the database is restored, start TSM and make any changes
required to drives/paths/libraries. I've found it simpler to just delete
everything and then re-define to match the D/R environment.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 4:14 PM
To: ADSM-L@VM.MARIST.EDU
Subject: disaster recovery drill: emergency!!!

Hey All!

I'm going to do a DR pre-test to see what I need to do concerning the
devconfig file.  I currently have an External and ACSLS library
configured
with LTO2 tape drives, the device classes, paths, etc.  When I go to DR
I
will have just the drives attached to the server.  My question is:
before
I issue the dsmserv restore command to restore the TSM server from a
dbbackup, do I want to delete all references to the home TSM
configuration
and add the manual library, device class and paths or do I do
delete/update/add the configuration changes to the server after?   I
have
everything planned out using my DRM plan, but this is the only portion
of
the plan that I am unsure of the order of operations.  Thank you in
advance!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]

Re: disaster recovery drill: emergency!!!

[Joni Moyer]

Hi Tom,

Gotcha!  So I guess my devconfig file could look like this.  And then when
it's up and it has restored the TSM server it will have the identical
definitions as I have at home and then I will just define more manual
drives, the paths to the drives and move from there?  If I leave the other
definitions there after the TSM DB restore, will conflicts occur?  Thank
you again!

  DEFINE DEVCLASS DR_LTO2 DEVTYPE=LTO FORMAT=ULTRIUM2C
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=60
  MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=DRLIB
  DEFINE DEVCLASS NASDEV DEVTYPE=NAS FORMAT=DRIVE
  ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=180
  MOUNTRETENTION=0 PREFIX=ADSM LIBRARY=DRLIB
  SET SERVERNAME TSMPROD
  SET SERVERPASSWORD 1829fecd5fecda74
  DEFINE LIBRARY DRLIB LIBTYPE=MANUAL
  DEFINE DRIVE LTO1
  DEFINE DRIVE LTO6
  DEFINE PATH TSMPROD LTO1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=DRLIB
  DEVICE=/DEV/RMT#
  DEFINE PATH NAS_SERVER_2 LTO6 SRCTYPE=DATAMOVER DESTTYPE=DRIVE
  LIBRARY=DRLIB DEVICE=C64T0LO





Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]




 "Kauffman, Tom"
 <[EMAIL PROTECTED]
 COM>   To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager"
 <[EMAIL PROTECTED] Subject
     .EDU> Re: disaster recovery drill:
   emergency!!!

 03/07/2005 04:35
 PM


 Please respond to
 "ADSM: Dist Stor
 Manager"
 <[EMAIL PROTECTED]
   .EDU>






Would you believe -- both?

Until the TSM database is restored and TSM started, you live off the
device config file; after the restore, you live off the definition in
the TSM database.

So -- change the device config file -- I usually go with a one-drive
manual library, as that's all I need to get the database restore
running. Once the database is restored, start TSM and make any changes
required to drives/paths/libraries. I've found it simpler to just delete
everything and then re-define to match the D/R environment.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 4:14 PM
To: ADSM-L@VM.MARIST.EDU
Subject: disaster recovery drill: emergency!!!

Hey All!

I'm going to do a DR pre-test to see what I need to do concerning the
devconfig file.  I currently have an External and ACSLS library
configured
with LTO2 tape drives, the device classes, paths, etc.  When I go to DR
I
will have just the drives attached to the server.  My question is:
before
I issue the dsmserv restore command to restore the TSM server from a
dbbackup, do I want to delete all references to the home TSM
configuration
and add the manual library, device class and paths or do I do
delete/update/add the configuration changes to the server after?   I
have
everything planned out using my DRM plan, but this is the only portion
of
the plan that I am unsure of the order of operations.  Thank you in
advance!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]

Re: disaster recovery drill: emergency!!!

[Kauffman, Tom]

Would you believe -- both?

Until the TSM database is restored and TSM started, you live off the
device config file; after the restore, you live off the definition in
the TSM database.

So -- change the device config file -- I usually go with a one-drive
manual library, as that's all I need to get the database restore
running. Once the database is restored, start TSM and make any changes
required to drives/paths/libraries. I've found it simpler to just delete
everything and then re-define to match the D/R environment.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Monday, March 07, 2005 4:14 PM
To: ADSM-L@VM.MARIST.EDU
Subject: disaster recovery drill: emergency!!!

Hey All!

I'm going to do a DR pre-test to see what I need to do concerning the
devconfig file.  I currently have an External and ACSLS library
configured
with LTO2 tape drives, the device classes, paths, etc.  When I go to DR
I
will have just the drives attached to the server.  My question is:
before
I issue the dsmserv restore command to restore the TSM server from a
dbbackup, do I want to delete all references to the home TSM
configuration
and add the manual library, device class and paths or do I do
delete/update/add the configuration changes to the server after?   I
have
everything planned out using my DRM plan, but this is the only portion
of
the plan that I am unsure of the order of operations.  Thank you in
advance!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]

Re: disaster recovery test

[Muthyam Reddy]

** High Priority **


You should find one from volhistory file like 'dbbfull'. You can
restore tsm db by two ways..one tape name and 2nd just with time, which
is going to search in volhistory file after you set correct paths in
dsmserv.opt.

good luck

muthyam

I am currently at a disaster recovery test and am having a problem
finding my TSM DB tape.  The DRM plan is calling for a tape that
doesn't
appear to be here.  I just upgraded a month ago to tsm 5.1.9 (AIX
4.3.3).  Does anyone know what the command is to see what tapes are DB
backup tapes ?

Thanks,
Ralph


This electronic mail transmission contains information from Joy Mining Machinery
which is confidential, and is intended only for the use of the proper addressee.
If you are not the intended recipient, please notify us immediately at the return
address on this transmission, or by telephone at (724) 779-4500, and delete
this message and any attachments from your system.  Unauthorized use, copying,
disclosing, distributing, or taking any action in reliance on the contents of
this transmission is strictly prohibited and may be unlawful.

<>

Re: disaster recovery test

[Levi, Ralph]

thanks

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Das, Samiran (IDS ECCS)
Sent: October 04, 2004 12:02 PM
To: [EMAIL PROTECTED]
Subject: Re: disaster recovery test


Ralph,

Q volhist type=dbb

Regards, Samiran Das


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Levi, Ralph
Sent: Monday, October 04, 2004 11:44 AM
To: [EMAIL PROTECTED]
Subject: disaster recovery test


Hi all,

I am currently at a disaster recovery test and am having a problem
finding my TSM DB tape.  The DRM plan is calling for a tape that doesn't
appear to be here.  I just upgraded a month ago to tsm 5.1.9 (AIX
4.3.3).  Does anyone know what the command is to see what tapes are DB
backup tapes ?

Thanks,
Ralph 

 
If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy,
retain or redistribute it. Click here for important additional terms
relating to this e-mail. http://www.ml.com/email_terms/ 

 

Re: disaster recovery test

[PAC Brion Arnaud]

Ralph, 

You should be able to find out on which volume your last DB backup was
done by looking in the volhistory file : there must be a least one entry
with "BACKUPFULL" !
Cheers. 


Arnaud 


**
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone:  +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: [EMAIL PROTECTED]

**

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Levi, Ralph
Sent: Monday, 04 October, 2004 17:44
To: [EMAIL PROTECTED]
Subject: disaster recovery test

Hi all,

I am currently at a disaster recovery test and am having a problem
finding my TSM DB tape.  The DRM plan is calling for a tape that doesn't
appear to be here.  I just upgraded a month ago to tsm 5.1.9 (AIX
4.3.3).  Does anyone know what the command is to see what tapes are DB
backup tapes ?

Thanks,
Ralph

Re: disaster recovery test

[Ray, Mark]

" q libv "



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Levi, Ralph
Sent: Monday, October 04, 2004 11:44 AM
To: [EMAIL PROTECTED]
Subject: disaster recovery test


Hi all,

I am currently at a disaster recovery test and am having a problem
finding my TSM DB tape.  The DRM plan is calling for a tape that doesn't
appear to be here.  I just upgraded a month ago to tsm 5.1.9 (AIX
4.3.3).  Does anyone know what the command is to see what tapes are DB
backup tapes ?

Thanks,
Ralph

Re: disaster recovery test

[Das, Samiran (IDS ECCS)]

Ralph,

Q volhist type=dbb

Regards, Samiran Das


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Levi, Ralph
Sent: Monday, October 04, 2004 11:44 AM
To: [EMAIL PROTECTED]
Subject: disaster recovery test


Hi all,

I am currently at a disaster recovery test and am having a problem
finding my TSM DB tape.  The DRM plan is calling for a tape that doesn't
appear to be here.  I just upgraded a month ago to tsm 5.1.9 (AIX
4.3.3).  Does anyone know what the command is to see what tapes are DB
backup tapes ?

Thanks,
Ralph 

 
If you are not an intended recipient of this e-mail, please notify the sender, delete 
it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click 
here for important additional terms relating to this e-mail. 
http://www.ml.com/email_terms/ 

 

Re: Disaster Recovery Manager

[Kauffman, Tom]

Joni --

I can't help with the DR Manager because we don't use it -- back in the
ADSM 2.x days it seemed to pricey to us and I couldn't see anything it
was doing (then) that we couldn't do on our own. I haven't looked at it
since, as our processes work.

But -- there is a bit of prep work required before you're ready to use
the DR Manager at D/R, and I can help with some of that.

First you need to restore the TSM environment. To assist in this, I have
a /DR directory on my root volume. Once a week I snapshot my TSM volume
group info to this directory: lsvg adsmvg >/DR/adsmvg.vglst and lsvg -l
adsmvg >/DR/adsmvg.lvlst. These allow rebuilding the volume group from
scratch if the automated process fails. I also run a savevg: savevg4vp
-I -e -f /DR/backup.adsmvg adsmvg. The exclude file ('-e' option)
contains /* -- exclude everything -- so all that gets created is the
meta-data for the vg. Now, when we run our weekly mksysb, we have
captured the data required to recreate the TSM volume group.

Now - at D/R.

Restore the AIX environment. We boot to service mode from CD and select
'restore system from a backup tape'; this will 'clone' the system,
getting any additional device drivers required for the hardware from the
CD. Then do a restore of the tsm vg: restvg4vp -f /DR/backup.adsmvg
. (The '4vp' is because we run SSD and multiple
paths to our ESS).

And now you're ready to recover your device config and volume history,
make any changes required to the device config, and restore the TSM
database. These are covered (IIRC) in the DR Manager scripts and
procedures, so someone else needs to step in here :-)

Tom Kauffman
NIBCO, Inc

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Thursday, September 02, 2004 7:42 AM
To: [EMAIL PROTECTED]
Subject: Disaster Recovery Manager

Hello All!

I believe that I am a little confused as to what/how DR Manager is and
works? I have looked at the manual, but things still don't make sense to
me
and I didn't want to wait until everything was configured due to the
fact
that I might be having a DR drill in December and we haven't even begun
moving things to the new environment.

1a.  I first looked at define machine and it appears as if I have to
define
the TSM server and all nodes that I wish to restore at a DR site?
1b.  Then you define the machine node association which seems as if you
just associate all of the nodes to the tsm server that you wish to
restore
from.  Why is this needed?  You would think that this is naturally
assumed
since this is where it has been backed up/defined...
1c.  Define Recovery Media - not quite sure what this is... There is a
type
of boot or other?  I'm not quite sure what this section is for?  It's
not
very clear!
1d.  Define Media Machine Association - Still confused about this
portion
as well.  When it is stated that the recovery media is to: Select the
name
of the recovery media to be associated with one or more machines. Do
they
mean TSM server machines or node machines?

2. DRM Offsite Recovery Media - Currently we just take all of our tapes
that have been vaulted to the DR site that were created before the DBB
that
we use for our DR.  I'm not quite sure what the commands portion of this
querying does?  Why/what would you specify here?

3a.  Create Recovery Plan File - Where do companies usually store this
file?  When you go down to DR, where do you begin?  I mean, what is the
starting point?  Where do you begin?
3b.  Do you use a dbbackup or a dbsnapshot?  Why would you ever want to
use
a snapshot?  You first have to restore the entire db before moving on...

4.  How often do you create the plan and how long do you retain the
plans?

I am sorry for my ignorance, but I am moving to a brand new TSM AIX
5.2.2.5
environment from the mainframe and everything is very cloudy.  Currently
we
just restore our TSM envrironment by restoring our DB & recovery log
volumes and starting up the tsm server, but now everything has changed
and
I'm not really sure how to restore this new environment or even where to
begin.  If anyone is willing to share a step by step plan/process of
your
recovery I would appreciate it!  It might give me a direction on
how/where
this will be accomplished.  Thank you in advance!


Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
[EMAIL PROTECTED]

CONFIDENTIALITY NOTICE:  This email and any attachments are for the exclusive and 
confidential use of the intended recipient.  If you are not the intended recipient, 
please do not read, distribute or take action in reliance upon this message. If you 
have received this in error, please notify us immediately by return email and promptly 
delete this message and its attachments from your computer system. We do not waive 
attorney-client or work product privilege by the transmission of this message.

Re: Disaster Recovery Manager

[Thomas Denier]

> 1a.  I first looked at define machine and it appears as if I have to define
> the TSM server and all nodes that I wish to restore at a DR site?

You may define any or all of these if you want the information stored in
the TSM database or incorporated into the recovery plan (TSM server only).
You are not required to define any of them. We have never used 'define
machine' and the related commands. Storing the corresponding information
outside of TSM allows client system administrators to reinstall their
operating systems and TSM client software while I am recreating the TSM
server.

> 1b.  Then you define the machine node association which seems as if you
> just associate all of the nodes to the tsm server that you wish to restore
> from.  Why is this needed?  You would think that this is naturally assumed
> since this is where it has been backed up/defined...

This allows for situations in which two or more client nodes are registered
for the same physical system. For example, most of our Oracle servers have
two nodes registered: one for file oriented backups and one for TDP.

> 1c.  Define Recovery Media - not quite sure what this is... There is a type
> of boot or other?  I'm not quite sure what this section is for?  It's not
> very clear!

This can be used for media required to install an operating system and
TSM client software before running TSM restores, such as Windows
distribution CD's or mksysb tapes for AIX systems. It is not required.

> 1d.  Define Media Machine Association - Still confused about this portion
> as well.  When it is stated that the recovery media is to: Select the name
> of the recovery media to be associated with one or more machines. Do they
> mean TSM server machines or node machines?

This allows for situations in which two or more systems share the same
recovery media, such as mulitple Windows systems that use the same
distribution CD's. It can be used for either client or server systems.

> 2. DRM Offsite Recovery Media - Currently we just take all of our tapes
> that have been vaulted to the DR site that were created before the DBB that
> we use for our DR.  I'm not quite sure what the commands portion of this
> querying does?  Why/what would you specify here?

I am not sure what command or commands you are referring to here.

> 3a.  Create Recovery Plan File - Where do companies usually store this
> file?  When you go down to DR, where do you begin?  I mean, what is the
> starting point?  Where do you begin?

As far as I can tell from past postings on this topics, most DRM sites
transfer two or more copies of this file to servers away from their
data centers. The transfers are done by a variety of means. I have heard
of e-mail, FTP, and NFS in this connection. Our approach is rather
unusual. We copy the recovery plan to a second file on the database
backup tape. This is relatively easy for a server running under z/OS. I
suspect that it would be much harder on other platforms.

The process at the DR site (for a Unix server platform) is as follows:
1.Recreate the operating system and TSM software on the replacement server.
2.Fetch the latest recovery plan from wherever it is stored.
3.Break the recovery plan into subfiles.
4.Execute shell scripts extracted in the previous step to recreate
  current versions of the server's configuration files and database
  and to update the status of storage pool tapes.

> 3b.  Do you use a dbbackup or a dbsnapshot?  Why would you ever want to use
> a snapshot?  You first have to restore the entire db before moving on...

We use dbsnapshots as protection from disasters that would require moving to
a replacement data center. We keep a weekly full backups and daily
incremental backups onsite as protection from smaller problems such as
disk failures. The advantage of the dbsnapshot is that it does not
interfere with the server's tracking of relationships between full and
incremental backups. I don't understand your objection to dbsnapshots;
if you end up using any form of backup of the TSM database you will have
to restore the entire DB before moving on.

> 4.  How often do you create the plan and how long do you retain the plans?

We create a plan every day and keep plans for three days. Each plan contains
instructions for restoring the latest database backup of the appropriate
type. You should create a new plan whenever you create a database backup
that will go offsite and keep the plan as long as you keep the backup.
Note that the 'source' operand on the 'prepare' and 'move drmedia' commands
must match the 'type' operand used on the relevant 'backup db' command.

Re: Disaster Recovery

[Fernando Figueiredo (EDS)]

In our DR procedure we have included only the last 8 days of our COPY_POOL volumes 
from DRMEDIA table, that need to be sent to DR Site. Our backup size is almost 2Tb on 
a daily basis and we do full backups weekly and incremental on a daily basis to LTO1.
Using this method we can control the number of volumes that need to be sent to our DR 
center, and we can reduce operations during recover, otherwise we need to load 
required volumes into the library each time TSM require. 

We send prepare file and "priority volumes" (from drmedia table) to our DR site and to 
our offsite safe. You'll not need to change anything in you prepare file, DR plan and 
DR tests. 
The result in a DR Test scenario should be the same as your DR Plan.

You shouldn't create DR scenario tests that are different from your DR Plan otherwise 
things might not work. 

The major advantage is to test DR with COPY_POOL, but you only need to transfer part 
of your COPY_POOL and not all COPY_POOL volumes. Of course for security purposes


Fernando Figueiredo
EDS Portugal
Senior System Administrator

-Original Message-
From: Joe Pendergast [mailto:[EMAIL PROTECTED] 
Sent: terça-feira, 31 de Agosto de 2004 15:24
To: [EMAIL PROTECTED]
Subject: Re: Disaster Recovery

In our case, on this most critical server, the backupset is a part of our
DR Test because it is part of our regular DR procedures.  For this system,
we create a backupset every day.  This system, in case of emergency, can
not rely on the restore of a TSM server.  With the daily backuset, I can
start this most critical system restore first, and then work on TSM, and
the next level critical systems.  In a rare case that the backupset tape
fails, I can then attempt a restore from the restored TSM server.  The
daily backupset offers us better timing and better safety for this most
critical server.




  "Stapleton, Mark"
  <[EMAIL PROTECTED]To:   [EMAIL PROTECTED]
  ERBEE.COM>   cc:
  Sent by: "ADSM:  Subject:  Re: Disaster Recovery
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  .EDU>


  08/31/2004 07:58
  AM
  Please respond to
  "ADSM: Dist Stor
  Manager"






From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Joe Pendergast
>If the systems are small enough, and you have plenty of tapes,
>you can produce "backupset" tapes of each system.  A backupset
>is a self contained tape that allows the client to restore
>without needing the TSM server.  We use a backupset for one of
>our critical systems.

As Mr. Rodriguez mentioned earlier in this thread, using backupsets for
DR testing is not DR testing. If you're trying to replicate the
conditions that hold in a real disaster, you're not going to have
backupsets conveniently up-to-date and ready for you.

One other alternative Mr. Choate has is to run MOVE NODEDATA on the
nodes to be tested:

MOVE NODEDATA  fromstg=

Note the volume number of the tape that is written to, and check that
tape (or tapes) out in preparation for your test.

However, as Mr. Rodriguez also mentioned, this too is not a true DR
test.

--
Mark Stapleton ([EMAIL PROTECTED])
Berbee Information Networks
 Office 262.521.5627

Re: Disaster Recovery

[Joe Pendergast]

In our case, on this most critical server, the backupset is a part of our
DR Test because it is part of our regular DR procedures.  For this system,
we create a backupset every day.  This system, in case of emergency, can
not rely on the restore of a TSM server.  With the daily backuset, I can
start this most critical system restore first, and then work on TSM, and
the next level critical systems.  In a rare case that the backupset tape
fails, I can then attempt a restore from the restored TSM server.  The
daily backupset offers us better timing and better safety for this most
critical server.




  "Stapleton, Mark"
  <[EMAIL PROTECTED]To:   [EMAIL PROTECTED]
  ERBEE.COM>   cc:
  Sent by: "ADSM:      Subject:  Re: Disaster Recovery
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  .EDU>


  08/31/2004 07:58
  AM
  Please respond to
  "ADSM: Dist Stor
  Manager"






From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Joe Pendergast
>If the systems are small enough, and you have plenty of tapes,
>you can produce "backupset" tapes of each system.  A backupset
>is a self contained tape that allows the client to restore
>without needing the TSM server.  We use a backupset for one of
>our critical systems.

As Mr. Rodriguez mentioned earlier in this thread, using backupsets for
DR testing is not DR testing. If you're trying to replicate the
conditions that hold in a real disaster, you're not going to have
backupsets conveniently up-to-date and ready for you.

One other alternative Mr. Choate has is to run MOVE NODEDATA on the
nodes to be tested:

MOVE NODEDATA  fromstg=

Note the volume number of the tape that is written to, and check that
tape (or tapes) out in preparation for your test.

However, as Mr. Rodriguez also mentioned, this too is not a true DR
test.

--
Mark Stapleton ([EMAIL PROTECTED])
Berbee Information Networks
 Office 262.521.5627

Re: Disaster Recovery

[Warren, Matthew (Retail)]

I have come across this scenario before, and we too decided against
generating subsets of tapes. It distorts the restore times compared to a
'real' disaster, and implies knowledge of the impending disaster.

We decided to go through the test relying on day to day procedure to
maintain the data we needed. The first time through was, interestingly,
a disaster.. but it helped us evaluate our setup and procedure, and by
the third time through everything worked well, and we generated fairly
consistent & reliable recovery times that could then be used with some
confidence to predict how long recovery  of various systems would take.

Matt.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joe Pendergast
Sent: Monday, August 30, 2004 5:21 PM
To: [EMAIL PROTECTED]
Subject: Re: Disaster Recovery

There are multiple options for this scenario.

If the systems are small enough, and you have plenty of tapes, you can
produce "backupset" tapes of each system.  A backupset is a self
contained
tape that allows the client to restore without needing the TSM server.
We
use a backupset for one of our critical systems.

The idea of a separate offsite pool with the critical systems on it
works
just fine.  One thing that we had to set up was a move data script to
keep
all the data for the offsite tapes down to just a few tapes.

One thing I must caution you on DR tests:  Keep it real.  We have one
group
that creates a "special" set of tapes just for their DR test.  This
makes
their test very successful, but I am very afraid of an actual disaster.
In
the case of an actual disaster they will not have time to create
"special"
tapes, and thus they will be recovering under totally different
circumstances.  I am fearful that they will be unable to meet their SLA
in
an actual disaster.  My group is using standard processes against the
standard set of tapes that are sent offsite every day.




  James Choate
  <[EMAIL PROTECTED]To:
[EMAIL PROTECTED]
  NC.COM>  cc:
  Sent by: "ADSM:  Subject:  Disaster
Recovery
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  .EDU>


  08/30/2004 08:13
  AM
  Please respond to
  "ADSM: Dist Stor
  Manager"






Hi all,

We are going to SunGard in November and we are interested in rebuilding
our
TSM server and 3 nodes that are in our environment.  We do not want to
take
our entire OFFSITE tape pool with us to Sungard.  Is there a way that we
can easily create a seperate storage pool for just the 3 nodes we are
interested in recovering + at the same time leave our current OFFSITE
storage pool in place?

Any ideas of what other folks are doing in this scenario would be
greatly
appreciated.

Thanks,
James Choate


___ Disclaimer Notice __
This message and any attachments are confidential and should only be read by those to 
whom they are addressed. If you are not the intended recipient, please contact us, 
delete the message from your computer and destroy any copies. Any distribution or 
copying without our prior permission is prohibited.

Internet communications are not always secure and therefore Powergen Retail Limited 
does not accept legal responsibility for this message. The recipient is responsible 
for verifying its authenticity before acting on the contents. Any views or opinions 
presented are solely those of the author and do not necessarily represent those of 
Powergen Retail Limited. 

Registered addresses:

Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG.
Registered in England and Wales No: 3407430

Telephone +44 (0) 2476 42 4000
Fax +44 (0) 2476 42 5432

Re: Disaster Recovery

[Stapleton, Mark]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
Behalf Of Joe Pendergast
>If the systems are small enough, and you have plenty of tapes, 
>you can produce "backupset" tapes of each system.  A backupset 
>is a self contained tape that allows the client to restore 
>without needing the TSM server.  We use a backupset for one of 
>our critical systems.

As Mr. Rodriguez mentioned earlier in this thread, using backupsets for
DR testing is not DR testing. If you're trying to replicate the
conditions that hold in a real disaster, you're not going to have
backupsets conveniently up-to-date and ready for you.

One other alternative Mr. Choate has is to run MOVE NODEDATA on the
nodes to be tested:

MOVE NODEDATA  fromstg=

Note the volume number of the tape that is written to, and check that
tape (or tapes) out in preparation for your test.

However, as Mr. Rodriguez also mentioned, this too is not a true DR
test.

--
Mark Stapleton ([EMAIL PROTECTED])
Berbee Information Networks
Office 262.521.5627  

Re: Disaster recovery of virt. volumes server

[Mark Ferraretto]

Solution was rather simple actually.  The passwords had changed since
these instances were generated.  I went back to the old passwords and all
was well.

Mark


--
Mark Ferraretto
Unix Systems Administrator
Deutsche Bank Hong Kong
ph: +852 2203 6362   Unix support hotline:  +852 2203 6369
[EMAIL PROTECTED]




[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
09/06/04 00:13
Please respond to ADSM-L

To: [EMAIL PROTECTED]
cc:
Subject:Re: Disaster recovery of virt. volumes server


I did a Disaster Recovery test with library sharing, and had to reset the
password between the two machines.  I'd expect you need to do the same
here.  I don't have the exact steps handy, but it was the same as the
initial configuration for the setup.

Nick Cassimatis
[EMAIL PROTECTED]

He who laughs last has a good backup.

Re: Disaster recovery of virt. volumes server

[Nicholas Cassimatis]

I did a Disaster Recovery test with library sharing, and had to reset the
password between the two machines.  I'd expect you need to do the same
here.  I don't have the exact steps handy, but it was the same as the
initial configuration for the setup.

Nick Cassimatis
[EMAIL PROTECTED]

He who laughs last has a good backup.

Re: disaster recovery question

[Tom Kauffman]

This should work -- we do much the same with our TSM server on AIX for D/R.

When TSM fires up it marks all the disk pools off-line if they cannot be
accessed or are not properly formated.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 1:16 PM
To: [EMAIL PROTECTED]
Subject: disaster recovery question


Hello everyone!

At our disaster recovery site we use all offsite tape volumes and do not
use any of the disk storage pools.   Our company runs tsm on the mainframe
and does a full volume backup of all of the dasd every Sunday, which is
what they restore at disaster recovery.  I was wondering, if we don't
restore any of the volumes for the disk pools and mark them offline after
tsm is brought up will everything run smoothly as long as we restore the
db, log, volume history and device configuration volumes?  Thank you!


***
Joni Moyer
[EMAIL PROTECTED]
***
CONFIDENTIALITY NOTICE:  This e-mail and any attachments are for the exclusive and 
confidential use of the intended recipient.  If you are not the intended recipient, 
please do not read, distribute or take action in reliance upon this message. If you 
have received this in error, please notify us immediately by return e-mail and 
promptly delete this message and its attachments from your computer system. We do not 
waive attorney-client or work product privilege by the transmission of this message.

Re: Disaster recovery test

[Zlatko Krastev/ACIT]

Jack,

it was discussed many times on this list (and with inclusion of DRM in
ITSM XE will be even more):
When DRM is used let it handle expiration of DB backup tapes. Otherwise
deletion through "del volh t=dbb" would shift off-site inventory and tapes
could stay in the vault instead of recalled onsite. And your suggestion
for "todate=today-2" may get exactly this.

Zlatko Krastev
IT Consultant






"Coats, Jack" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
08.03.2003 17:26
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: Disaster recovery test


Congratulations on learning from your DR experience.

The short answer is no.  If it isn't in the database, you cannot rebuild
the
database from tapes.

There was as discussion on the list not long ago about the 'daily
procedure', the rough cut
was similar to what we use in our daily backup script:

backup stg diskdata copypool wait=y
backup stg tapedata copypool wait=y
move drmedia * wherest=courier wait=y --- DRM
backup devconfig
backup volhist
delete volhist type=all todate=today-62
delete volhist type=db todate=today-2
...
And if someone else has a better method, I am all ears! ... JC
...

Re: Disaster recovery test

[Coats, Jack]

Congratulations on learning from your DR experience.

The short answer is no.  If it isn't in the database, you cannot rebuild the
database from tapes.

There was as discussion on the list not long ago about the 'daily
procedure', the rough cut
was similar to what we use in our daily backup script:

backup stg diskdata copypool wait=y
backup stg tapedata copypool wait=y
move drmedia * wherest=courier wait=y --- DRM
backup devconfig
backup volhist
delete volhist type=all todate=today-62
delete volhist type=db todate=today-2
backup db dev=ltoclass1 scratch=y type=full wait=y
/* The move below doesn't do anything ususally, as the tape is still
mounted, that is why it is done again after expire inventory */
move drmedia * wherestate=mo rem=bulk wait=yes --- DRM
prepare wait=yes --- DRM
update stg diskdata hi=0 lo=0
/* Expire Inventory is done to (1) expire inventory ... duh, and (2) allow a
wait tiome for the migration to pretty much complete for diskdata to go to
tapepool */
expire inventory wait=yes
update stg diskdata hi=20 lo=3 cache=y
move drmedia * wherestate=courierr wait=yes --- DRM
move drmedia * wherestate=mo rem=bulk wait=yes --- DRM
move drmedia * wherest=notmo wait=yes rem=bulk --- DRM

All the entries with " --- DRM" after them are DRM related of course.

As ususal, YMMV, but does this help a little?
And if someone else has a better method, I am all ears! ... JC
> -Original Message-
> From: Marcel J.E. Mol [SMTP:[EMAIL PROTECTED]
> Sent: Saturday, March 08, 2003 8:39 AM
> To:   [EMAIL PROTECTED]
> Subject:  Disaster recovery test
>
> Hello list,
>
> Last week we did a disaster recovery test and as always we learned a lot.
>
> For one thing we discoverd that the last database backup was made while
> the backup to the copypool was still running. As a result some files
> were not visable in the test environment (where of coarse we ony used
> the last database backup tapes and the copypool tapes), but all data
> must be on the last copypool tapes. Of coarse we will update the
> backup schedules so this will never happen again (famous last words)
> but I'm wondering what one can do when this would happen in a real
> disaster recovery?
>
> I determined which copypool volumes were written to after the database
> backup was made and tried to do a 'audit volume' on them. But this did
> not help. From the help audit volume I'm a bit confused what happens
> during an audit volume. The FROMDATE option says that the default date
> to audit from is TODAY. But the FROMDATE cannot be given when doing an
> audit volume . So what exactly is checked for during
> a specific volume audit?
>
> Also will the audit volume recover files on the tape that are
> not in the database, or are there other ways to do that?
>
> -Marcel
> --
>  == Marcel J.E. MolMESA Consulting
> B.V.
> ===-ph. +31-(0)6-54724868  P.O. Box 112
> ===-[EMAIL PROTECTED] 2630 AC
> Nootdorp
> __ www.mesa.nl ---U_n_i_x__I_n_t_e_r_n_e_t The Netherlands
> 
>  They couldn't think of a number,   Linux user 1148  --
> counter.li.org
> so they gave me a name!  -- Rupert Hine  --  www.ruperthine.com

Re: Disaster Recovery Test

[Joe Pendergast]

Questions for you to ponder:
Are you restoring a TSM server, and then your Application server, or are your
restoring them both to the same box.
If item 1 is "one box", Do you already have the TSM server software sitting
dormant on the Application server.
Are you using DRM?
Have you already attempted a dry run on your in-house systems?
Should you add a recent backupset to your list of "Things to Take"?

Your list looks fairly complete.  When we ran our DR test at Sungard, I had
forgotten the Atape drivers.  If you install the Atape drivers on your server
before your mksysb, they will already be on the server.

We ran two different style tests on two different servers:

First one was a backupset restore. (Offers a quick and accurate restore, but
does not work well if a TDP is involved.)
1) Boot box with our sysback tape, and restore rootvg from sysback.
(Your routine will include the mksysb tapes and the savevgs)
2) Reboot and use the TSM client to restore the backupset using the overwrite
"ifnewer" option.
3) Reboot and test the application and we are done.

Second method, restore TSM server and application to the same box:
1) Same as other routine, boot box and load rootvg - remember to reboot
2) Create VG, LV, and FS as needed to load TSM database and logs
3) Load the DRM planfile from the floppy and expand it.
4) Adjust TSM configuration files as necessary for the change in environment (ie
tape)
5) Execute DRM script "RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE"
6) When the DRM scripts asks for the dsm console to be started:
 a) double check the dsm.opt and dsm.sys files on the client (ie change
server name)
 b) start the TSM server if not already started
 c) remove the drives/libraries
 d) add the corrected library/drive
 e) start the dsm console (the console allows you to see tape requests on
the server)
 f) press return on the first session to complete the DRM script
7) restore the OS and application using the overwrite "ifnewer" option - a
reboot after might be good for safety
8) restore the application data using the TDP software





Theresa Sarver <[EMAIL PROTECTED]> on 12/18/2002 12:34:42 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: Joseph Pendergast/Corona/Watson)

Subject:  Disaster Recovery Test



Hi all;

I'm getting ready to preform a Disaster Recovery test (with Sungard) and I was
wondering if anyone would be interested in reviewing my steps and letting me
know of anything I may be missing. - Thanks in advance!

THINGS TO TAKE:
mksysb (and savevgs)
AIX 4.3.3 cdroms
Atape drivers
DLT tape drivers
Application Software  (Stars/Sql_backtrack/OBSI)
Database software (Sybase)
Tivoli Software
All license Information

Steps to Restore:
1)  Restore mksysb
2)  Install ATAPE/DLT drivers
3)  Restore savevgs
4)  Restore TSM database
5)  Restore "Export Node" data
6)  Restore OS data  (not sure if this step is necessary?)
7)  Install Application/Database Software (not sure if this step is necessary?)
8)  Restore Sybase [raw] data
9)  Check network connectivity

Also, our environment has 2 internal DLT tape drives, I will only have 1
external DLT drive during the test - will Tivoli have a problem [restoring] with
this?

Any advice or comments would be much appreciated - thanks again!

Have a happy holidays;
Theresa

Re: Disaster Recovery Test

[Kauffman, Tom]

Theresa --

1) I don't know if this is your plan, but the best bet is to boot from CD,
select the maintenance mode shell, and select "install from system backup".
Then select your mksysb tape as the install device. This will 'clone' your
system, adding device drivers from the CD as required.

2) Shouldn't need to do this, the Atape driver should be on the mksysb

3) I'm presuming here that you have vg backups with all data excluded
(/etc/exclude. with /* as the only content) and are recovering the
vg, lv, and filesystem definitions only. (I run the savevg to a
/DR/backup. every time the vg changes, then re-run the mksysb).

4) You'll need to change your device config file to match the device name of
your tape drive (and manual library, if that's what you'll use). I dump the
current device config and volume history to floppy daily and ship it off
with the TSM database backup.

5) ? (We've never done this -- 'export node' that is . . .)

6) Only required if your mksysb is out of date or you're trying to be
current on user passwords. We just reset the user passwords as required.

7) Should be able to restore this via TSM

After you get TSM up you'll need to re-do your tape drive and library
definitions -- TSM won't update the database from the device config file
used for the database recovery.

Hope this helps a bit --

Good luck, and please let us know how it turns out.

Tom Kauffman
NIBCO, Inc

> -Original Message-
> From: Theresa Sarver [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 18, 2002 3:35 PM
> To: [EMAIL PROTECTED]
> Subject: Disaster Recovery Test
>
>
> Hi all;
>
> I'm getting ready to preform a Disaster Recovery test (with
> Sungard) and I was wondering if anyone would be interested in
> reviewing my steps and letting me know of anything I may be
> missing. - Thanks in advance!
>
> THINGS TO TAKE:
> mksysb (and savevgs)
> AIX 4.3.3 cdroms
> Atape drivers
> DLT tape drivers
> Application Software  (Stars/Sql_backtrack/OBSI)
> Database software (Sybase)
> Tivoli Software
> All license Information
>
> Steps to Restore:
> 1)  Restore mksysb
> 2)  Install ATAPE/DLT drivers
> 3)  Restore savevgs
> 4)  Restore TSM database
> 5)  Restore "Export Node" data
> 6)  Restore OS data  (not sure if this step is necessary?)
> 7)  Install Application/Database Software (not sure if this
> step is necessary?)
> 8)  Restore Sybase [raw] data
> 9)  Check network connectivity
>
> Also, our environment has 2 internal DLT tape drives, I will
> only have 1 external DLT drive during the test - will Tivoli
> have a problem [restoring] with this?
>
> Any advice or comments would be much appreciated - thanks again!
>
> Have a happy holidays;
> Theresa
>

Re: Disaster Recovery Strategies with TSM redpiece

[Jane Bamberger]

Charlotte,

I have printed it and read the first couple chapters - nice job!!!

Jane
%%
Jane Bamberger
IS Department
Bassett Healthcare
607-547-4750
- Original Message -
From: "Charlotte Brooks" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 05, 2002 5:23 PM
Subject: Disaster Recovery Strategies with TSM redpiece


> I saw that some of you have already snuck in and seen this. A new draft
> redbook (aka redpiece) is up on theRedbooks website, entitled "Disaster
> Recovery Strategies with Tivoli Storage Management", SG24-6844. Search on
> SG24-6844 at www.ibm.com/redbooks, or go directly to
> http://www.redbooks.ibm.com/redpieces/pdfs/sg246844.pdf for now.  It still
> has some formatting/typo errors, however I expect the edited version (real
> redbook) to be available within the next 4 to 6 weeks. I hope you will
find
> it useful.
>
> Here's the abstract of the book
>
> Disasters, by their very nature, cannot be predicted, in either their
> intensity, timing or effects. However, all enterprises can, and should
> prepare themselves for whatever might happen in order to protect
themselves
> against loss of data, or worse, their entire business. It is too late to
> start preparing after a disaster occurs. This book will help you protect
> against a disaster - taking you step by step through the planning stages,
> with templates for sample documents. It explores the role that IBM Tivoli
> Storage Manager plays in disaster protection and recovery - from both the
> client and server side. Plus, it describes basic sample procedures for
bare
> metal recovery of some popular operating systems - Windows 2000, AIX,
> Solaris and Linux.
> This redbook is organized in two parts: the general Disaster Recovery
> Planning process is presented in Part 1. It shows the relationship (and
> close interconnection) of Business Continuity Planning with Disaster
> Recovery Planning. It also describes how you might set up a Disaster
> Recovery Plan test. Various general techniques and strategies for
> protecting your enterprise are presented. Part 2 focuses on the
practical -
> how to use IBM Tivoli Disaster Recovery Manager to create an auditable and
> easily executed recovery plan for your TSM server. It also shows
approaches
> for bare metal recovery on different client systems.
> This redbook is written for any computing professional who is concerned
> about protecting their data and enterprise from disaster. It assumes basic
> knowledge of storage technologies and products, in particular, of IBM
> Tivoli Storage Manager.
>
> Regards, Charlotte
> Project Leader, Tape and Storage Management solutions, ITSO San Jose
> email: [EMAIL PROTECTED] ph: (408) 927-3641 fax: (408) 927-3616 t/l:
> 8-457-3641
> http://ibm.com/redbooks
>

Re: Disaster Recovery Strategies with TSM redpiece

[Coats, Jack]

We still have Novell and NT4 as part of our environment.  And we STILL
have to recover them and will for some time.  I wish you could put
those sections back in.  It used to be in some of the old ADSM versions.

Thanks for asking us about what is important to us!

Re: Disaster recovery with copy storage pools.

[Steve Harris]

Do you do client compression?
If you have compressible data this may be a good way to reduce the amount of data to 
be transferred, at the expense backup speed (e.g. I have an several 8 way clients with 
big pipes but I'm limited to by compression running a single CPU at max whilst the 
others sit idle. )

It can also improve efficiency of non-tape resources - like diskpools.

Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia

>>> [EMAIL PROTECTED] 28/07/2002 1:53:12 >>>
This may be a math problem.  How much data are you trying to send over the
T1 daily.  A T1 is 1.454Mbits/sec which after taking your stack overhead off
is about 1.1Mbits or about 145KBytes/sec.  In 24 hours you can send about
12.5GB.  So, just remind your auditors this is the case and they need to
write a finding that the data center does not have enough budget to meet the
audit requirement.  Then management makes the decision as to whether they
can stay in business if they do not mirror the data.

CTAM looks real good when all said and done.  AKA. Chevy Truck Access
Method.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-Original Message-
From: John C Dury [mailto:[EMAIL PROTECTED]] 
Sent: Friday, July 26, 2002 1:36 PM
To: [EMAIL PROTECTED] 
Subject: Disaster recovery with copy storage pools.


 We currently have 2 TSM servers. TSM1 which holds the data backups of
all the fileservers in the company. TSM2 which  is off-site and is used only
as a copy storage pool which is defined on TSM1 and nightly we do a backup
of the primary storage pool (3494libpool2 on TSM1) to the copy storage pool
(DR_POOL1 on TSM2). Unfortunately this is a rather large amount of data and
runs for a very long time and doesn't finish copying in 1 day. My auditors
want to make sure that we have 2 copies of all data from our fileservers,
one on-site and one off-site. Anyone have any suggestions on how to do this
in a better fashion? Initially we were having some problems with the backup
not finishing because of a network glitch which caused the whole process
which could have been running for 8 hours or so, to fail. I believe the
network glitches have been solved but the whole operation still takes a
great deal of time, usually 24 hours.
 Because the data is going from tape to tape, I thought about making
another copy storage pool on TSM2 on DISK,instead of TAPE, and making it
have a migration threshold such that the data immediately went to TAPE from
DISK. The DISK would act like a buffer. I don't know if this is even
possible but I'm willing to try anything. Unfortunately adding a faster link
between the 2 servers isn't really an option as we are really budget
contrained. Right now it's only T1.

 Anyone have any ideas or suggestions? I'm willing to rearrange the
whole backup structure if necessary. This is how it was setup when I adopted
TSM.

Thanks much,
John



**
This e-mail, including any attachments sent with it, is confidential 
and for the sole use of the intended recipient(s). This confidentiality 
is not waived or lost if you receive it and you are not the intended 
recipient(s), or if it is transmitted/ received in error.  

Any unauthorised use, alteration, disclosure, distribution or review 
of this e-mail is prohibited.  It may be subject to a statutory duty of 
confidentiality if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this 
e-mail in error, you are asked to immediately notify the sender by 
telephone or by return e-mail.  You should also delete this e-mail 
message and destroy any hard copies produced.
**

Re: Disaster recovery with copy storage pools.

[Seay, Paul]

This may be a math problem.  How much data are you trying to send over the
T1 daily.  A T1 is 1.454Mbits/sec which after taking your stack overhead off
is about 1.1Mbits or about 145KBytes/sec.  In 24 hours you can send about
12.5GB.  So, just remind your auditors this is the case and they need to
write a finding that the data center does not have enough budget to meet the
audit requirement.  Then management makes the decision as to whether they
can stay in business if they do not mirror the data.

CTAM looks real good when all said and done.  AKA. Chevy Truck Access
Method.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-Original Message-
From: John C Dury [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 26, 2002 1:36 PM
To: [EMAIL PROTECTED]
Subject: Disaster recovery with copy storage pools.


 We currently have 2 TSM servers. TSM1 which holds the data backups of
all the fileservers in the company. TSM2 which  is off-site and is used only
as a copy storage pool which is defined on TSM1 and nightly we do a backup
of the primary storage pool (3494libpool2 on TSM1) to the copy storage pool
(DR_POOL1 on TSM2). Unfortunately this is a rather large amount of data and
runs for a very long time and doesn't finish copying in 1 day. My auditors
want to make sure that we have 2 copies of all data from our fileservers,
one on-site and one off-site. Anyone have any suggestions on how to do this
in a better fashion? Initially we were having some problems with the backup
not finishing because of a network glitch which caused the whole process
which could have been running for 8 hours or so, to fail. I believe the
network glitches have been solved but the whole operation still takes a
great deal of time, usually 24 hours.
 Because the data is going from tape to tape, I thought about making
another copy storage pool on TSM2 on DISK,instead of TAPE, and making it
have a migration threshold such that the data immediately went to TAPE from
DISK. The DISK would act like a buffer. I don't know if this is even
possible but I'm willing to try anything. Unfortunately adding a faster link
between the 2 servers isn't really an option as we are really budget
contrained. Right now it's only T1.

 Anyone have any ideas or suggestions? I'm willing to rearrange the
whole backup structure if necessary. This is how it was setup when I adopted
TSM.

Thanks much,
John

Re: Disaster Recovery Input.

[Tony Sinclair]

I need everyone's help on the list and to put on their brainstorming caps
on to put forth some ideas on how I can dramatize to upper level management
the best Disaster Recovery structure to meet our business needs to keep us
or any company in business.

I have been given the task of meeting with our companies upper level
management/directors to describe our needs/requirements/wish list based on
our companies existing Mainframe/Distributed disaster recovery
capabilities.

So I was trying to think of something dramatic that the 35 attendees could
do while they are setting down at this meeting that could demonstrate the
difficulties that we currently all face 365 days, 7/24 put forth as
requirements by these people in all companies.

I will be making this presentation at an offsite location at a local hotel,
so whatever I come up with needs to be non destructive, but demonstrate
what it really takes to be able to recover in a disaster.  I have come up
with several ideas so far, one of which was to place several large boxes of
appropriate tinker toys or legos on the table split the group up into teams
and make the request of them to build the tallest self standing building
with in 15 minuets.  Or have 10-15 candles lit on the table with a large
lit candle sitting of to the side, then blow out 4-6 candles and have them
re-light them without using matches or lighters.

I know we all face the decisions of upper level management every day on how
our systems are created, backed up and recovered, and that alot of times we
don't get the opportunity to express our own creative thoughts to these
individual's on how the best way to handle the situations we are all faced
with on a daily bases.

So if you have any suggestion or ideas I could use to make this subject
personal to them I would be eternally grateful for any ideas.  I figured
that the ones to ask where the ones who have to do the recovery daily,
those of us who work in the trenches and have the responsibility of keeping
the business of the world able to do business.

Thanks again for those who will be making suggestions.

Tony Sinclair
Lead Disaster Recovery Analyst - Sr. Storage Administrator

Re: Disaster Recovery Site

[Zlatko Krastev]

T1 simply is not enough. Just some math:
1.536 MB/s * 3600 sec/h = 5529.6 MB/h (5.4 GB/h)
5.4 GB/h * 24h/day = 129.6 GB/day
129.6 GB/day * 7 days/week = 907.2 GB/week
Having 90 GB daily change you are very very close to the limit - for real
disaster recovery you will need also TSM DB backup/snapshot at DR site and
you did not pointed how big is DB. And for sure there is no enough
throughput for weekend's SAP DB (even being one and the only).
So you have to reconsider something.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Disaster Recovery Site

Hi,

I am currently putting together a plan to make one of our sites a disaster
recovery site.  I have it visualized how I would like to do it, but I
thought I would run it past you more experienced TSM'ers in hopes you
might
catch my flaws or give me some better advise.  Here are the details:

Colorado

NSM Server -- AIX 4.3.3,  TSM 4.1.3
  We will be changing to from a NSM server to a TSM server V5.1 in the
  near future.
LTO 3584
2 Domains:
DM1 - 46 Servers
SAP - 19 Servers
Clients run the gamout from V3.7.2.19 to V4.2.1.32
Average 90 gig on weekdays and 1.5 TB on weekends (due to SAP database)


New Jersey Site 1

2 Domains:
DM1 (this is part of the DM1 in Colorado) - 2 Servers
LAB - 1 Server and 3 Workstations
Both Domains combined have 20 gig total data
Using Backup Exec with DLT drives attached to servers


New Jersey Site 2

1 Domain:
DM1 (this is part of the DM1 in Colorado) - 2 Servers
17 gig total data
Using Backup Exec with DLT drives attached to servers


Here is what I would like to do:

   Put a TSM Server  and LTO 3583 in New Jersey Site 1 to backup both New
   Jersey sites.
 We would do this with a T1 that is dedicated to only the backups.
 The TSM server would be a W2K server.
   Use the New Jersey Site 1 as a disaster recovery site for Colorado and
   vise versa.
 I would backup the tapepool in Colorado to a special Copypool
 (i.e. COLOcopypool) in New Jersey
 I would backup the tapepool in New Jersey to a special Copypool
 (i.e. NJcopypool) in Colorado.
 We have two option to get the data back and forth (my LAN WAN
 person is investigating this for me):
Dedicated line between the two sites
A T1 (dedicated ot just backups) going through a frame.


Here are my questions:

   Since they will be Disaster Recovery sites for each other, does the TSM
   server need to be the same operating system?
   Would the backup tapepool to copypool be the best way to do this?
   Has anyone else setup a system like this and how did you do it?
   Also has anyone had to provide an ROI for TSM?  I can think of some
   basic things like saving on headcount (but I have been a one person
team
   for years so that wont fly).


Sorry this email is so long.  Any advise would be greatly appreciated.

Lori Cundiff
Backup Engineer

Re: Disaster Recovery

[Steve Harris]

Hi Roy,

We are considering a DR implementation that's similar to yours - although 500 yards 
seems a little close for a DR site.

We haven't actually done it yet, but there are two major possibilities. Assuming that 
you have appropriate SAN and network setup. Further assume active/active use of the 
two sites.
Configure two TSM servers to run one at each site in such a manner that both TSM 
servers can run on the same physical box on either site.
Mirror your disk pools, DB and  logs  at the AIX level (or using ESS PPRC facilities) 
so that you can run either server at either site either singly or together.
Option 1.
Now either dedicate drives in your library to one server or the other or invest in 
library sharing licences with each server controlling what is normally its local 
library. Define each library to each server and make the tape primary stgpools go to 
the local library and copypools go to the remote library. Use each server to back up 
its local machines.
In case of failure, bring up failed server at other site. mark primary copies 
unavailable and restore as necessary from copypool.  You can have scripts on hand to 
change definitions to allow backups for the failed over clients to continue to the 
failed over server at the "wrong" library because in a real disaster its going to take 
you a while to get back.
Option 2.
If you don't have SAN connection to your remote drives, use server to server to define 
your copypools as being on the other TSM server and just run stgpool and database 
backups over the LAN.  In the case of disaster you still run both servers on the one 
machine, but restores are done tape->serverb->internal TCP/IP->servera->client, which 
will impact machine performance, but requires only a DRM licence on each server.

Option 3.
You could also physically ship your copypool tapes between the two sites.  Never 
underestimate the bandwidth of a small car loaded with carts.  

Let us know what you decide and how you get on.

Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia

>>> [EMAIL PROTECTED] 17/04/2002 6:27:12 >>>
How do you get the "libraries" connected to ESS?  Disks can be mirrored
but not tapes! I don't think there is a way to do what you say.  Maybe some
real DRM or HA expert has an answer!

I think there is a way for both RS/6000's to see both libraries, takes
some extra hardware and config steps.  I've seen it done in past
just don't have details.

However if you loose contact with one library, the second library
doesn't have access to the data in the first.

David Longo

>>> [EMAIL PROTECTED] 04/16/02 07:17AM >>>
Hi guys,

I am in the situation whereby I have to think about DR soon, and need
the best solution.

Here is the story so far:-

I have a TSM Server on an RS/6000 plugged into a 3583 library on one
site. The DR suite is 4 to 500 yards down the road. This has another
RS/6000 with a second 3583 library plugged into it for HA purposes.

What i need to be able to do, when the Primary Server fails over to the
secondary Server (In a HA situation), is to get it to use the second
library.

Both of the two libraries are plugged into to mirrored ESS's, so both
the RS/6000's should be able to see BOTH libraries.

What I was thinking of doing was putting copy tapes into the second
library, and onsite tapes into the first and utilising both librarys at
the same time - can this be done?.

If anyone could give me and pointers here as to the best approach or
any possible OTHER approaches, then I would be forever in their debt!.

Kind Regards,

Roy Lake
RS/6000 & TSM Systems Administration Team
Tibbett & Britten European I.T.
Judd House
Ripple Road
Barking
Essex IG11 0TU
0208 526 8853
[EMAIL PROTECTED] 

This e-mail message has been scanned using Sophos Sweep http://www.sophos.com 

**
---  IMPORTANT INFORMATION -
This message is intended only for the use of the Person(s) ('the
intended recipient') to whom it was addressed. It may contain
information which is privileged & confidential within the meaning
of applicable law. Accordingly any dissemination, distribution,
copying, or other use of this message, or any of its contents,
by any person other than the intended recipient may constitute
a breach of civil or criminal law and is strictly prohibited.

If you are NOT the intended recipient please contact the sender
and dispose of this email as soon as possible. If in doubt please
contact European IT on 0870 607 6777 (+44 20 85 26 88 88).
This message has been sent via the Public Internet.
**



"MMS " made the following
 annotations on 04/16/02 16:41:24
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by

Re: Disaster Recovery

[David Longo]

How do you get the "libraries" connected to ESS?  Disks can be mirrored
but not tapes! I don't think there is a way to do what you say.  Maybe some
real DRM or HA expert has an answer!

I think there is a way for both RS/6000's to see both libraries, takes
some extra hardware and config steps.  I've seen it done in past
just don't have details.

However if you loose contact with one library, the second library
doesn't have access to the data in the first.

David Longo

>>> [EMAIL PROTECTED] 04/16/02 07:17AM >>>
Hi guys,

I am in the situation whereby I have to think about DR soon, and need
the best solution.

Here is the story so far:-

I have a TSM Server on an RS/6000 plugged into a 3583 library on one
site. The DR suite is 4 to 500 yards down the road. This has another
RS/6000 with a second 3583 library plugged into it for HA purposes.

What i need to be able to do, when the Primary Server fails over to the
secondary Server (In a HA situation), is to get it to use the second
library.

Both of the two libraries are plugged into to mirrored ESS's, so both
the RS/6000's should be able to see BOTH libraries.

What I was thinking of doing was putting copy tapes into the second
library, and onsite tapes into the first and utilising both librarys at
the same time - can this be done?.

If anyone could give me and pointers here as to the best approach or
any possible OTHER approaches, then I would be forever in their debt!.

Kind Regards,

Roy Lake
RS/6000 & TSM Systems Administration Team
Tibbett & Britten European I.T.
Judd House
Ripple Road
Barking
Essex IG11 0TU
0208 526 8853
[EMAIL PROTECTED] 

This e-mail message has been scanned using Sophos Sweep http://www.sophos.com 

**
---  IMPORTANT INFORMATION -
This message is intended only for the use of the Person(s) ('the
intended recipient') to whom it was addressed. It may contain
information which is privileged & confidential within the meaning
of applicable law. Accordingly any dissemination, distribution,
copying, or other use of this message, or any of its contents,
by any person other than the intended recipient may constitute
a breach of civil or criminal law and is strictly prohibited.

If you are NOT the intended recipient please contact the sender
and dispose of this email as soon as possible. If in doubt please
contact European IT on 0870 607 6777 (+44 20 85 26 88 88).
This message has been sent via the Public Internet.
**



"MMS " made the following
 annotations on 04/16/02 16:41:24
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

Re: disaster recovery ?

[Aaron Widmeyer]

I understand that the data in on tape on the UNIX TSM server in question
but why are you trying to backup data on tape to another server when there
may be better/easier ways of getting the data off site and safe in case of
a disaster?  Why not create a copy pool and point it to a small section of
your silo, use that to collocate and copy your critical data to and then
export those tapes and take them off site.  Then in the case of a disaster
you could restore the TSM server from the "mksysb you make every month of
your system disk" (right), get your TSM server up and running and import
the tapes.  Just a suggestion.  Or maybe you  have a very legitimate reason
for going this route that I am unaware of, please inform me.

Thank you for your patience with my babbling.



"Hunley, Ike"
cc:
Sent by:         Subject: Re: disaster recovery ?
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


04/05/2002
10:01 AM
Please respond
to "ADSM: Dist
Stor Manager"






There are business critical servers backing up to the TSM on this UNIX
server.  I understood that the backup data is on tape.  It is that data we
need to recover in a disaster situation.



-Original Message-
From: Aaron Widmeyer [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 9:52 AM
To: [EMAIL PROTECTED]
Subject: Re: disaster recovery ?


If I understand what you are saying here is that you want to not only
backup the UNIX machines TSM database but the actual tapes as well to
another TSM server?  There are some options here and it has been a while
since I have read up on this and please correct me if I misunderstand or
misstate anything.  Here we go:

You could export the tapes from your UNIX TSM server and import them into
the z/OS server of your choice.

You could set it up for off site storage by setting up a mirrored (don't
think TSM uses term "mirrored") tape silo.  If I remember correctly this
involves creating a copy pool that points to a secondary tape silo?

My question to you is why are you trying to backup the data on the tapes to
another server?  Maybe with a little more information on why you are
choosing this route, of backing up data that is already backed up, we could
better help you.



bizzorg
 cc:
Sent by: "ADSM:Subject: disaster recovery ?
Dist Stor
Manager"
<[EMAIL PROTECTED]
T.EDU>


04/05/2002 03:15
AM
Please respond
to "ADSM: Dist
Stor Manager"






I hope someone out there can help.

All our TSM servers run on OS390 or z/OS, except for one UNIX based TSM.
This UNIX server is not setup for offsite storage.  I think we can back
this
server up to a TSM on z/OS.  How do I backup the backed up data?  It's all
in a tape silo attached to this UNIX box.

Thanks in advance..



Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect
the views of Blue Cross Blue Shield of Florida, Inc.

Re: disaster recovery ?

[Miller, Ryan]

Have you thought about using Server to Server Virtual Volumes, you could do this and 
create a copy pool on one of your OS/390 TSM servers.

Ryan

-Original Message-
From: Aaron Widmeyer [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 9:23 AM
To: [EMAIL PROTECTED]
Subject: Re: disaster recovery ?


I understand that the data in on tape on the UNIX TSM server in question
but why are you trying to backup data on tape to another server when there
may be better/easier ways of getting the data off site and safe in case of
a disaster?  Why not create a copy pool and point it to a small section of
your silo, use that to collocate and copy your critical data to and then
export those tapes and take them off site.  Then in the case of a disaster
you could restore the TSM server from the "mksysb you make every month of
your system disk" (right), get your TSM server up and running and import
the tapes.  Just a suggestion.  Or maybe you  have a very legitimate reason
for going this route that I am unaware of, please inform me.

Thank you for your patience with my babbling.



"Hunley, Ike"
cc:
Sent by:         Subject: Re: disaster recovery ?
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


04/05/2002
10:01 AM
Please respond
to "ADSM: Dist
Stor Manager"






There are business critical servers backing up to the TSM on this UNIX
server.  I understood that the backup data is on tape.  It is that data we
need to recover in a disaster situation.



-Original Message-
From: Aaron Widmeyer [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 9:52 AM
To: [EMAIL PROTECTED]
Subject: Re: disaster recovery ?


If I understand what you are saying here is that you want to not only
backup the UNIX machines TSM database but the actual tapes as well to
another TSM server?  There are some options here and it has been a while
since I have read up on this and please correct me if I misunderstand or
misstate anything.  Here we go:

You could export the tapes from your UNIX TSM server and import them into
the z/OS server of your choice.

You could set it up for off site storage by setting up a mirrored (don't
think TSM uses term "mirrored") tape silo.  If I remember correctly this
involves creating a copy pool that points to a secondary tape silo?

My question to you is why are you trying to backup the data on the tapes to
another server?  Maybe with a little more information on why you are
choosing this route, of backing up data that is already backed up, we could
better help you.



bizzorg
 cc:
Sent by: "ADSM:Subject: disaster recovery ?
Dist Stor
Manager"
<[EMAIL PROTECTED]
T.EDU>


04/05/2002 03:15
AM
Please respond
to "ADSM: Dist
Stor Manager"






I hope someone out there can help.

All our TSM servers run on OS390 or z/OS, except for one UNIX based TSM.
This UNIX server is not setup for offsite storage.  I think we can back
this
server up to a TSM on z/OS.  How do I backup the backed up data?  It's all
in a tape silo attached to this UNIX box.

Thanks in advance..



Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect
the views of Blue Cross Blue Shield of Florida, Inc.

Re: disaster recovery ?

[Hunley, Ike]

There are business critical servers backing up to the TSM on this UNIX
server.  I understood that the backup data is on tape.  It is that data we
need to recover in a disaster situation.



-Original Message-
From: Aaron Widmeyer [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 9:52 AM
To: [EMAIL PROTECTED]
Subject: Re: disaster recovery ?


If I understand what you are saying here is that you want to not only
backup the UNIX machines TSM database but the actual tapes as well to
another TSM server?  There are some options here and it has been a while
since I have read up on this and please correct me if I misunderstand or
misstate anything.  Here we go:

You could export the tapes from your UNIX TSM server and import them into
the z/OS server of your choice.

You could set it up for off site storage by setting up a mirrored (don't
think TSM uses term "mirrored") tape silo.  If I remember correctly this
involves creating a copy pool that points to a secondary tape silo?

My question to you is why are you trying to backup the data on the tapes to
another server?  Maybe with a little more information on why you are
choosing this route, of backing up data that is already backed up, we could
better help you.



bizzorg
 cc:
Sent by: "ADSM:Subject: disaster recovery ?
Dist Stor
Manager"
<[EMAIL PROTECTED]
T.EDU>


04/05/2002 03:15
AM
Please respond
to "ADSM: Dist
Stor Manager"






I hope someone out there can help.

All our TSM servers run on OS390 or z/OS, except for one UNIX based TSM.
This UNIX server is not setup for offsite storage.  I think we can back
this
server up to a TSM on z/OS.  How do I backup the backed up data?  It's all
in a tape silo attached to this UNIX box.

Thanks in advance..



Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this e-mail 
message. Any personal comments made in this e-mail do not reflect the views of Blue 
Cross Blue Shield of Florida, Inc.

Re: disaster recovery ?

[Aaron Widmeyer]

If I understand what you are saying here is that you want to not only
backup the UNIX machines TSM database but the actual tapes as well to
another TSM server?  There are some options here and it has been a while
since I have read up on this and please correct me if I misunderstand or
misstate anything.  Here we go:

You could export the tapes from your UNIX TSM server and import them into
the z/OS server of your choice.

You could set it up for off site storage by setting up a mirrored (don't
think TSM uses term "mirrored") tape silo.  If I remember correctly this
involves creating a copy pool that points to a secondary tape silo?

My question to you is why are you trying to backup the data on the tapes to
another server?  Maybe with a little more information on why you are
choosing this route, of backing up data that is already backed up, we could
better help you.



bizzorg
 cc:
Sent by: "ADSM:Subject: disaster recovery ?
Dist Stor
Manager"
<[EMAIL PROTECTED]
T.EDU>


04/05/2002 03:15
AM
Please respond
to "ADSM: Dist
Stor Manager"






I hope someone out there can help.

All our TSM servers run on OS390 or z/OS, except for one UNIX based TSM.
This UNIX server is not setup for offsite storage.  I think we can back
this
server up to a TSM on z/OS.  How do I backup the backed up data?  It's all
in a tape silo attached to this UNIX box.

Thanks in advance..

Re: disaster recovery ?

[Prather, Wanda]

That should be fine.
You will be rebuilding your server offsite, defining the library there, and
checking in whichever tapes you want.
That library can be anything you want that supports your drives, or no
library at all.

 A lot of people don't even use a library at their DR site; they just have
drives.
if you have tape drives but no library, you just define your library as
"manual" and respond to mount requests yourself.

-Original Message-
From: Coviello, Paul [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 22, 2002 10:33 AM
To: [EMAIL PROTECTED]
Subject: disaster recovery ?



I have been asked the following, if we lost our TSM server and tape
library, ATL P2000, with currently 100 slots and 4 drives upgrading soon to
198 or so slots.  Would a P1000 work with 2 drives and I believe 100 slots.
We are currently managing approximately 140 tapes now.   The question is do
I have to load all the tapes that are offsite into the library at once to
restore it?  or can I fill it and answer requests as they come?


thanks

Paul

Re: Disaster Recovery Project

[Coviello, Paul]

since I was trying to add this and it was kicked back, can we keep
this one going.


I have been asked the following, if we lost our TSM server and tape
library, ATL P2000, with currently 100 slots and 4 drives upgrading soon to
198 or so slots.  Would a P1000 work with 2 drives and I believe 100 slots.
We are currently managing approximately 140 tapes now.   The question is do
I have to load all the tapes that are offsite into the library at once to
restore it?  or can I fill it and answer requests as they come?


thanks

Paul

Re: Disaster Recovery Project

[Kauffman, Tom]

Step 1 -- determine which servers are 'critical' and which are 'nice to
have'; find out what the expectations are for getting the 'critical' back on
line. For example, our requirement is to recover to within 12 hours of the
outage in less than 48 hours. Make sure your backup/archive/off-site
rotation strategy matches. Ours doesn't :-(

Step 2 -- work out what you need to rebuild from scratch. For the SP frame,
you'll need to rebuild the CWS (mksysb tape); then delete all nodes and
frames, and re-acquire frames and nodes (your hot-site will NOT match your
configuration, trust me!). Then re-customize and boot/install from your node
images on disk. Back when we had an SP frame, I kept the adsm node image on
the CWS disk and had a savevg of the volume group.

I don't know about Alpha or Solaris -- there are some nice writeups from IBM
on 'bare metal restore' for NT, and AIX recovers nicely with mksysb
(complicated, on the SP frame by the nature of the beast).

You might want to take a look at the archives here
http://msgs.adsm.org/cgi-bin/get/adsm-current.html for other suggestions.

FWIW -- we were an SP frame shop, with TSM on a wide node, and ran several
successful D/R tests. Now we have 6 RS/6000 systems, two MS-Exchange
servers, and a Rightfax system covered on our hot-site contract. We do not
use DRM or third party tools; just in-house scripts and well-written
procedures.

Tom Kauffman
NIBCO, Inc


> -Original Message-
> From: Jane Bamberger [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 26, 2002 1:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Disaster Recovery Project
>
>
> HI,
>
> Thanks - and sorry I did not give specific details.
>
> I am AIX 4.3.3 with TSM 4.2.1.9 on and THIN SP2 node with a 3494 Tape
> library. We currently do not have DRM, and are using an
> offsite rotation to
> another building on our hospital campus. We have 2 Alpha
> ES40's, AIX sp
> frame with 7 nodes, 10 Netfinity servers, 23 NT servers, 1 linux, 2
> proliants, 4 Solaris - as you can see - a real mixed bag - so
> any help would
> be appreciated.
>
> Jane
>
> 
> Jane Bamberger
> IS Department
> Bassett Healthcare
> 607-547-4784
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On
> Behalf Of
> George Lesho
> Sent: Tuesday, February 26, 2002 12:56 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Disaster Recovery Project
>
>
> It would be easier to speak to this issue if you had mentioned your
> environment.  I am in an AIX / TSM /DRM environment and we do
> mksysb tapes
> of our production servers and store them offsite. In
> addition, we allow
> TSM/DRM to decide which tapes are needed offsite in the event of a
> disaster. If a disaster occurred, we have contingency servers
> available at
> an offsite location (in case this location no longer exists)
> and we would
> ship copies of the DRM Prepare plan and associated recovery
> files along
> with all DRM (offsite tapes) to this location. We would then
> rebuild the
> servers (including the TSM Server) affected using mksysb
> tapes and then
> reapply production stuff (like Informix databases and
> critical apps) using
> the DRM media.
>
> George Lesho
> AFC Enterprises
>
>
>
>
>
> Jane Bamberger <[EMAIL PROTECTED]>@VM.MARIST.EDU> on
> 02/26/2002
> 11:27:41 AM
>
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
> Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
>
> To:   [EMAIL PROTECTED]
> cc:(bcc: George Lesho/Partners/AFC)
> Fax to:
> Subject:  Disaster Recovery Project
>
> Hi,
>
> I work for a hospital, and was just given the project of
> gathering all the
> information I can about disaster recovery. I would appreciate
> it if I could
> get any sites, information from any of you that have already
> gone down this
> road.
>
> I also would like to here any horror stories, or bad reviews
> about any of
> the major players in DRM. Do any of you use Tivoli DRM,
> Autovault, or any
> other third party software?
>
> I am pretty new to the list - so if this has already been
> hashed over in
> detail - let me know - and I'll go searching!
>
> Thanks,
> Jane
>
>
> 
> Jane Bamberger
> IS Department
> Bassett Healthcare
> 607-547-4784
>

Re: Disaster Recovery Project

[Malbrough, Demetrius]

This is a pretty good site for the basics and to make sure you have all
aspects of the plan together:

http://www.disasterplan.com/yellowpages/Intro.html

Regards,

Demetrius Malbrough

-Original Message-
From: Jane Bamberger [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 26, 2002 11:28 AM
To: [EMAIL PROTECTED]
Subject: Disaster Recovery Project


Hi,

I work for a hospital, and was just given the project of gathering all the
information I can about disaster recovery. I would appreciate it if I could
get any sites, information from any of you that have already gone down this
road.

I also would like to here any horror stories, or bad reviews about any of
the major players in DRM. Do any of you use Tivoli DRM, Autovault, or any
other third party software?

I am pretty new to the list - so if this has already been hashed over in
detail - let me know - and I'll go searching!

Thanks,
Jane



Jane Bamberger
IS Department
Bassett Healthcare
607-547-4784

Re: Disaster Recovery Project

[Braich, Raminder]

Hi Jane,
  We are a NT shop. We do not have DRM either. Currently we make copies of
all the tapes that were written to and ship them offsite. We also make a
copy of TSM database and ship it offsite. Similarly volhist and devconfig
files are written to our west coast servers daily and backed up. In a
disaster we would have servers in a remote location and would need to
restore TSM server and the database from offsite tapes. Then would need to
restore all the production stuff, DB servers, mail server, data server, etc.

Raminder Braich
SAP/ORACLE DBA
The Davey Tree Expert Company
330-673-9515 X270


> -Original Message-
> From: Jane Bamberger [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, February 26, 2002 1:22 PM
> To:   [EMAIL PROTECTED]
> Subject:      Re: Disaster Recovery Project
>
> HI,
>
> Thanks - and sorry I did not give specific details.
>
> I am AIX 4.3.3 with TSM 4.2.1.9 on and THIN SP2 node with a 3494 Tape
> library. We currently do not have DRM, and are using an offsite rotation
> to
> another building on our hospital campus. We have 2 Alpha ES40's, AIX sp
> frame with 7 nodes, 10 Netfinity servers, 23 NT servers, 1 linux, 2
> proliants, 4 Solaris - as you can see - a real mixed bag - so any help
> would
> be appreciated.
>
> Jane
>
> 
> Jane Bamberger
> IS Department
> Bassett Healthcare
> 607-547-4784
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> George Lesho
> Sent: Tuesday, February 26, 2002 12:56 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Disaster Recovery Project
>
>
> It would be easier to speak to this issue if you had mentioned your
> environment.  I am in an AIX / TSM /DRM environment and we do mksysb tapes
> of our production servers and store them offsite. In addition, we allow
> TSM/DRM to decide which tapes are needed offsite in the event of a
> disaster. If a disaster occurred, we have contingency servers available at
> an offsite location (in case this location no longer exists) and we would
> ship copies of the DRM Prepare plan and associated recovery files along
> with all DRM (offsite tapes) to this location. We would then rebuild the
> servers (including the TSM Server) affected using mksysb tapes and then
> reapply production stuff (like Informix databases and critical apps) using
> the DRM media.
>
> George Lesho
> AFC Enterprises
>
>
>
>
>
> Jane Bamberger <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/26/2002
> 11:27:41 AM
>
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
> Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
>
> To:   [EMAIL PROTECTED]
> cc:(bcc: George Lesho/Partners/AFC)
> Fax to:
> Subject:  Disaster Recovery Project
>
> Hi,
>
> I work for a hospital, and was just given the project of gathering all the
> information I can about disaster recovery. I would appreciate it if I
> could
> get any sites, information from any of you that have already gone down
> this
> road.
>
> I also would like to here any horror stories, or bad reviews about any of
> the major players in DRM. Do any of you use Tivoli DRM, Autovault, or any
> other third party software?
>
> I am pretty new to the list - so if this has already been hashed over in
> detail - let me know - and I'll go searching!
>
> Thanks,
> Jane
>
>
> 
> Jane Bamberger
> IS Department
> Bassett Healthcare
> 607-547-4784

Re: Disaster Recovery Project

[George Lesho]

Guess the first thing to do is to figure out which servers would need to be
brought back in the event of a disaster. I back up several dozen servers
but only a couple are needed in the event of a total meltdown in order to
maintain company operational capability (the restore of these servers is
mandated by contract). The next step is to figure out what is needed to
bring each of the required servers back up to a running state quickly. In
our case, the mksysb tapes are all that is required. In your case, there
may be a mixed answer. The DRM part is pretty easy using TSM/DRM as TSM
keeps track of which tapes are needed and also offers a "Prepare" file
which has all the info needed to rebuild the TSM environement (along with a
couple other files like the volume history and hardware stuff).

George Lesho
AFC Enterprises






Jane Bamberger <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/26/2002
12:21:59 PM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:(bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  Re: Disaster Recovery Project

HI,

Thanks - and sorry I did not give specific details.

I am AIX 4.3.3 with TSM 4.2.1.9 on and THIN SP2 node with a 3494 Tape
library. We currently do not have DRM, and are using an offsite rotation to
another building on our hospital campus. We have 2 Alpha ES40's, AIX sp
frame with 7 nodes, 10 Netfinity servers, 23 NT servers, 1 linux, 2
proliants, 4 Solaris - as you can see - a real mixed bag - so any help
would
be appreciated.

Jane


Jane Bamberger
IS Department
Bassett Healthcare
607-547-4784


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
George Lesho
Sent: Tuesday, February 26, 2002 12:56 PM
To: [EMAIL PROTECTED]
Subject: Re: Disaster Recovery Project


It would be easier to speak to this issue if you had mentioned your
environment.  I am in an AIX / TSM /DRM environment and we do mksysb tapes
of our production servers and store them offsite. In addition, we allow
TSM/DRM to decide which tapes are needed offsite in the event of a
disaster. If a disaster occurred, we have contingency servers available at
an offsite location (in case this location no longer exists) and we would
ship copies of the DRM Prepare plan and associated recovery files along
with all DRM (offsite tapes) to this location. We would then rebuild the
servers (including the TSM Server) affected using mksysb tapes and then
reapply production stuff (like Informix databases and critical apps) using
the DRM media.

George Lesho
AFC Enterprises





Jane Bamberger <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/26/2002
11:27:41 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:(bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  Disaster Recovery Project

Hi,

I work for a hospital, and was just given the project of gathering all the
information I can about disaster recovery. I would appreciate it if I could
get any sites, information from any of you that have already gone down this
road.

I also would like to here any horror stories, or bad reviews about any of
the major players in DRM. Do any of you use Tivoli DRM, Autovault, or any
other third party software?

I am pretty new to the list - so if this has already been hashed over in
detail - let me know - and I'll go searching!

Thanks,
Jane



Jane Bamberger
IS Department
Bassett Healthcare
607-547-4784

Re: Disaster Recovery Project

[Jane Bamberger]

HI,

Thanks - and sorry I did not give specific details.

I am AIX 4.3.3 with TSM 4.2.1.9 on and THIN SP2 node with a 3494 Tape
library. We currently do not have DRM, and are using an offsite rotation to
another building on our hospital campus. We have 2 Alpha ES40's, AIX sp
frame with 7 nodes, 10 Netfinity servers, 23 NT servers, 1 linux, 2
proliants, 4 Solaris - as you can see - a real mixed bag - so any help would
be appreciated.

Jane


Jane Bamberger
IS Department
Bassett Healthcare
607-547-4784


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
George Lesho
Sent: Tuesday, February 26, 2002 12:56 PM
To: [EMAIL PROTECTED]
Subject: Re: Disaster Recovery Project


It would be easier to speak to this issue if you had mentioned your
environment.  I am in an AIX / TSM /DRM environment and we do mksysb tapes
of our production servers and store them offsite. In addition, we allow
TSM/DRM to decide which tapes are needed offsite in the event of a
disaster. If a disaster occurred, we have contingency servers available at
an offsite location (in case this location no longer exists) and we would
ship copies of the DRM Prepare plan and associated recovery files along
with all DRM (offsite tapes) to this location. We would then rebuild the
servers (including the TSM Server) affected using mksysb tapes and then
reapply production stuff (like Informix databases and critical apps) using
the DRM media.

George Lesho
AFC Enterprises





Jane Bamberger <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/26/2002
11:27:41 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:(bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  Disaster Recovery Project

Hi,

I work for a hospital, and was just given the project of gathering all the
information I can about disaster recovery. I would appreciate it if I could
get any sites, information from any of you that have already gone down this
road.

I also would like to here any horror stories, or bad reviews about any of
the major players in DRM. Do any of you use Tivoli DRM, Autovault, or any
other third party software?

I am pretty new to the list - so if this has already been hashed over in
detail - let me know - and I'll go searching!

Thanks,
Jane



Jane Bamberger
IS Department
Bassett Healthcare
607-547-4784

Re: Disaster Recovery Project

[George Lesho]

It would be easier to speak to this issue if you had mentioned your
environment.  I am in an AIX / TSM /DRM environment and we do mksysb tapes
of our production servers and store them offsite. In addition, we allow
TSM/DRM to decide which tapes are needed offsite in the event of a
disaster. If a disaster occurred, we have contingency servers available at
an offsite location (in case this location no longer exists) and we would
ship copies of the DRM Prepare plan and associated recovery files along
with all DRM (offsite tapes) to this location. We would then rebuild the
servers (including the TSM Server) affected using mksysb tapes and then
reapply production stuff (like Informix databases and critical apps) using
the DRM media.

George Lesho
AFC Enterprises





Jane Bamberger <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/26/2002
11:27:41 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:(bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  Disaster Recovery Project

Hi,

I work for a hospital, and was just given the project of gathering all the
information I can about disaster recovery. I would appreciate it if I could
get any sites, information from any of you that have already gone down this
road.

I also would like to here any horror stories, or bad reviews about any of
the major players in DRM. Do any of you use Tivoli DRM, Autovault, or any
other third party software?

I am pretty new to the list - so if this has already been hashed over in
detail - let me know - and I'll go searching!

Thanks,
Jane



Jane Bamberger
IS Department
Bassett Healthcare
607-547-4784

Re: disaster recovery

[Remeta, Mark]

We use IBM's Sterling Forest site. We rent floor space and have dedicated
servers running 24-7 there.

Mark


-Original Message-
From: MacMurray, Andrea (CC-ETS Ent Storage Svcs)
[mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 2:26 PM
To: [EMAIL PROTECTED]
Subject: Re: disaster recovery


We are using the IBM side in Gaithersburg and just had a very successful DR
test.
Andrea Mac Murray
Sen. Systems Administrator
ConAgra Foods, Inc.
7300 World Communication Drive
Omaha,NE 68122
Tel: (402) 577-3603
[EMAIL PROTECTED]


-Original Message-
From: Coviello, Paul [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 1:14 PM
To: [EMAIL PROTECTED]
Subject: disaster recovery


HI, we are currently putting together our disaster recovery plan.  I was
wondering what you may use as to any of the disaster services (Sungard,
IBM...) or even your own hotsite? with duplicate equipment.

thanks
Paul

Paul J Coviello
Sr Systems Analyst
Catholic Medical Center
2456 Brown Ave
Manchester, NH 03103
603 663-5326

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Re: disaster recovery

[MacMurray, Andrea (CC-ETS Ent Storage Svcs)]

We are using the IBM side in Gaithersburg and just had a very successful DR
test.
Andrea Mac Murray
Sen. Systems Administrator
ConAgra Foods, Inc.
7300 World Communication Drive
Omaha,NE 68122
Tel: (402) 577-3603
[EMAIL PROTECTED]


-Original Message-
From: Coviello, Paul [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 1:14 PM
To: [EMAIL PROTECTED]
Subject: disaster recovery


HI, we are currently putting together our disaster recovery plan.  I was
wondering what you may use as to any of the disaster services (Sungard,
IBM...) or even your own hotsite? with duplicate equipment.

thanks
Paul

Paul J Coviello
Sr Systems Analyst
Catholic Medical Center
2456 Brown Ave
Manchester, NH 03103
603 663-5326

Re: Disaster Recovery...Has anyone really successfully done testi ng?

[Seay, Paul]

I have seen most of the answers to this question.  However, this may be one
thing you have not considered.  Remember TSM is only going to mount the
tapes it needs once you update the access to the copy pools so that they can
be used to resolve the restores.  It think your issue was you thought you
had to recreate the primary pools before you could do any restores, not so.
As one suggested you may still need to rebuild the primary pools in a real
disaster so that you can start running backups again.  You should probably
test that after you get your stuff restored.  Otherwise, you will only have
one copy of your data unless you have multiple copy pools until you do so.
Think about what you are trying to accomplish from a business point of view,
then whittle it down to something that you can afford.

-Original Message-
From: Cinda Mullen [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 14, 2002 10:37 AM
To: [EMAIL PROTECTED]
Subject: Disaster Recovery...Has anyone really successfully done
testing?


Good Morning All

We are running TSM on OS/390 (Version 4.1.4).  We have approximately 200
NT/UNIX/NETWARE servers and are backing our daily incremental stgpools
to copypools for offsite storage.

It appears the copypools don't just keep the active versions of data,
they keep everythingwe currently have 190+  Storage Tek 9840s
offsite for TSM.  If we go to the hotsite to do Disaster Recovery
Testing, how do we restore these storage pools in a reasonable amount of
time?  Has anyone successfully performed Disaster Recovery?

Our TSM database is 10GB so, I'm also guessing it will take quite a
while to get that restored???  Any ideas, thoughts?

Is anyone using Backupsets instead of copypools for DR?

Thanks!!
Cinda Mullen
Sr. Systems Programmer
Ascension Health ISD
[EMAIL PROTECTED]



NOTE: This e-mail message may contain information that may be privileged,
confidential, and exempt from disclosure.  It is intended for use only by
the person to whom it is addressed. If you have received this message in
error, please do not forward or use this information in any way, delete it
immediately, and contact the sender as soon as possible by the reply option
or by telephone at the telephone number listed (if available).  Thank you.

Re: Disaster Recovery...Has anyone really successfully done testi ng?

[Kauffman, Tom]

The last D/R test we did last year had 340+ DLT tapes -- and we don't have
an atl on the D/R contract, just free-standing drives.

1) restore the TSM environment (os, filesystems, any other cruft required)
2) recover/re-key the device config file to match the D/R site (we keep a
copy on floppy)
3) recover the volhist (same floppy)
4) restore the TSM database from the backup tape (our 6 GB took about 30
minutes from DLT)
5) start up TSM
6) update the device config in the TSM database to match changes in step 2
7) update vol * acce=unav whereaccess=reado,readw (marks all tapes
unavailable if they were in the library)
8) update vol * acce=reado whereacce=of (marks all the off-site tapes
readonly)
9) run your restores from the readonly copypool tapes.

Depending on your D/R goals, this may be good enough. You may have a storage
pool or two you'll want to recreate from the copies

Tom Kauffman
NIBCO Inc

> -Original Message-
> From: Cinda Mullen [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 14, 2002 10:37 AM
> To: [EMAIL PROTECTED]
> Subject: Disaster Recovery...Has anyone really successfully done
> testing?
>
>
> Good Morning All
>
> We are running TSM on OS/390 (Version 4.1.4).  We have
> approximately 200
> NT/UNIX/NETWARE servers and are backing our daily incremental stgpools
> to copypools for offsite storage.
>
> It appears the copypools don't just keep the active versions of data,
> they keep everythingwe currently have 190+  Storage Tek 9840s
> offsite for TSM.  If we go to the hotsite to do Disaster Recovery
> Testing, how do we restore these storage pools in a
> reasonable amount of
> time?  Has anyone successfully performed Disaster Recovery?
>
> Our TSM database is 10GB so, I'm also guessing it will take quite a
> while to get that restored???  Any ideas, thoughts?
>
> Is anyone using Backupsets instead of copypools for DR?
>
> Thanks!!
> Cinda Mullen
> Sr. Systems Programmer
> Ascension Health ISD
> [EMAIL PROTECTED]
>
>
>
> NOTE: This e-mail message may contain information that may be
> privileged,
> confidential, and exempt from disclosure.  It is intended for
> use only by
> the person to whom it is addressed. If you have received this
> message in
> error, please do not forward or use this information in any
> way, delete it
> immediately, and contact the sender as soon as possible by
> the reply option
> or by telephone at the telephone number listed (if
> available).  Thank you.
>

Re: Disaster Recovery...Has anyone really successfully done testi ng?

[Cook, Dwight E (SAIC)]

In this case what you do is
1) bring up yout tsm environment
2) put all your copypool tapes into the atl
3) check them all in
4) do an "UPD VOL * ACC=UNAVAIL WHERESTG=yourprimarypool"
might need to make that acc=destroyed...
then any restore request that comes in will automatically pull the info from
the copypool volume
won't technically need to restore the primary pools... ;-)

Dwight

PS a 10GB db won't be very bad on a restore...
an hour or so... and you will spend more time than that putting the
tapes into an atl !



-Original Message-
From: Cinda Mullen [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 14, 2002 9:37 AM
To: [EMAIL PROTECTED]
Subject: Disaster Recovery...Has anyone really successfully done
testing?


Good Morning All

We are running TSM on OS/390 (Version 4.1.4).  We have approximately 200
NT/UNIX/NETWARE servers and are backing our daily incremental stgpools
to copypools for offsite storage.

It appears the copypools don't just keep the active versions of data,
they keep everythingwe currently have 190+  Storage Tek 9840s
offsite for TSM.  If we go to the hotsite to do Disaster Recovery
Testing, how do we restore these storage pools in a reasonable amount of
time?  Has anyone successfully performed Disaster Recovery?

Our TSM database is 10GB so, I'm also guessing it will take quite a
while to get that restored???  Any ideas, thoughts?

Is anyone using Backupsets instead of copypools for DR?

Thanks!!
Cinda Mullen
Sr. Systems Programmer
Ascension Health ISD
[EMAIL PROTECTED]



NOTE: This e-mail message may contain information that may be privileged,
confidential, and exempt from disclosure.  It is intended for use only by
the person to whom it is addressed. If you have received this message in
error, please do not forward or use this information in any way, delete it
immediately, and contact the sender as soon as possible by the reply option
or by telephone at the telephone number listed (if available).  Thank you.

Re: Disaster Recovery...Has anyone really successfully done testi ng?

[Jeff Bach]

That is long restore ... 2 years. :)

Jeff Bach

> -Original Message-
> From:   [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, January 14, 2002 10:02 AM
> To:   [EMAIL PROTECTED]
> Subject:      Re: Disaster Recovery...Has anyone really successfully done
> testing?
>
> I've been successfully restoring at DR using TSM for two years. The TSM db
> recovery of your size should take only about 15 minutes. Check how long
> its
> taking to back it up, it should take just a little longer to recover if
> you
> have the same hardware.
> You really don't restore the tape storage pools just bring you copy
> storage
> pools to the test.
> I too see the same problems you see though. My clients are complaining
> that
> we have to vault so many tapes because we keep all the versions for DR
> also.
> I wish there was a way to tell DRM to only keep maybe 3 of the latest
> versions of my on-site pools.
> Its one of my projects this year to find a way to do Disaster Recovery
> using less tape. maybe backupsets is the answer.
>
>
>
>
> "Cinda Mullen" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/14/2002
> 10:36:35 AM
>
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
> Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>
>
> To:   [EMAIL PROTECTED]
> cc:
>
> Subject:  Disaster Recovery...Has anyone really successfully done testing?
>
>
> Good Morning All
>
> We are running TSM on OS/390 (Version 4.1.4).  We have approximately 200
> NT/UNIX/NETWARE servers and are backing our daily incremental stgpools
> to copypools for offsite storage.
>
> It appears the copypools don't just keep the active versions of data,
> they keep everythingwe currently have 190+  Storage Tek 9840s
> offsite for TSM.  If we go to the hotsite to do Disaster Recovery
> Testing, how do we restore these storage pools in a reasonable amount of
> time?  Has anyone successfully performed Disaster Recovery?
>
> Our TSM database is 10GB so, I'm also guessing it will take quite a
> while to get that restored???  Any ideas, thoughts?
>
> Is anyone using Backupsets instead of copypools for DR?
>
> Thanks!!
> Cinda Mullen
> Sr. Systems Programmer
> Ascension Health ISD
> [EMAIL PROTECTED]
>
>
>
> NOTE: This e-mail message may contain information that may be privileged,
> confidential, and exempt from disclosure.  It is intended for use only by
> the person to whom it is addressed. If you have received this message in
> error, please do not forward or use this information in any way, delete it
> immediately, and contact the sender as soon as possible by the reply
> option
> or by telephone at the telephone number listed (if available).  Thank you.


**
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed.  If you have received this email
in error destroy it immediately.
**

Re: Disaster Recovery...Has anyone really successfully done testing?

I've been successfully restoring at DR using TSM for two years. The TSM db
recovery of your size should take only about 15 minutes. Check how long its
taking to back it up, it should take just a little longer to recover if you
have the same hardware.
You really don't restore the tape storage pools just bring you copy storage
pools to the test.
I too see the same problems you see though. My clients are complaining that
we have to vault so many tapes because we keep all the versions for DR
also.
I wish there was a way to tell DRM to only keep maybe 3 of the latest
versions of my on-site pools.
Its one of my projects this year to find a way to do Disaster Recovery
using less tape. maybe backupsets is the answer.




"Cinda Mullen" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/14/2002
10:36:35 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:

Subject:  Disaster Recovery...Has anyone really successfully done testing?


Good Morning All

We are running TSM on OS/390 (Version 4.1.4).  We have approximately 200
NT/UNIX/NETWARE servers and are backing our daily incremental stgpools
to copypools for offsite storage.

It appears the copypools don't just keep the active versions of data,
they keep everythingwe currently have 190+  Storage Tek 9840s
offsite for TSM.  If we go to the hotsite to do Disaster Recovery
Testing, how do we restore these storage pools in a reasonable amount of
time?  Has anyone successfully performed Disaster Recovery?

Our TSM database is 10GB so, I'm also guessing it will take quite a
while to get that restored???  Any ideas, thoughts?

Is anyone using Backupsets instead of copypools for DR?

Thanks!!
Cinda Mullen
Sr. Systems Programmer
Ascension Health ISD
[EMAIL PROTECTED]



NOTE: This e-mail message may contain information that may be privileged,
confidential, and exempt from disclosure.  It is intended for use only by
the person to whom it is addressed. If you have received this message in
error, please do not forward or use this information in any way, delete it
immediately, and contact the sender as soon as possible by the reply option
or by telephone at the telephone number listed (if available).  Thank you.

Re: disaster recovery

[Joe Cascanette]

I have been working on a solution for this. We are switching from magstar
tapes to DLT tapes in the near future. I have been looking into the option
of BACKUPSETS. From what I can see, when I create a BACKUPSET and store
these on separate DLT tapes (for DRP purposes), you should be able to setup
the servers with a DLT unit attached , and be able to  perform a restore
(will be testing Bare Metal Restores when the unit comes in next week) of
that server without waiting for the recreation of your TSM server. Of course
you will still need to recreate the TSM server, DB restore, etc. to perform
incremental restores (depending on the BACKUPSETS date), however this can be
done while the DRP servers are being restored with the BACKUPSETS.

Any thoughts on this plan would be greatly appreciated.

Joe Cascanette
The Cumis Group

-Original Message-
From: Wu, Jie [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 18, 2001 4:58 PM
To: [EMAIL PROTECTED]
Subject: disaster recovery


we are thinking of a better disaster recovery plan. Right now we have one
TSM server. We back up db and primary stgpool and send the tapes to a vault
for disaster recovery purpose. Based on our current environment, the
recovery steps basicly would be:
1. aquire new hardware and install OS and TSM
2. apply TSM server recovery procedures, including formatting log,
db volumes, db restore, etc.
This plan takes relatively long time and we want to purchase a standby TSM
server(with OS, TSM software, tape library, and everything) for a speedy
recovery. The question is "do we still need to go through the TSM server
recovery procudures?", which may take long time. Will server-to-server
configuration helps?

Thanks.

JiePs - I would also like to say that my heart goes out to all those people
directly and indirectly affected by yesterday's tragic events. Saddened
beyond belief.

Re: Disaster Recovery Question

[Steve Harris]

Hi Mark,

Just ideas, I haven't tried  this, but ...
How about defining your default DB backup to be on virtual volumes at the offsite 
location.
Run a full backup at a convenient time when there's not much activity, and then daily 
incrementals.
Run a db snapshot daily to local media.

Alternatively,

Run db backup or snapshot to local disk, then compress - gzip compresses db backups 
about 10 to 1,  then move offsite by ftp or whatever

Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia

>>> "Remeta, Mark" <[EMAIL PROTECTED]> 19/10/2001 4:00:26 >>>
Hello everyone. We are in the position to possibly have a T-1 between our
offices and our hot site and the question has come up how to utilize the T-1
to make disaster recovery quicker. The easy answer is to backup the database
to the hot site but the size of our database ~~24gb makes that impractible.
I was wondering if anyone else out there has a similar setup and how they
are using it. Any information would be appreciated.

Thanks in advance,

Mark Remeta
Seligman Data Corp.
100 Park Avenue
New York, NY 10017


Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.



**
This e-mail, including any attachments sent with it, is confidential 
and for the sole use of the intended recipient(s). This confidentiality 
is not waived or lost if you receive it and you are not the intended 
recipient(s), or if it is transmitted/ received in error.  

Any unauthorised use, alteration, disclosure, distribution or review 
of this e-mail is prohibited.  It may be subject to a statutory duty of 
confidentiality if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this 
e-mail in error, you are asked to immediately notify the sender by 
telephone or by return e-mail.  You should also delete this e-mail 
message and destroy any hard copies produced.
**

Re: Disaster Recovery Manager

[Zlatko Krastev/ACIT]

Look Chapter 9 of SG24-4877-02Tivoli Storage Management Concepts

Zlatko Krastev
IT Consultant





Pétur Eyþórsson <[EMAIL PROTECTED]> on 26.09.2001 12:16:09
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:Disaster Recovery Manager

Hi guys

I have been searching for White Papers, Redbooks or Tivoli Manuals about 
DRM

And i cant seem to find mutch the only thing i found was this

and old Redbook: ADSM Client Disaster Recovery - Bare Metal
and this book on the tivoli web page:  Tivoli Disaster Recovery Manager, 
S/390 Edition 

Does anyone know about any other documents than this.



Kvedja/Regards
Petur Eythorsson
Taeknimadur/Technician
Kerfisfraedingur IR
Tivoli Storage Manager Certified Professional
Microsoft Certified System Engineer
Nyherji HfSimi TEL: +354-569-7700
Borgartun 37   105 Iceland
URL:http://www.nyherji.is

Re: Disaster Recovery Manager

[Joshua S. Bassi]

Take a look at the "TSM Administrator's Guide" for whatever version of
the TSM server you happen to be running.


--
Joshua S. Bassi
Independent IT Consultant
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (408)&(831) 332-4006
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Pétur Eyþórsson
Sent: Wednesday, September 26, 2001 5:16 AM
To: [EMAIL PROTECTED]
Subject: Disaster Recovery Manager

Hi guys

I have been searching for White Papers, Redbooks or Tivoli Manuals about
DRM

And i cant seem to find mutch the only thing i found was this

and old Redbook: ADSM Client Disaster Recovery - Bare Metal
and this book on the tivoli web page:  Tivoli Disaster Recovery Manager,
S/390 Edition 

Does anyone know about any other documents than this.



Kvedja/Regards
Petur Eythorsson
Taeknimadur/Technician
Kerfisfraedingur IR
Tivoli Storage Manager Certified Professional
Microsoft Certified System Engineer
Nyherji HfSimi TEL: +354-569-7700
Borgartun 37   105 Iceland
URL:http://www.nyherji.is

Re: Disaster Recovery and other questions

[Maurice van 't Loo]

Q1:
You need two files also, the devconf and volhist files. In the devconf are
discriptions of the hardwareconfigurations and in the volhist is a list of
the usage of tapes (you can see it with q volhist).
So you can backup these files to floppy or email it to somewhere out of the
building.

Without the volhist, you need to know witch tape is the dbbackup or try them
all :-)

Q2:
I'm not experienced... with DRM ;-) 

Greetings,
   Maurice van 't Loo
   Compare Computers
   The Netherlands

- Original Message -
From: "Wouter V" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 05, 2001 4:08 PM
Subject: Disaster Recovery and other questions


> Hello my dear TSM friends,

*** cut ***

> This works all OK, but if my TSM DB becomes larger than the capacity of my
> internal tapestreamer I will have a problem.
> That's the reason for the following question :
>
> I've seen that some of you do a db backup to a seperate tape in the
library,
> but :
>
> Question 1:
>
>If everything is destroyed (machine and library), and you didn't buy
DRM
> (so you don't have a script
>created by DRM to put everything back from scratch), how do you read
your
> DB back from tape ??? You need at least your
>TSM DB to restore your offsite copy.  Or do you completely reinstall
your
> OS and reinstall TSM ? I almost
>can't believe the last thing because you still lost all the pointers to
> your data on the offsite copy.
>Or is there a way to read that tape directly from your OS through the
> special device name ?  (for example
>tar xvf /dev/rmt3 ??)
>
> Question 2:
>
>Are there any rules to choose the exact size of the components in a TSM
> Server ?
>For example :- 25 Mb. RAM for each backupclient
> - TSM DB size = 10 % of totalcapacity to
backup
> - CPU : ???
>
> Question 3:
>
>  - Can the experienced DSM'ers tell me some special advices ?  What
> beginnermistakes did you guys made (and should I avoid)
>  - What important reports can I make (I made a daily report to see if all
> the schedules were finished completely, and
>one monthly report to see how many times all the portables were backed
> up) ?
>  - Any advices, tips, tricks ?
>

Re: Disaster Recovery - Question

[Prather, Wanda]

Not entirely true - you can start multiple restore sessions for a client.


Doesn't make sense for small clients with only one disk, but for your larger
NT clients with multiple disks, or your AIX clients with multiple file
systems, there is no reason at all not to open multiple TSM windows and
start multiple restores, up until you exceed your throughput capacity.

That's one of the reasons some people collocate by file space...you can
restore the file spaces in parallel.

-Original Message-
From: Maurice van 't Loo [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 15, 2001 5:52 PM
To: [EMAIL PROTECTED]
Subject: Re: Disaster Recovery - Question


Don't forget that you restore serial, for one client there is only one
restore session, so also 1 tapedrive is needed.
You can save time when you can use collocation, but it takes more tapes; up
to 90 tapes in your case.

So, you can only save time when you need to restore more than 6 clients at
the same time.
An other help could be to use the money for the 14 drives to buy disks and
make a very large diskpool, so you can use caching. All data goes to tape,
but stays also in the diskpool, when you need a restore, this will save A
LOT of time when you have enough network bandwidth.

Good luck,
  Maurice van 't Loo
  The Netherlands

- Original Message -
From: "Pearson, Dave" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 15, 2001 10:32 PM
Subject: Disaster Recovery - Question


> Hi ,
>
> I have a couple of questions about your Disaster Recovery Plan,
> How much parallelism does TSM recovery have.  How many tape drives do you
> use for this plan?
> We have 6 tape drives (3494 tape library with 3590 tape drive). We have
> about 90 clients on TSM (AIX, NT, SUN)
> Could we use 20 tape drive to recover all the clients in a shorter time
then
> just have 6 tape drive and take a looong time to do the recovery?
>
> Is anyone using Lanless backup on a server with the fibre network? How is
> this working for you?
>
> Thanks for you help
>
> Dave Pearson
>

Re: Disaster Recovery - Question

[Maurice van 't Loo]

Don't forget that you restore serial, for one client there is only one
restore session, so also 1 tapedrive is needed.
You can save time when you can use collocation, but it takes more tapes; up
to 90 tapes in your case.

So, you can only save time when you need to restore more than 6 clients at
the same time.
An other help could be to use the money for the 14 drives to buy disks and
make a very large diskpool, so you can use caching. All data goes to tape,
but stays also in the diskpool, when you need a restore, this will save A
LOT of time when you have enough network bandwidth.

Good luck,
  Maurice van 't Loo
  The Netherlands

- Original Message -
From: "Pearson, Dave" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 15, 2001 10:32 PM
Subject: Disaster Recovery - Question


> Hi ,
>
> I have a couple of questions about your Disaster Recovery Plan,
> How much parallelism does TSM recovery have.  How many tape drives do you
> use for this plan?
> We have 6 tape drives (3494 tape library with 3590 tape drive). We have
> about 90 clients on TSM (AIX, NT, SUN)
> Could we use 20 tape drive to recover all the clients in a shorter time
then
> just have 6 tape drive and take a looong time to do the recovery?
>
> Is anyone using Lanless backup on a server with the fibre network? How is
> this working for you?
>
> Thanks for you help
>
> Dave Pearson
>

Re: Disaster Recovery - Question

[Alex Paschal]

Well, I've never had the resources to try this, but it might work.  Contract
for bucket loads of disk at your disaster site, enough to restore your
critical nodes' primary pool, and restore the copypool to the diskpool using
the maxpr switch to get multiple processes to speed the restore.
Noncritical nodes can wait on tapes.  Your critical nodes can then restore
quickly and simultaneously from disk.

Note, if anybody has the funds for that, please don't tell me as it would
make me too darned jealous.  Any thoughts on feasability, other than cost?

Alex

-Original Message-
From: Lindsay Morris [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 15, 2001 1:33 PM
To: [EMAIL PROTECTED]
Subject: Re: Disaster Recovery - Question


If you have 20 tape drives, and you're trying to recover many clients,
you'll probably run into this:
Restore of system A has tape volume 0001 mounted;
Restore of System B ALSO needs volume 0001, so it hangs.

If you collocate your copy pool, this shouldn't happen.  But collocating
your copy pool is not recommmended.
Anyone have a good solution for this problem?


> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Pearson, Dave
> Sent: Wednesday, August 15, 2001 4:32 PM
> To: [EMAIL PROTECTED]
> Subject: Disaster Recovery - Question
>
>
> Hi ,
>
> I have a couple of questions about your Disaster Recovery Plan,
> How much parallelism does TSM recovery have.  How many tape drives do you
> use for this plan?
> We have 6 tape drives (3494 tape library with 3590 tape drive). We have
> about 90 clients on TSM (AIX, NT, SUN)
> Could we use 20 tape drive to recover all the clients in a
> shorter time then
> just have 6 tape drive and take a looong time to do the recovery?
>
> Is anyone using Lanless backup on a server with the fibre network? How is
> this working for you?
>
> Thanks for you help
>
> Dave Pearson
>

"WorldSecure " made the following
 annotations on 08/15/01 14:28:10
--

[INFO] -- Content Manager:
The information contained in this communication is confidential and intended solely 
for the use of the individual to whom it is addressed and others authorized to receive 
it.  If you are not the intended recipient, any disclosure, copying, distribution or 
taking of any action in reliance on the contents of this information is prohibited. If 
you have received this communication in error, please immediately notify the sender by 
phone if possible or via email message.

==

Re: Disaster Recovery - Question

[Lindsay Morris]

If you have 20 tape drives, and you're trying to recover many clients,
you'll probably run into this:
Restore of system A has tape volume 0001 mounted;
Restore of System B ALSO needs volume 0001, so it hangs.

If you collocate your copy pool, this shouldn't happen.  But collocating
your copy pool is not recommmended.
Anyone have a good solution for this problem?


> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Pearson, Dave
> Sent: Wednesday, August 15, 2001 4:32 PM
> To: [EMAIL PROTECTED]
> Subject: Disaster Recovery - Question
>
>
> Hi ,
>
> I have a couple of questions about your Disaster Recovery Plan,
> How much parallelism does TSM recovery have.  How many tape drives do you
> use for this plan?
> We have 6 tape drives (3494 tape library with 3590 tape drive). We have
> about 90 clients on TSM (AIX, NT, SUN)
> Could we use 20 tape drive to recover all the clients in a
> shorter time then
> just have 6 tape drive and take a looong time to do the recovery?
>
> Is anyone using Lanless backup on a server with the fibre network? How is
> this working for you?
>
> Thanks for you help
>
> Dave Pearson
>

Re: Disaster recovery - unable to restore

[Kauffman, Tom]

My backup script runs a brarchive run followed by selective backups of
/oracle/SID/saparch and /oracle/SID/sapbackup after the brbackup completes.

In addition, to speed up the PIT restore of some of the SAP directories, I
run an archive run every Sunday of all the non-database filesystems to the
management classes (two copies) I use for the redo logs. At the D/R site we
retrieve the archives, run a PIT restore of /usr/sap/SID,
/oracle/SID/sapbackup, and /oracle/SID/saparch. Then we use backfm to pull
down the most current .anf or .aff for the backup and .svd for the redo
logs.

We've never run into the 'bad format' error. OTOH, the documentation for
backint does imply using TSM to capture these logs.

Tom Kauffman
NIBCO, Inc

> -Original Message-
> From: Praveen Kumar [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 29, 2001 5:12 AM
> To: [EMAIL PROTECTED]
> Subject: Disaster recovery - unable to restore
>
>
> Hi all,
>
> We are having SAP 40B with Oracle 8.0.x as database. OS is solaris 7.
> We installed TSM 4.1 and TDP for SAP R/3 2.7 for backup.
> Backup is working
> without any problem. My problem is in restoring my production
> server backup
> onto the disaster recovery server.
>
> To restore the backup onto the disaster recovery server,
> first i have to
> restore the summary and detailed backup logs. I am restoring
> these two files
> using backfm utility of TDP. Then to start actual Oracle database
> restoration we are using brrestore utility of SAP. While starting the
> brrestore, it terminates after the selection of perticuler
> backup, with an
> error saying "bad format in detail BRBACKUP log file, filename
> /oracle/SID/sapbackup/bdfpmgin.anf". If i copy detailed
> backup log from
> production server to DRServer, restoration starts without any
> problem. After
> comparing backup logs restored from tapeloader and the ones
> from production
> server, we found that the detailed backup log restored from
> tapeloader is
> incomplete. Because backup of detailed log is happening not
> at the end of
> the SAP backup process. After the actual datafile backup, TDP
> is backing up
> SAP logs and profiles. During the backup of these logs and
> profiles, TDP
> backs up detailed log first and then backs up summary log,
> .ora, .sap, .utl
> files. So the detailed backup log doesn't contain complete
> backup info.
>
> The one way to solve this problem is by backing up summary
> log and detailed
> log using dsmc selective command after the completion of SAP
> backup. Is
> there any other methods to get rid of this problem.
>
> Thanks in advance
> Regards
>
> Pavikumar
>
>
> __
> ___
> Get Your Private, Free E-mail from MSN Hotmail at
http://www.hotmail.com.

Re: Disaster recovery - unable to restore

[Nicholas Cassimatis]

I had an older setup (when it was still called Backint), and ran the
incremental backups of the SAP system as the last command in the brbackup
script.  Basically the same as you're suggesting with the selective backup,
and it worked.  3 DR tests of this install under our belt, all 3
successful, so it at least works.  I don't know if there's a better way or
not.

Nick Cassimatis
[EMAIL PROTECTED]

Today is the tomorrow of yesterday.

Re: Disaster Recovery Plan

[Mark Stapleton]

"Rosetti, Bill" wrote:
> I am using TSM 4.1.1 with Disaster Recovery.  I have DR generating local
> plans (writing them to a file on an NFS mounted file system).  I have two
> questions.
>
> 1.  I have entered both the TSM server and node information in the DR module
> and established all the relationships.  How come there is no info about the
> nodes in the DR plan?

The node information is embedded in the database. In fact, the only data
that DR uses that resides outside the database (volhist and devconfig)
are only preserved outside of the database in the prepare statement is
that the database is not usable unless volhist and devconfig are
available before accessing the database.

--
Mark Stapleton ([EMAIL PROTECTED])

Re: Disaster Recovery Plan

[Thomas Denier]

Quoting "Rosetti, Bill" <[EMAIL PROTECTED]>:

> 2.  Any time I query TSM about a plan file I get no results returned.
> This
> includes querying rpfilecontents and volhist.  Is that the way it is
> supposed to work when you store the plans locally?

Yes, the documentation for both commands states that they only support
recovery plans that were sent to another TSM server.

Re: Disaster Recovery

[Kauffman, Tom]

My quick and dirty approach to the tape checkin issue --

1) mark all tapes in the old library (back home) as 'unavailable'. I do this
by storage pool - "upd vol * acce=unav wherestg=aix-cart" (I have 10 storage
pools I do this for).

2) mark all off-site tapes as read-only. "upd vol * acce=reado whereacce=of"

We currently run a 'manual' library at D/R, so this is all that is required.
If you have a true automated library, follow up with a 'checkin libv
 search=yes stat=pri checklabel=barcode". And then, after the
assorted restores are going, worry about setting up scratch tapes, admin
schedules, and such like (I tend to blow away all schedules as soon as I get
ADSM up, and then add them back in when I'm ready for them).

Tom Kauffman
NIBCO, Inc.

> -Original Message-
> From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 22, 2000 10:13 AM
> To: [EMAIL PROTECTED]
> Subject: Disaster Recovery
>
>
> Hi all ,
>   Completed Disaster Recovery Test successfully at Sungurad
> Philadelphia
> yesterday.
> i was   going through following steps , and encountered some
> problems ,
>   I restored TSM database and log
>   updated all  tapepool volumes as destroyed ,
>
> loaded all copypool volumes in STk9710 , after this when i
> started restoring
> oracle database
> in actlog   TSM was asking to checkin volumes  A1234 .   this
> process was so
> time consuming ,
> if one has 100 copypool tapes , do they need to checkin first
> ? can`t TSM
> checkin them as private ?
> even if i am using DRM module , lot of steps i was doing
> manually , DRM scripts
> only helps you to
> 1  format log and  DB volumes , restore database , register  license ,
> but did not update any volumes as destroyed .. neither checkin process
> Anyhow i started  at 8.00 .AM  and finished   by 3:00 AM ..
> was using 10 DLT
> drives
> in STK9710 . out of 2 gone bad after sometime  : -)
> Thanks to Chris Wikham , as her tips were useful , like STK
> Library Microcode
> ver .
> Hotline phone Nos. (Without this  ACSLS was not working ).
> thanks everybody who provided inputs for the same.
> Also  passed the Tivoli Cert Test on 14 OF December .
>
>
> Shekhar Dhotre
> IBM certified AIX specialists
> IBM certified RS/6000 SP Admin .
> Microsoft Certified Systems Engg.
> Tivoli Certified  Consultant 4.1 ( 14 December 2000)
> [EMAIL PROTECTED]
>
> 508-359-3872
>
> "Winner never quits, Quitter never wins "
>

Re: Disaster Recovery Test.

[Christine Wickham]

I would definitely let Sungard know what version you are at as soon as you can.
This way,
when they set up the equipement the day/night before your test they should get
the library
at the right version.

Best of luck.
Chris




"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 10/02/2000 12:04:39 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: Disaster Recovery Test.

Hi Chris ,
I  am writing shell and awk scripts to create file  volume groups, logical
volumes , and file systems .
our stk library microcode is 1.01 , so do i need to tell sunGuard , to update
there STK library code to be at same level ?


> Steps to recreate File systems after restoring from mksysb.
>
> Step0 : Clean all ODM entries, check all hdisk's are in available state.
> exportvg oracle8vg
> lspv
>
> # Step1 : Create VG , 32MB PP size.
> mkvg -f -y'oracle8vg' -s'32' hdisk2 hdisk3 hdisk4 hdisk5 hdisk6 hdisk8
> varyonvg oracle8vg
>
> # Step2 : Create LV , 10PP's and 2 copies of each ,  (check the  size and
> write in terms of PP's)
>
> mklv -y'ora01' -c'2' oracle8vg 10
>
> #Step3 : Create JFS on LV, With all default values.
>
> crfs -v jfs -d'ora01' -m'/ora01' -A''`locale yesstr | awk -F: '{print \
> $1}'`'' -p'rw' -t''`locale nostr | awk -F: '{print $1}'`'' -a frag='40 \
> 96' -a nbpi='4096' -a ag='8'
>
> #step4 : after creation of fs, mount it.
> mount /ora1
>
> #Step5 : Repeat step 2 to 4 for all file systems. e.g.
> mklv -y'ora02' -c'2' oracle8vg 10
> crfs -v jfs -d'ora02' -m'/ora02' -A''`locale yesstr | awk -F: '{print \
> $1}'`'' -p'rw' -t''`locale nostr | awk -F: '{print $1}'`'' -a frag='40 \
> 96' -a nbpi='4096' -a ag='8'
> mount /ora2
>
> #Step6 : Repeat step1 to step5 for all VG's
>
> #Step7 : Restore Data , using  Tivoli .


awk command is just to create file system
which can be replaced with.

crfs -v jfs -d'ora01' -m'/ora01' -A yes -p rw -t no -a frag=4096 -a
nbpi=4096 -a ag=8






"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 09/27/2000 01:18:31 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: Disaster Recovery Test.

I would make several recommendations, having done this twice so far this year.

Take blank tapes of all media you might use (ie, 8mm for AIX mksysbs, DLT for
the library, etc). While
you're at it, take cleaning tapes too. We had our own, and used several of
them. By the time Sungard
found their cleaning tapes, we had already cleaned the drives and moved on.
Create your volume group creation scripts ahead of time and stick them in the
mksysb/savevg or bring
them on a floppy. Sungard is supposed to tell you what equipment you will have.
They gave us 4.5 GB
SSA drives,which differs from what we have on site (a mix of 9.1 and 4.5 GB
SSA). The scripts we used
at Sungard differed greatly from the ones used to create the vgs at home.
Create a detailed plan (more than what you've got here) that lists all steps
with commands included. This way,
when you are tired or distracted after a long day, you don't have to go on
memory.  We took pages of
documetation to the first test, and refined it for the second test, adding in
all the steps we hadn't thought
of before (like exporting all the volumegroups so that when they are recreated,
there aren't any conflicts in
/etc/filesystems).
If possible bring your own command reference manuals and the ADSM manuals.
Sungard only has
hardware documentation, and they don't provide access to the internet.  While
we were at Sungard
our remote dial in system was down for a period of time, stranding us from the
online docs (we did
have hard copies).
Know what version of the firmware your STK library is running. If possible,
have your STK engineer
give you a duplicate copy to bring with you. We spent 11 hours attempting to
getACSLS running
and the problem turned out to be the library was at the wrong version of
firmware. TheSTK onsite
guys weren't much help. It took a hotline product engineer to figure it out.
Of course, bring all the hotline phone numbers and site numbers.
Bring a picture of how everything is to be set up (send it ahead if you can). A
picture is worth a
thousand words when attempting to get the equipment in the right place, and
connected up properly.
When you get there, go over all the hardware and connections. We were suprised
by the fact that
our server couldn't communicate

Re: Disaster Recovery Test.

[Shekhar Dhotre]

Hi Chris ,
I  am writing shell and awk scripts to create file  volume groups, logical
volumes , and file systems .
our stk library microcode is 1.01 , so do i need to tell sunGuard , to update
there STK library code to be at same level ?


> Steps to recreate File systems after restoring from mksysb.
>
> Step0 : Clean all ODM entries, check all hdisk's are in available state.
> exportvg oracle8vg
> lspv
>
> # Step1 : Create VG , 32MB PP size.
> mkvg -f -y'oracle8vg' -s'32' hdisk2 hdisk3 hdisk4 hdisk5 hdisk6 hdisk8
> varyonvg oracle8vg
>
> # Step2 : Create LV , 10PP's and 2 copies of each ,  (check the  size and
> write in terms of PP's)
>
> mklv -y'ora01' -c'2' oracle8vg 10
>
> #Step3 : Create JFS on LV, With all default values.
>
> crfs -v jfs -d'ora01' -m'/ora01' -A''`locale yesstr | awk -F: '{print \
> $1}'`'' -p'rw' -t''`locale nostr | awk -F: '{print $1}'`'' -a frag='40 \
> 96' -a nbpi='4096' -a ag='8'
>
> #step4 : after creation of fs, mount it.
> mount /ora1
>
> #Step5 : Repeat step 2 to 4 for all file systems. e.g.
> mklv -y'ora02' -c'2' oracle8vg 10
> crfs -v jfs -d'ora02' -m'/ora02' -A''`locale yesstr | awk -F: '{print \
> $1}'`'' -p'rw' -t''`locale nostr | awk -F: '{print $1}'`'' -a frag='40 \
> 96' -a nbpi='4096' -a ag='8'
> mount /ora2
>
> #Step6 : Repeat step1 to step5 for all VG's
>
> #Step7 : Restore Data , using  Tivoli .


awk command is just to create file system
which can be replaced with.

crfs -v jfs -d'ora01' -m'/ora01' -A yes -p rw -t no -a frag=4096 -a
nbpi=4096 -a ag=8






"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 09/27/2000 01:18:31 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: Disaster Recovery Test.

I would make several recommendations, having done this twice so far this year.

Take blank tapes of all media you might use (ie, 8mm for AIX mksysbs, DLT for
the library, etc). While
you're at it, take cleaning tapes too. We had our own, and used several of
them. By the time Sungard
found their cleaning tapes, we had already cleaned the drives and moved on.
Create your volume group creation scripts ahead of time and stick them in the
mksysb/savevg or bring
them on a floppy. Sungard is supposed to tell you what equipment you will have.
They gave us 4.5 GB
SSA drives,which differs from what we have on site (a mix of 9.1 and 4.5 GB
SSA). The scripts we used
at Sungard differed greatly from the ones used to create the vgs at home.
Create a detailed plan (more than what you've got here) that lists all steps
with commands included. This way,
when you are tired or distracted after a long day, you don't have to go on
memory.  We took pages of
documetation to the first test, and refined it for the second test, adding in
all the steps we hadn't thought
of before (like exporting all the volumegroups so that when they are recreated,
there aren't any conflicts in
/etc/filesystems).
If possible bring your own command reference manuals and the ADSM manuals.
Sungard only has
hardware documentation, and they don't provide access to the internet.  While
we were at Sungard
our remote dial in system was down for a period of time, stranding us from the
online docs (we did
have hard copies).
Know what version of the firmware your STK library is running. If possible,
have your STK engineer
give you a duplicate copy to bring with you. We spent 11 hours attempting to
getACSLS running
and the problem turned out to be the library was at the wrong version of
firmware. TheSTK onsite
guys weren't much help. It took a hotline product engineer to figure it out.
Of course, bring all the hotline phone numbers and site numbers.
Bring a picture of how everything is to be set up (send it ahead if you can). A
picture is worth a
thousand words when attempting to get the equipment in the right place, and
connected up properly.
When you get there, go over all the hardware and connections. We were suprised
by the fact that
our server couldn't communicate on the network. Turns out there was an extra FE
adapter in the
server (not at our request) and that was what they had hooked up.

Hope this helps.
-Chris Wickham
Bayer Corp, Pharma Division




"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 09/27/2000 09:46:17 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Disaster Recovery Test.

Hi all , going for firstever DR test 

Re: Disaster Recovery Test.

[Shekhar Dhotre]

Matt,
For restoring TSM database   ,manually place the database volume in the
automated library  and note the element no.
Where you placed the database  volume ,   then update the comments in the
device configuration file. to identify location of those volumes.
for more information see : Admin Guide  page  787 ,789.
your libraries elements nos.  can be found on Tivoli`s web site
http://www.tivoli.com/support/storage_mgr/devices_latest

shekhar






"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 09/27/2000 02:18:43 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: Disaster Recovery Test.

Shekar,

When you do the restore of the database with a 9710, how does TSM
know or find the location of the dbbackup volume inside the silo? Do you do
a manual type restore first with the tape in the drive or is TSM capable of
finding that volume inside the silo with the silo defined in the dev.conf
file?, even though it might not be in the same cell location when the last
dbbackup was done.  I am getting ready to do a BRS test of our 9710
connected to an R50 via F/W Diff SCSI cards.  Thanks

Matt Long
Systems Administration
Marriott International


-Original Message-
From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 27, 2000 9:45 AM
To: [EMAIL PROTECTED]
Subject: Disaster Recovery Test.


Hi all , going for firstever DR test at Sunguard ,
here is what i have collected  for test .

1. mksysb tapes .
2.  TSM database tapes , and  all offsite (copypool tapes).
3. savevg of tsm  (i have a volume group called tsm  for tivoli)
4. disaster recovery plan file  (hard copy and soft copy , sample awk script
to
break it down.)
5. ACSLS is configured on Sun so , for the same ufsdump tapes
6. AIX , SUn Slorais , and ACSLS , installation media .
7. out puts of lsvg, lsvg -l vgnames , df , lsdev- Cc disks , lsdev- Cc
tape,
lscfg , lsattr -El mem0 , lsps -a , lsattr -El en0.
   same for the sun .out put of dsm.sys , dsm.opt ,dsmserv.opt  I know
they
will be in rootvg ,but precaution is better than cure   :-)
8. chapter  25 of Admin Guide .
9. medem configured on RS/6000 inhouse if any info regarding configuration
required from sungurad then can dial up and get it.

My plan .
1. Install  AIX from mksysb .
2. create all volume groups , logical volumes and file systems. from output
of
all the commands in step 7
3. restore tsmvg  from savevg  .
4. confiure library , smitty devices , tapes etc..
5 copy recovery plan file from floppy  to any directory , and break with awk
script
6. run each script

STK and ACSLS PART.

Install SUn from CD`S  , install ACSLS in case ufsdump won`t work ,  have
taken
backup of ACSLS ,
connect STK9710 scsi cable to sun --probe -scsi -all
configure ACSLS , restore ACSLS backup (This i have tested in house it works
,
but have to test with STK9710 connected)

put all DRM  in silo , and try restoring data .

where  all you will suggest me changes with your  experiance with Disaster
recovery . and where  all you have faced problems .
what procedure is most time consuming ?  so that i can prepare , having more
5
days .
any troubleshooting experiance?did i forgot something to take with me..

Thanks
Shekhar.




.

Re: Disaster Recovery Test.

[Shekhar Dhotre]

Thank you  very much chris. i will update the list.
shekhar




"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 09/27/2000 01:18:31 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: Disaster Recovery Test.

I would make several recommendations, having done this twice so far this year.

Take blank tapes of all media you might use (ie, 8mm for AIX mksysbs, DLT for
the library, etc). While
you're at it, take cleaning tapes too. We had our own, and used several of
them. By the time Sungard
found their cleaning tapes, we had already cleaned the drives and moved on.
Create your volume group creation scripts ahead of time and stick them in the
mksysb/savevg or bring
them on a floppy. Sungard is supposed to tell you what equipment you will have.
They gave us 4.5 GB
SSA drives,which differs from what we have on site (a mix of 9.1 and 4.5 GB
SSA). The scripts we used
at Sungard differed greatly from the ones used to create the vgs at home.
Create a detailed plan (more than what you've got here) that lists all steps
with commands included. This way,
when you are tired or distracted after a long day, you don't have to go on
memory.  We took pages of
documetation to the first test, and refined it for the second test, adding in
all the steps we hadn't thought
of before (like exporting all the volumegroups so that when they are recreated,
there aren't any conflicts in
/etc/filesystems).
If possible bring your own command reference manuals and the ADSM manuals.
Sungard only has
hardware documentation, and they don't provide access to the internet.  While
we were at Sungard
our remote dial in system was down for a period of time, stranding us from the
online docs (we did
have hard copies).
Know what version of the firmware your STK library is running. If possible,
have your STK engineer
give you a duplicate copy to bring with you. We spent 11 hours attempting to
getACSLS running
and the problem turned out to be the library was at the wrong version of
firmware. TheSTK onsite
guys weren't much help. It took a hotline product engineer to figure it out.
Of course, bring all the hotline phone numbers and site numbers.
Bring a picture of how everything is to be set up (send it ahead if you can). A
picture is worth a
thousand words when attempting to get the equipment in the right place, and
connected up properly.
When you get there, go over all the hardware and connections. We were suprised
by the fact that
our server couldn't communicate on the network. Turns out there was an extra FE
adapter in the
server (not at our request) and that was what they had hooked up.

Hope this helps.
-Chris Wickham
Bayer Corp, Pharma Division




"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 09/27/2000 09:46:17 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Disaster Recovery Test.

Hi all , going for firstever DR test at Sunguard ,
here is what i have collected  for test .

1. mksysb tapes .
2.  TSM database tapes , and  all offsite (copypool tapes).
3. savevg of tsm  (i have a volume group called tsm  for tivoli)
4. disaster recovery plan file  (hard copy and soft copy , sample awk script to
break it down.)
5. ACSLS is configured on Sun so , for the same ufsdump tapes
6. AIX , SUn Slorais , and ACSLS , installation media .
7. out puts of lsvg, lsvg -l vgnames , df , lsdev- Cc disks , lsdev- Cc tape,
lscfg , lsattr -El mem0 , lsps -a , lsattr -El en0.
   same for the sun .out put of dsm.sys , dsm.opt ,dsmserv.opt  I know they
will be in rootvg ,but precaution is better than cure   :-)
8. chapter  25 of Admin Guide .
9. medem configured on RS/6000 inhouse if any info regarding configuration
required from sungurad then can dial up and get it.

My plan .
1. Install  AIX from mksysb .
2. create all volume groups , logical volumes and file systems. from output of
all the commands in step 7
3. restore tsmvg  from savevg  .
4. confiure library , smitty devices , tapes etc..
5 copy recovery plan file from floppy  to any directory , and break with awk
script
6. run each script

STK and ACSLS PART.

Install SUn from CD`S  , install ACSLS in case ufsdump won`t work ,  have taken
backup of ACSLS ,
connect STK9710 scsi cable to sun --probe -scsi -all
configure ACSLS , restore ACSLS backup (This i have tested in house it works ,
but have to test with STK9710 connected)

put all DRM  in silo , and try restoring data .

where  all you will suggest me changes with your  experiance with Disaster
recovery . and where  all you have faced problems .
what procedure is most time consuming ?  so that i can prepare , having more 5
days .
any troubleshooting experiance?did i forgot something to take with me..

Thanks
Shekhar.




.

Re: Disaster Recovery Test.

[Long, Matt]

Shekar,

When you do the restore of the database with a 9710, how does TSM
know or find the location of the dbbackup volume inside the silo? Do you do
a manual type restore first with the tape in the drive or is TSM capable of
finding that volume inside the silo with the silo defined in the dev.conf
file?, even though it might not be in the same cell location when the last
dbbackup was done.  I am getting ready to do a BRS test of our 9710
connected to an R50 via F/W Diff SCSI cards.  Thanks

Matt Long
Systems Administration
Marriott International


-Original Message-
From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 27, 2000 9:45 AM
To: [EMAIL PROTECTED]
Subject: Disaster Recovery Test.


Hi all , going for firstever DR test at Sunguard ,
here is what i have collected  for test .

1. mksysb tapes .
2.  TSM database tapes , and  all offsite (copypool tapes).
3. savevg of tsm  (i have a volume group called tsm  for tivoli)
4. disaster recovery plan file  (hard copy and soft copy , sample awk script
to
break it down.)
5. ACSLS is configured on Sun so , for the same ufsdump tapes
6. AIX , SUn Slorais , and ACSLS , installation media .
7. out puts of lsvg, lsvg -l vgnames , df , lsdev- Cc disks , lsdev- Cc
tape,
lscfg , lsattr -El mem0 , lsps -a , lsattr -El en0.
   same for the sun .out put of dsm.sys , dsm.opt ,dsmserv.opt  I know
they
will be in rootvg ,but precaution is better than cure   :-)
8. chapter  25 of Admin Guide .
9. medem configured on RS/6000 inhouse if any info regarding configuration
required from sungurad then can dial up and get it.

My plan .
1. Install  AIX from mksysb .
2. create all volume groups , logical volumes and file systems. from output
of
all the commands in step 7
3. restore tsmvg  from savevg  .
4. confiure library , smitty devices , tapes etc..
5 copy recovery plan file from floppy  to any directory , and break with awk
script
6. run each script

STK and ACSLS PART.

Install SUn from CD`S  , install ACSLS in case ufsdump won`t work ,  have
taken
backup of ACSLS ,
connect STK9710 scsi cable to sun --probe -scsi -all
configure ACSLS , restore ACSLS backup (This i have tested in house it works
,
but have to test with STK9710 connected)

put all DRM  in silo , and try restoring data .

where  all you will suggest me changes with your  experiance with Disaster
recovery . and where  all you have faced problems .
what procedure is most time consuming ?  so that i can prepare , having more
5
days .
any troubleshooting experiance?did i forgot something to take with me..

Thanks
Shekhar.




.

Re: Disaster Recovery Test.

[Christine Wickham]

I would make several recommendations, having done this twice so far this year.

Take blank tapes of all media you might use (ie, 8mm for AIX mksysbs, DLT for
the library, etc). While
you're at it, take cleaning tapes too. We had our own, and used several of
them. By the time Sungard
found their cleaning tapes, we had already cleaned the drives and moved on.
Create your volume group creation scripts ahead of time and stick them in the
mksysb/savevg or bring
them on a floppy. Sungard is supposed to tell you what equipment you will have.
They gave us 4.5 GB
SSA drives,which differs from what we have on site (a mix of 9.1 and 4.5 GB
SSA). The scripts we used
at Sungard differed greatly from the ones used to create the vgs at home.
Create a detailed plan (more than what you've got here) that lists all steps
with commands included. This way,
when you are tired or distracted after a long day, you don't have to go on
memory.  We took pages of
documetation to the first test, and refined it for the second test, adding in
all the steps we hadn't thought
of before (like exporting all the volumegroups so that when they are recreated,
there aren't any conflicts in
/etc/filesystems).
If possible bring your own command reference manuals and the ADSM manuals.
Sungard only has
hardware documentation, and they don't provide access to the internet.  While
we were at Sungard
our remote dial in system was down for a period of time, stranding us from the
online docs (we did
have hard copies).
Know what version of the firmware your STK library is running. If possible,
have your STK engineer
give you a duplicate copy to bring with you. We spent 11 hours attempting to
getACSLS running
and the problem turned out to be the library was at the wrong version of
firmware. TheSTK onsite
guys weren't much help. It took a hotline product engineer to figure it out.
Of course, bring all the hotline phone numbers and site numbers.
Bring a picture of how everything is to be set up (send it ahead if you can). A
picture is worth a
thousand words when attempting to get the equipment in the right place, and
connected up properly.
When you get there, go over all the hardware and connections. We were suprised
by the fact that
our server couldn't communicate on the network. Turns out there was an extra FE
adapter in the
server (not at our request) and that was what they had hooked up.

Hope this helps.
-Chris Wickham
Bayer Corp, Pharma Division




"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 09/27/2000 09:46:17 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Disaster Recovery Test.

Hi all , going for firstever DR test at Sunguard ,
here is what i have collected  for test .

1. mksysb tapes .
2.  TSM database tapes , and  all offsite (copypool tapes).
3. savevg of tsm  (i have a volume group called tsm  for tivoli)
4. disaster recovery plan file  (hard copy and soft copy , sample awk script to
break it down.)
5. ACSLS is configured on Sun so , for the same ufsdump tapes
6. AIX , SUn Slorais , and ACSLS , installation media .
7. out puts of lsvg, lsvg -l vgnames , df , lsdev- Cc disks , lsdev- Cc tape,
lscfg , lsattr -El mem0 , lsps -a , lsattr -El en0.
   same for the sun .out put of dsm.sys , dsm.opt ,dsmserv.opt  I know they
will be in rootvg ,but precaution is better than cure   :-)
8. chapter  25 of Admin Guide .
9. medem configured on RS/6000 inhouse if any info regarding configuration
required from sungurad then can dial up and get it.

My plan .
1. Install  AIX from mksysb .
2. create all volume groups , logical volumes and file systems. from output of
all the commands in step 7
3. restore tsmvg  from savevg  .
4. confiure library , smitty devices , tapes etc..
5 copy recovery plan file from floppy  to any directory , and break with awk
script
6. run each script

STK and ACSLS PART.

Install SUn from CD`S  , install ACSLS in case ufsdump won`t work ,  have taken
backup of ACSLS ,
connect STK9710 scsi cable to sun --probe -scsi -all
configure ACSLS , restore ACSLS backup (This i have tested in house it works ,
but have to test with STK9710 connected)

put all DRM  in silo , and try restoring data .

where  all you will suggest me changes with your  experiance with Disaster
recovery . and where  all you have faced problems .
what procedure is most time consuming ?  so that i can prepare , having more 5
days .
any troubleshooting experiance?did i forgot something to take with me..

Thanks
Shekhar.




.

Re: Disaster recovery on AIX

[Joel Fuhrman]

Attached is a shell script that was shared by someone on this list a long
while back.

On Sat, 2 Sep 2000, Stefan Llabres wrote:

> Talafous, John G. wrote:
> > Excellent outline/recap of steps to recover TSM on AIX. However, I have not
> > heard of the 'savevg' mentioned in the second step. Could you please provide
> > details? Where can I find documentation to lead me on this path?
>
> savevg ist part of aix and documented in the os guide (an man pages).
>
> S.Llabres
>


#!/usr/bin/ksh

# The shell will save the volume group descriptions for the
# non-rootvg volume groups using the savevg command.  This
# output can be used by the restore vg command to recreate 
# the volume groups.  For example:
#   restvg -qf /vg_images/savevg.$VGNAME

rm -f /vg_images/savevg.*
rm -f /tmp/savevg
integer total_error=0

# 1) get the non-rootvg volume groups (vg)
# 2) get the logical volumes (lv) by vg's, remove the header
#line, remove the unmounted & raw lv's, remove the nfs
#mounted files and print the mount point.
# 3) save the mount point in /etc/exclude.$VGNAME
# 4) save the volume group information for each volume group,
#while excluding the actual files, in /vg_images/savevg.$VGNAME

lsvg -o |grep -v rootvg |while read VGNAME
do
lsvg -l $VGNAME |grep -v LV | grep -v "N/A" | grep / | awk '{print $7 "/"} ' \
> /etc/exclude.$VGNAME 
savevg -eif/vg_images/savevg.$VGNAME $VGNAME >> /tmp/savevg 2>&1
(( total_error = total_error + $? ))
done

if (( total_error > 0 ))
then
/bin/mail -s "`hostname`: savevg had errors" admin < /tmp/savevg
exit 1
fi
exit 0

Re: Disaster recovery on AIX

[Stefan Llabres]

Talafous, John G. wrote:
> Excellent outline/recap of steps to recover TSM on AIX. However, I have not
> heard of the 'savevg' mentioned in the second step. Could you please provide
> details? Where can I find documentation to lead me on this path?

savevg ist part of aix and documented in the os guide (an man pages).

S.Llabres

Re: Disaster recovery on AIX

[Jolley, Bill]

the savevg is an aix command and should be part of the AIX os. Review the
man pages.

touch a file in /etc:  touch /etc/exclude.vgname (the file contains only /*)
savevg -ievf /dev/rmtx vgname
or
savevg -ievf filename vgname (save to a directory in rootvg)

at dr site restore savevg

restvg -q -f filename hdiskx ( This will restore the vg and lv's)


 AIX Version 4.3 Commands Reference, Volume 5





savevg Command



Purpose



Finds and backs up all files belonging to a specified volume group.



Syntax



savevg [ -b Blocks ] [ -e ] [ -f Device ] [ -i | -m ] [ -p ] [ -v ] [ -X ]
VGName


Description



Attention: The savevg command will not generate a bootable tape if the
volume
group is the root volume group.



The savevg command finds and backs up all files belonging to a specified
volume
group. A volume group must be varied-on, and the file systems must be
mounted.

-Original Message-
From: Talafous, John G. [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 01, 2000 10:20 AM
To: [EMAIL PROTECTED]
Subject: Re: Disaster recovery on AIX


Bill Jolley wrote:

>restore AIX from mksysb (ADSM code resides here hopefully)
>restore adsmvg from a savevg (this creates just the lv for dbv & logv)
>dsmfmt dbv and logv
>dsmserv format dbv and logv
>modify devconfig (manual or atl)
>dsmserv restore db
s>tart server
>mirror dbv and logv
>update devconfig
>Continue with section title "begin COPYSTGPOOL.VOLUMES.AVAILABLE module" in
>DRM planprefix /tsm/drm/drm

Excellent outline/recap of steps to recover TSM on AIX. However, I have not
heard of the 'savevg' mentioned in the second step. Could you please provide
details? Where can I find documentation to lead me on this path?

TIA
John G. Talafous IS Technical Principal
The Timken Company Phone: (330)-471-3390
P.O. Box 6927   Fax  :   (330)-471-4034
1835 Dueber Ave. S.W.
Canton, Ohio USA  44706-0927
[EMAIL PROTECTED]  http://www.timken.com/

Re: Disaster recovery on AIX

[Richard Sims]

>Excellent outline/recap of steps to recover TSM on AIX. However, I have not
>heard of the 'savevg' mentioned in the second step. Could you please provide
>details? Where can I find documentation to lead me on this path?

'savevg' is mentioned on the first page of chapter 14 in the ADSM Client Disaster
Recovery: Bare Metal Restore redbook, in discussing AIX Version 4.1 Recovery.
'man savevg' should provide a description on your system.  Or see
AIX 4.3 online documentation:
www.rs6000.ibm.com/doc_link/en_US/a_doc_lib/aixgen/topnav/topnav.htm

 Richard Sims, BU

Re: Disaster recovery on AIX

[George Yang]

yes in the very begining
George

Re: Disaster recovery on AIX

[Talafous, John G.]

Bill Jolley wrote:

>restore AIX from mksysb (ADSM code resides here hopefully)
>restore adsmvg from a savevg (this creates just the lv for dbv & logv)
>dsmfmt dbv and logv
>dsmserv format dbv and logv
>modify devconfig (manual or atl)
>dsmserv restore db
s>tart server
>mirror dbv and logv
>update devconfig
>Continue with section title "begin COPYSTGPOOL.VOLUMES.AVAILABLE module" in
>DRM planprefix /tsm/drm/drm

Excellent outline/recap of steps to recover TSM on AIX. However, I have not
heard of the 'savevg' mentioned in the second step. Could you please provide
details? Where can I find documentation to lead me on this path?

TIA
John G. Talafous IS Technical Principal
The Timken Company Phone: (330)-471-3390
P.O. Box 6927   Fax  :   (330)-471-4034
1835 Dueber Ave. S.W.
Canton, Ohio USA  44706-0927
[EMAIL PROTECTED]  http://www.timken.com/

Re: Disaster recovery on AIX

[Christine Wickham]

This year we have performed two ADSM server recoveries at Sungard in
Philadelphia. Here is an overview of what we performed:


Restore node from mksysb (in our case it was an SP node)
Export our old volume groups clean out /etc./filesystems
Create volume groups and filesystems for database, storage pools, etc. Sungard
gave us the exact layout of what we would have, so we created scripts that
would create appropriate filesystems. In our case, we have 9 GB SSA drives at
our site, but Sungard only had 4.5 GB drives.
>From this point on, we followed the documentation in the Admin guide on DRM
Burst apart the DRM plan. We send ours off site every day on a floppy, so we
used the copy from the floppy. Our Mksysb did not have the plan for the day we
were restoring to.
Instead of running the main script, we chose to run each script individually to
ensure that any errors we encountered wouldn't get buried in log files.

Chris Wickham
System Admin (UNIX and ADSM)
Bayer Corporation, Pharmaceutical Division





"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 09/01/2000 09:03:18 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: Disaster recovery on AIX

I am doing the same thing now (Sungarde too).
But I am not restore AIX, because before we restore DB it is impossible
(except using other media or tar which required more daily operation).
1. install AIX
2. install library
2  install TSM
3  follow your DRMPLAN (Which is part of your DRM) copy Devconfig,
dsmserv.opt and volhist files,
4. do dsmfmt -db and dsmfmt -log (make sure the db size and log size)
5. dsmserv restore devc=devclass_name vol=vol_name1,vol_name_2 commit=yes
6. then you can restore the AIX.


George

Re: Disaster recovery on AIX

[Jeff Justus]

We found that using SYSBACK worked better than MKSYSB for our system backups
because it recreates our logical volumes and vg's.  Be very careful at Sunguard
(its who we use for our DR too) because they have both 3590b and e drives so if
you use the 3590's you can only boot from the same e or b as you have at your
home site.

Jeff Justus




Shekhar Dhotre <[EMAIL PROTECTED]> on 09/01/2000 09:43:27 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: Jeff Justus/US/Schneider)
Subject:  Re: Disaster recovery on AIX



But AIX will be restored first  from mksysb and then you will create volume
groups logical volumes ,
which is out put of commands  df -k , lsvg -o | lsvg -i -l,   lsvg   lsdev
-C | sort -d -f etc..
your step 6  says restore AIX , so your are installing fresh copy of AIX? and
not from mksysb?





"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 09/01/2000 09:03:20 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: Disaster recovery on AIX

I am doing the same thing now (Sungarde too).
But I am not restore AIX, because before we restore DB it is impossible
(except using other media or tar which required more daily operation).
1. install AIX
2. install library
2  install TSM
3  follow your DRMPLAN (Which is part of your DRM) copy Devconfig,
dsmserv.opt and volhist files,
4. do dsmfmt -db and dsmfmt -log (make sure the db size and log size)
5. dsmserv restore devc=devclass_name vol=vol_name1,vol_name_2 commit=yes
6. then you can restore the AIX.


George

Re: Disaster recovery on AIX

[Jolley, Bill]

I complete a drill in august and was successful.

restore AIX from mksysb (ADSM code resides here hopefully)
restore adsmvg from a savevg (this creates just the lv for dbv & logv)
dsmfmt dbv and logv
dsmserv format dbv and logv
modify devconfig (manual or atl)
dsmserv restore db
start server
mirror dbv and logv
update devconfig
Continue with section title "begin COPYSTGPOOL.VOLUMES.AVAILABLE module" in
DRM planprefix /tsm/drm/drm

-Original Message-
From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 31, 2000 6:09 PM
To: [EMAIL PROTECTED]
Subject: Disaster recovery on AIX


Hi all ,
 we are in the process of testing DRM  for our production and devolopment
environment, at  Sunguard (philadelphia)
our environment S-7a advanced server , and h-70 (AIX 433) TSM 3.7.2  ACSLS
5.2
,STK9710 ,
now i have given task , to perform this test succesfully , in the month of
Noeveber 5  still 2 months to study
now the steps  which i know are  ,
1. i will take my mksysb from this loaction to Sunguard(Sunguards will
provide
identical hardware) so
restoring from mksysb is not a problem.
2. after rstoring AIX environment , i want to know exact steps to recover
ADSM
server .i.e . how to recover databas and log?
i am using DRM module in TSM  so i am having following tapes with me . and a
floppy that is created each day (volhist.. etcc) .

Recovery Plan for Server TSM
Created by DRM PREPARE on 08/31/00 10:00:07
DRM PLANPREFIX /tsm/drm/drm
Storage Management Server for AIX-RS/6000 - Version 3, Release 7, Level 2.0


Volumes required for data base restore

 Location =
  Device Class = STK9710
  Volume Name =
   MED519

Volumes required for storage pool restore

 Location =
  Copy Storage Pool = COPYPOOL
  Device Class = STK9710
  Volume Name =
   MED517

 Location = VAULT
  Copy Storage Pool = COPYPOOL
  Device Class = STK9710
  Volume Name =
   MED500
   MED502
   MED503
   MED505
   MED506
   MED507
   MED508
   MED509
   MED510
   MED511
   MED512
   MED514
   MED515
   MED520
   MED521
   MED522
   MED523
   MED525
   MED526
   MED527
   MED528
   MED529
   MED530
   MED531
   MED532
   MED534
   MED535
   MED537
   MED538
   MED539
   MED541
   MED542
   MED543

as this will be my first test , i will be under pressure , as you ahev gone
thru this can you please guide me ?
that is steps involved , recovering  TSM server . or any documentation ?
meanwhile i am reading Tivoli Storage manager for AIX admin Guide
chapter 21: Using Tivoli Disaster recovery Manager. and refering ADSM.org
for
DRM experiance..

Thanks  in Advance .

Shekhar Dhotre.
IBm certified AIX 4.3.3 Administrator
IBM certified RS/6000 SP  Administrator
Microsoft Certified Systems Engg.

Re: Disaster recovery on AIX

[Shekhar Dhotre]

But AIX will be restored first  from mksysb and then you will create volume
groups logical volumes ,
which is out put of commands  df -k , lsvg -o | lsvg -i -l,   lsvg   lsdev
-C | sort -d -f etc..
your step 6  says restore AIX , so your are installing fresh copy of AIX? and
not from mksysb?





"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 09/01/2000 09:03:20 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:

Subject: Re: Disaster recovery on AIX

I am doing the same thing now (Sungarde too).
But I am not restore AIX, because before we restore DB it is impossible
(except using other media or tar which required more daily operation).
1. install AIX
2. install library
2  install TSM
3  follow your DRMPLAN (Which is part of your DRM) copy Devconfig,
dsmserv.opt and volhist files,
4. do dsmfmt -db and dsmfmt -log (make sure the db size and log size)
5. dsmserv restore devc=devclass_name vol=vol_name1,vol_name_2 commit=yes
6. then you can restore the AIX.


George

Re: Disaster recovery on AIX

[George Yang]

I am doing the same thing now (Sungarde too).
But I am not restore AIX, because before we restore DB it is impossible
(except using other media or tar which required more daily operation).
1. install AIX
2. install library
2  install TSM
3  follow your DRMPLAN (Which is part of your DRM) copy Devconfig,
dsmserv.opt and volhist files,
4. do dsmfmt -db and dsmfmt -log (make sure the db size and log size)
5. dsmserv restore devc=devclass_name vol=vol_name1,vol_name_2 commit=yes
6. then you can restore the AIX.


George

Re: Disaster Recovery Manager Withdrawal?

[Joshua S. Bassi]

DRM is NOT slated for withdrawal.


--
Joshua S. Bassi
Senior Technical Consultant
Symatrix Technology, Inc.
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Matthias Hensel
Sent: Tuesday, August 15, 2000 12:35 AM
To: [EMAIL PROTECTED]
Subject: Disaster Recovery Manager Withdrawal?


regarding Disaster Recovery Manager I was told that this product is
announced to be withdrawn at the end of october 2000. Is this true? Will
it not be included in TSM4.1?

Matthias

Re: Disaster Recovery Manager Withdrawal?

[Daniel Swan/TM]

I don't think I'd ever suffer Disaster Recovery Manager Withdrawl,
but if you do, there are treatments available.