I could not find a clear answer on this, so i will post it here.
I activated "per VM backup" on our repositories.
I however would love to know what will happen with the backupdata before the change.
Two backupjobs were given an "active full" to see if the "per VM backup chain" would be created and that seemed to work like a charm, i clearly see the seperate VM backups.
But the old data is still in the directory.
A) is this data still usefull
B) is this data automatically going to be removed when the retention is matched?
C) can i already manually remove this to clear up some space?
-
- Service Provider
- Posts: 21
- Liked: never
- Joined: Oct 07, 2016 1:58 pm
- Full Name: Denit Support
- Location: the Netherlands
- Contact:
-
- Product Manager
- Posts: 6551
- Liked: 765 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: Switching to "Per VM backup chain" and old retention
Hi,
A) Yes
B) Yes
C) Yes, however it is not recommended.
Thanks
A) Yes
B) Yes
C) Yes, however it is not recommended.
Thanks
-
- Service Provider
- Posts: 21
- Liked: never
- Joined: Oct 07, 2016 1:58 pm
- Full Name: Denit Support
- Location: the Netherlands
- Contact:
Re: Switching to "Per VM backup chain" and old retention
Thanks!
That was a quick reply, i appreciate it.
This helps me a a lot.
That was a quick reply, i appreciate it.
This helps me a a lot.
Who is online
Users browsing this forum: Google [Bot] and 57 guests