OK, I can't say what the DDS3 drive is off the top of my head but if it is
something you would have an a potential disaster recovery TSM server, sure
it will work... ALSO based on the size of the file dumped to disk, you could
always "ftp" it somewhere else... AND if you have yet another tsm server
somewhere, you could back that file up over on the other tsm server.
We have moved a tsm environment by backing the db up to disk, ftp'ing the
file over to a new server and doing the restore from that ftp'ed file.
I JUST LOVE THIS PRODUCT !
Dwight
-----Original Message-----
From: Ray [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 21, 2001 11:12 AM
To: [EMAIL PROTECTED]
Subject: database backup
Hello all,
I currently do on-disk db backups (to a file devclass) of my relatively
small (2 gb) database. Full on Saturday, incrementals Sun-Fri. I keep 2
weeks of backups on disk.
I need to start implementing an offsite stgpool. Instead of wasting a
100gb LTO tape for the db, i'm thinking about just tarring the on-disk
backup to a DDS3 drive. I'll also put vol history and devconfig on the
DDS3 tape, and send it offsite with the LTO tapes.. I think it'll be a
very long time before the db exceeds the 12gb capacity of DDS3.
Anyone see any problems/gotchas with sending the db offsite this way?
Thanks,
Ray
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ray DeJean http://www.r-a-y.org
Systems Administrator Southeastern Louisiana University
IBM Certified Specialist AIX Administration, AIX Support
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
