Comprehensive data protection for all workloads
Post Reply
ortec-RW
Enthusiast
Posts: 44
Liked: 7 times
Joined: May 04, 2016 1:39 pm
Full Name: Richard Willkomm
Contact:

SOBR immutability per VM and cleanup

Post by ortec-RW »

Hi

I'm stuck with some immutability issue. Lemme try to explain.

I have an SOBR, with a performance tier (fast local storage), and a capacity tier (S3 object storage in Cloudian). The SOBR is set up to offload data to the S3 the moment it appears. So each backup I write to the SOBR automatically ends up in both extends (local + S3). The bucket is set up to be immutable for 1 day (plus 10 extra days you get from Cloudian by default). So far so good, been using this for a while now.

But, I run into an issue during backup cleanup. I have jobs that contain multiple VMs. Some of these VMs eventually get deleted, so I also need to remove them from these jobs. But the job itself remains, because it still contains other VMs. But the last backup of the deleted VM stays in the repository. Even long after the retention has passed. I manually need to empty out the last data of that deleted VM from the SOBR. If I don't clean up I'm left with a lot of old data from VMs that have been removed months ago. And they also take up space in my S3 buckets.

I delete this old data in the repository by selecting the VMs and right click delete while browsing the backup content, after which a delete job starts and Veeam removes the old data. This works fine sometimes. But on the SOBR, the data needs to be removed from both performance and capacity extends. This should not be an issue because the immutability period has long since passed (1+10 days). However, I still get an error the data is immutable for about 5 days more. And if I retry the next day, it's still 5 days. But the last backup is almost 2 months ago. Nowhere near 1, 5 or 11 days at all. Why is this ?

Each VM in the job is backupped with individual files. So the deleted VM is not part of a file that also contains other non deleted VMs.

Is all VM data locked because there are still active VMs being backed up in the same job ? I hope not. What else would be the reason of having seperate files per VM in a job.

So what I am missing here ?

Greetz
Richard
haslund
Veeam Software
Posts: 867
Liked: 154 times
Joined: Feb 16, 2012 7:35 am
Full Name: Rasmus Haslund
Location: Denmark
Contact:

Re: SOBR immutability per VM and cleanup

Post by haslund »

Rasmus Haslund | Twitter: @haslund | Blog: https://rasmushaslund.com
Post Reply

Who is online

Users browsing this forum: Baidu [Spider], Bing [Bot], claudio.fortuna, dasfliege, Google [Bot], Semrush [Bot] and 102 guests