Re: [Networker] New-Bee?: restoring from BU Srvr A -> BU Srvr B

On Aug 16, 2006, at 9:56 AM — 8/16/06, Albert Eddie Contractor AFRPACIO/IT wrote:

Environment
        Windows 2003 Servers
        Networker 6.2.1
        T-1
        LTO2 Tapes
        ADIC Libraries
        I have network access to all servers from my location.

Sit-Rep:
Backup Server A
        Located in NYC

Backup Server B
        Located in Aloha State

Disaster recovery plan calls for backup tapes from Server A to be sent
to location B and vice-versa.

Now we want to test.

We are going to attempt to restore a "tape from BU Server B" using BU
Server A Restoring "TO BU Server B" across the network.

The rub here is the tape from server B is NOT in server A's index.

Any suggestions on best way to proceed and commands needed? Better yet

caveats? When I read this I imagine I should be able to put thetape in

my local library, read the tape and restore it. I know there has to be
more to it than that. The info on this tape is not in the index on my
backup server.

Sincerest thanks in advance for not telling me to RTFM.

First off, why are you using version 6.2.1? That version is no longersupported. Can you run at least version 7.2.2 on your pair of backupservers?

Second, is there any chance your two servers can share a disk volume?I have never tried this, so I am just thinking out loud, but you maybe able to place your client file and media index directories on ashared disk volume. Then if you license the backup server exactly thesame way as the production server, you may be able to simply start upthe backup server and have it work the same way as your primaryserver BUT you can't run both servers at the same time.

Another alternative is to do long-distance disk-to-disk replicationof your primary NetWorker server to your backup server.

Your options really depend on how large your client file index is andthe number of clients you back up each night.

Also, what is your time frame for recovering your data at the DRsite? If necessary, you can mmrecov a copy of your most recentbootstrap volume at the DR site then recover your client file indexdata, but that path is likely to require a lot of time. The amount oftime is also contingent on the number of files that are tracked inyour client file index. More files in the database, means more timeto recover the database.

I am sure some others on this list will offer some different ideasthat may be better than what I just posted, but you never know!


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
wit 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