Hi Stan,

How will you handle networker's authentication to the data?  I'm not at all 
familiar with UNIX/Mainframe or even with using a storage node, but you will 
have to scanner that data into a Networker installation somewhere and the 
networker installation must have the volume/media/security/registration 
settings identical to your source networker server.  Do you have all of this 
Networker info documented so that you can rebuild it all manually?  
Additionally Networker is heavily dependant upon DNS.  How will you restore 
without proper host resolution?

BTW Are you going to the Scottsdale facility?  That is a fantastic facility and 
I have done my DR tests there for the last three years, but I'm 100% Windows.  
We are moving tests to the New Jersey facility starting later this year.

Also one gotcha I ran into during my first test was block size differences 
between the LTO3 drives I use in my production facility and those on the Drives 
provided by Sungard.  Fixed eventually with a call, but was a 1 hour delay 
before I could get anything going.

--Shawn

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Stan Horwitz
Sent: Wednesday, January 16, 2008 9:01 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Tips for doing a DR at SunGard

On Jan 16, 2008, at 9:41 AM, Coty, Edward wrote:

> I have done many tests at sunguard. I would do the following.
>
> 1) Make sure you have a valid bootstrap and all client indexes backed
> up fully on the DR tapes.

I think I explained this unclearly. I am not interested in recovering my 
NetWorker server at SunGard.

In fact, recovering the entire server would be impossible as far as I can see 
because our production NetWorker server uses Sony SAIT-1 tapes and the DR 
server at SunGard uses LTO-3 media, which is what we use to back up this 
client's data to a storage node. I don't understand why I would need the 
bootstrap data since I don't care about recovering the actual NetWorker server, 
I just need to read the client's data off the
LTO-3 tapes and call it a day.

> 2) Make sure your DR backup server had the same server name as your
> production.

Thanks. Why would this be necessary if I am not interested in recovering the 
NetWorker server?

> 3) Since you only have one client to recover ask sunguard for a
> standalone drive, if not just use the drives in the library but do not
> configure the silo if you don't need it.

Why? The data will likely take at least 16 hours to read off tape. I would 
prefer not to have to swap out tapes manually if I can avoid it, but I 
certainly will, of course.

> 4) Install networker and run mmrecov and enter the information needed.
> Make sure the tape is in the drive. Add the drive /dev/rmt/xxxx to the
> base install of networker.

In light of the fact that my only interest here is reading the client's data, I 
doubt this would be necessary. In fact, now that I think about it, this 
exercise is more like moving data from one backup server to another, not a full 
DR exercise.

> 5) Once the DB has been recovered, stop networker, and rename the res
> directories.
> 6) restart networker. Remove your jukebox and add the standalone
> drives.
> Mount the tapes with the indexes and data.
> 7) Using the gui recover the index from the client in question from
> tape. When done run nsrck -L6 clientname. You could also use nsrck -L7
> clientname -t date.
> 8) Once the index is recovered you can do a browsable recovery.

That's cool, and I have had to do that twice in the past four months when my 
production server died on me twice, but for this exercise, management cares 
only about ONE thing; getting the client data back to the client. They do not 
care about recovering the actual NetWorker server at SunGard.

In fact, we will have a VTL at SunGard connected to their mainframe via ESCON 
channel to handle backups without NetWorker should the need arise. Back here at 
home, we have the same VTL connected to our mainframe and it backs up to disk 
storage that's controlled by a Linux box, which is itself a NetWorker client. 
This is the client I am interested in recovering at SunGard. What I need to do 
is recover the data from our production VTL to our DR VTL, then our mainframe 
people will verify that they can actually use the recovered data. Once that 
verification is done, we have no further use for NetWorker at SunGard for this 
exercise.

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or via RSS at 
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER