Go with the save file if you have the space. Heck, I'll even give you my FTP
batch program. Contact me off line.
I do machine switches via FTP frequently. I have a utility program called
SENDTONEW. It does everything I need to do to get a new box set up,
including restoring and running programs needed to restore user profiles,
configuration items, libraries, etc.
It takes a tweak here and there, depending on the customer, but it pretty
much just runs.
I start it up about 8 PM, and the next morning, the users sign on to the new
box.
Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gord Hutchinson
Sent: Friday, August 14, 2009 7:03 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: Virtual Tape vs Savf
The thread on migrating without using tape got me thinking of something I'll
be setting up soon.
Weekly, I will be copying our production file library from or production
machine to our development machine. I was going to save to a savf and then
FTP that over.
Is there any benefit to using virtual tape instead of a savf?
Thanks
Gord
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.
midrange.com
