Re: backup to and restore from local win server

Jim,

we have some CLs to do something similar using Internet + NAS and I've learned a couple of things:

* You can go fast or you can go cheap: Fast means parallel saves, but requires you have at least 50% free space, or so. Cheap means using serialized backups, needs a big window and once you save you can ZIP and transfer or just transfer and delete the SAVF to free up space.

* Space: If you are trying to compress before transfer I recommend ZIP or P7zip with mx1 (faster) and NO compression on SAVF. You get something rounding 8:1 compress ratio. But you need same space as library for each SAVF.

* Based on these: Parallel backup requires same space as data you save and when zipping an additional 15% . Serialized backup requires sames space as largest library + 15%

If you try to save-transfer-restore maybe your best chance is to avoid ZIP and use incremental backups. With incremental backups I guess you can save just 1/10th of your data.

Remember to test-test-test, use best communication mechanism (sometimes SCP/SFTP with compression is faster than FTP with uncompresse SAVF), change TCP attributes for a larger send/receive buffer and test-test-test again

You could save a big library and start your stopwatch, then make your math considering save-to-disk, transfer and restore from disk

Good luck

Regards

Diego Kesselman


El 02/11/17 a las 18:18, midrange escribió:

Is it feasible/reasonable to nightly backup savf from IBM I to local Win
server of qsys.lib libraries and selected ifs directories.

At V7R1, and total savfs should be .5 Tb ? There is room on disk for the
save files.

Don't know how to calc how the "real world" speed of such a transfer (shared
drive or ftp ) across 1Gb Ethernet.

. poor man's DR idea . any not obvious potholes to avoid?


Jim