RE: Network backups

>From: Evan Harris [mailto:spanner@xxxxxxxxxx] 
>The client wants one of the machines only if possible to be used as the 
>machine that has tapes changed, as the other machine is located in a remote

>part of the site.

Here is what we're doing on one of our development (small) machines. 

1) Save to local tape after OS upgrades and PTFs (only way to restore
system)
2) Each night save user libraries (data/programs/etc.) to save files
3) FTP save files to our backup server (W2K in our case)
4) Save files on W2K to tape.

We're recovered several times from this scenario so I know it works. Your
system in undoubtedly larger, but the theory is the same. The biggest draw
back to this approach is the space needed by the save files. 

Additionally, a restore requires first a restore of the save file from tape,
then an FTP to put it back on the iSeries, then a restore from the save
file. Since your machine is another iSeries you would have the option of not
saving the savf itself, but doing a savsavfdta command on the save file.
That way your restore was simply a restore from tape.

I would point out if you are doing this, make sure you have a tape drive on
each of these machines that can read you backup tape. Nothing is more
annoying that crashing your primary system, moving to the secondary system
and having a round tape and a square drive.

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)