I am looking for a good strategy on expiring my old backups in v5 once I have moved my backups to a newly created v6 environment.
The current plan is to keep the target the same (data domain 860 via cifs). But with a 30 day retention policy, is there a good way to let the jobs in v5 still run, and expire/cleanup the old backups without actually doing a backup of the VM? We probably won’t have enough space on the DD for 30 days of backups on both V5 and V6 and I’m being asked not to go below a full 30 days’ worth of backups at any given time.
-
- Enthusiast
- Posts: 30
- Liked: never
- Joined: Jun 26, 2011 7:02 pm
- Full Name: Jeff Couch
- Contact:
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Preping for New Jobs in v6, Expire old backups in v5
No, this is definitely impossible as cleanup is only done after successful backup.jkcouch wrote:is there a good way to let the jobs in v5 still run, and expire/cleanup the old backups without actually doing a backup of the VM
-
- Enthusiast
- Posts: 30
- Liked: never
- Joined: Jun 26, 2011 7:02 pm
- Full Name: Jeff Couch
- Contact:
Re: Preping for New Jobs in v6, Expire old backups in v5
Ok Thanks. So how does the cleanup process work for deleted VMs? How does veeam know its deleted?
My thought is that I could leave one VM in the job so it will still run, and remove the rest from the job. I assume this wont work either, but its worth asking.
My thought is that I could leave one VM in the job so it will still run, and remove the rest from the job. I assume this wont work either, but its worth asking.
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Preping for New Jobs in v6, Expire old backups in v5
This would work if you are using regular incremental backup mode (default). Your older backup files will be gradually removed according to retention, as soon as deleted VM retention period expires for each VM that is no longer backed up.jkcouch wrote:I could leave one VM in the job so it will still run, and remove the rest from the job
Who is online
Users browsing this forum: No registered users and 71 guests