Detached Backups
-
Not a big deal, but it would be nice if 'Detached Backups' could be re-attached to a new job, or maybe some other way to say "yea, it's parent is gone but it's a good backup".
Maybe this is the way it's supposed to work, but sometimes I've found I need to recreate a job. Unfortunately, this results in a bunch of perfectly good backups showing up without a home.
Again, not a bit deal, but I feel like there could be some improvement.
Thanks.
-
Ping @Rajaa-BARHTAOUI or @badrAZ
-
Hi,
The detached backups are the VM backups with missing jobs, schedules, and VMs.
We show the detached backups because:
-
These backups will never executed.
-
The retention will never be applied.
-
XO does not manage these bakcups and they will never be cleaned by XO.
The benefits of attaching those detached backups will be to clean them automatically when the retention limit is reached and to reduce the size of the exported backup on the first execution in case of a delta backup.
Those benefits are negligible in comparison with the technical challenges which will lead this functionality.
Best regards.
-
-
Thanks for the feedback.
Coincidently, a few days ago, I accidentally approved some Xen drivers in WSUS. Next day, all my Windows VMs were toast. (Wouldn't boot). For most of the VMs, easiest solution was to restore a backup. As a result, the backup retention started over and I had some time consuming clean up to do with my backups. Also, until I go though an entire rotation of backups (90 days), I'll need to continue to manually clean up.
I don't mind cleaning up the backups and ignoring the detached backups. I was just looking for a better way to handle situations where you simply want to restore a backup w/o breaking the backup chain.
Okay, yes, snapshots come to mind, but I try to keep my snapshots to a minimum.
Based on your reply, this topic has been considered and the pros/cons (currently) amount to working within the current setup. Thanks again.
-
I just had an idea - how hard would it be to add a feature to the delta backup to retain 'x' number of snapshots, vs. just the the last snapshot? Maybe also have a limit on it.
-
You can do that already if you like (combined rolling snap and delta backup). But what's the point?
edit: about your previous question, restoring without breaking the chain. That might be possible. In theory, after restore, we should take a snapshot before booting the backup and then re-link the restored VM to the backup folders. It's doable (renaming some folders correctly) but I'm not sure this will be very useful.
-
@olivierlambert said in Detached Backups:
You can do that already if you like (combined rolling snap and delta backup). But what's the point?
Oh, wow. You can combine backup methods in the same job (as long as they are compatible methods (i.e. Delta and CR). This is cool. I currently have separate jobs for my deltas and CRs. I'll need to make time to make the changes, but this will simply things greatly. I'll even throw in a few extra snapshots to retain. So, yea, this is pretty much what I was thinking of. I didn't realize it was there.
Why would I need this? Well, when my WSUS installed the Xen drivers on all my Windows VMs, I went a day before realizing what happened. A snapshot would have been sufficient, if I had one from the day before. Instead, I restored the backup which broke the chain.
@olivierlambert said in Detached Backups:
edit: about your previous question, restoring without breaking the chain. That might be possible. In theory, after restore, we should take a snapshot before booting the backup and then re-link the restored VM to the backup folders. It's doable (renaming some folders correctly) but I'm not sure this will be very useful.
I'll look into this when I get some time. Thanks.
