Local storage - as many calendar weeks as I can store, with synth fulls once a week. What I want to graduate to is a tiered backup solution to maximize my on-disk restore window within both a local and remote site, with Local, Remote and Remote Tape in the mix. I had that working a few weeks ago, it does accomplish getting a weekly copy to tape. If I only set the archival for 2 - weekly, and once a week backup the oldest weekly - does that get me what I want? I assume a setting of 2 keeps one from the prior week, creates a new for the current week, and on the third week deletes the oldest is that correct? The confusion is around the archival settings. Ideally, I'd like the 31days of local restore points, then some number of remote copy restore points and a mechanism whereby I can rollup a weekly full and copy it to tape. This VM's backup copy job is scheduled at at 10PM it is set to retain 7 restore points. That remote machine has Veeam running and a tape library. The VM's backup copy job takes the local data and moves it to a second remote machine/storage location. I am a little confused as to how to accomplish a tiered backup strategy (local, remote copy, remote tape) that would allow me to recover any file created on a given server within 365 days of its creation.Īs an example: I have a backup for a VM that runs daily at 8PM, it is set to do forever incrementals, maintain 31 days of recovery (locally) synthetic fulls on Saturday.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |