There is no 'restore'. I don't ftp a save file of my virtual tape image
catalogs. I ftp the image catalog entries directly.
Object . . . . . . : /vrtclg/VRT001
Size of object data in bytes . . . . . : 29780029601
Allocated size of object . . . . . . . : 29787947008
Takes about 41 minutes to do the save to virtual tape. It's all stream
files being saved, no qsys.lib type stuff.
Takes about 1 hour and 20 minutes to ftp the data.
Takes 23 minutes to dupe the tape from image catalog to physical media.
If I combined the save and the transmission by using NFS instead of doing
the transmission offline I can guarantee that the outage of what I backup
will increase from the 45 minutes. Unless you can guarantee that NFS will
be faster than my local disk drives.
Size % %
Unit Type (M) Used Busy
1 4327 52923 62.8 1
2 4327 52923 62.8 1
3 4327 52923 62.8 1
4 4327 52923 62.8 1
5 4327 70564 62.8 1
6 4327 70564 62.8 1
Keep in mind, that modern tape drives may actually be faster than saving
to disk. You're talking about utilizing two different busses, etc. The
tape drive has one user at a time using it versus disk having multiple
users (system tasks, etc) all sending the disk arms all over the place.
We did not do it to save time. We did it to do a remote backup, get the
'tape' over here and then we send it off to Iron Mountain. Please, no
offers to sell me VTL devices at this time.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.