Manual Backup (no schedule and no automatic deletion of old backups) Please?
-
Hello, so I screwed up. I was playing with backups and I wanted to see if I can do a manual backup (triggered by me, no schedule). Well apparently this is not sported. I realized this after I deleted the schedule and the backup job would not save, saying I need a schedule. So I created a (default) schedule and then disabled it. I then manually triggered the backup to test this approach. Of course the backup went through just fine. Soon after I realized that I messed things up good. The default backup schedule defaults to only retaining one copy. My half a dozen previous backups have now been automatically removed. The problem is I need my first backup in case I want to start over working on my VM. Well, that gone now
I get that I caused this myself. I'm wondering if a function for manually triggered backups without deleting any previous backups can be added.
My use case is as follows. You start working on a new VM, you get the basic setup done. Now I want to be able to get back to this point at any time should the changes I make next not work out so I'd like to trigger a manual backup. Next few weeks are keeping me busy with other work. I finally come back to what I started earlier and continue my configuration. In the next few days I realize that what I have done is not going to work. At this point I would like to simply restore my first backup that already has the basic configuration done and I can go for attempt two.
I guess another way of saying this is I would like to tag certain backups as protected so that they will never be erased automatically to reclaim storage space. Does anyone agree that this would be useful?
Cheers.
-
-
Ouch. How unlucky
Makes me think of a safety feature. A new backup job should warn before removing backups from other jobs.
-
But a new job will have a unique ID, isn't it @julien-f ?
-
@Forza Actually not all is lost. I have off site backups, so I could restore the backup target remote from it's off site backup.
I'm wondering if I power off XO, then restore the contents of the directory where my backup target remote points to, will XO then be able to see the old backups, before they were wiped? Or, will it be very confused because it's metadata is not stored on the remote but rather on the XO VM.
-
All metadata are stored in the remote directly, not in XO.
-
@olivierlambert OK, thank you for the clarification.
-
@olivierlambert Yes, each job has a unique identifier and willl not touch backup files of other jobs.
