Hi Guys
I have a question regarding data, policys and retention.
All policys has been setup using tags, so when a new vm is added, just add a tag and then it will be backed up.
Scenario 1.
Customer has a VM, which he after several months want a different retention on, in this case they want to prolong it, so instead of 1 year they now want 3 year.
In this policy there is several other vm's, only one VM should have the prolonged retention.
Is it possible to prolong for just one VM, or can we somehow move the retention to another policy?
Maybe the data is structured per. vm, so the policy with longest retention is the one deciding for all others ?
Scenario 2.
Customer wants to change policy for a VM, and sets another tag. Will this then create a new full chain, or use the chain from the other policy ?
Scenario 3.
As in scenario 2. the customer forgets to remove the other tag, so a VM has 2 tags and by that 2 policys, what would happen mere in terms of chain, data amount etc ?
-
- Service Provider
- Posts: 49
- Liked: 3 times
- Joined: Mar 04, 2021 2:17 pm
- Full Name: Kim Svane
- Location: Denmark
- Contact:
Retention and changing of jobs
Kim Svane @ any.cloud
-
- Product Manager
- Posts: 5838
- Liked: 1220 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Retention and changing of jobs
1. This is not possible. You would have to move that VM to another policy to apply those new retention settings (which starts a new chain).
2. The existing snapshots/backups are removed upon their retention. A new backup chain will be created as it may go to a different repository.
3. The policy with the highest priority (listed in the policy overview) will "win". This means that if you configure a second policy that has lower priority, the first retention settings will remain and nothing changes. If you do change the priority, it's the same answer as scenario 2: a new chain starts.
2. The existing snapshots/backups are removed upon their retention. A new backup chain will be created as it may go to a different repository.
3. The policy with the highest priority (listed in the policy overview) will "win". This means that if you configure a second policy that has lower priority, the first retention settings will remain and nothing changes. If you do change the priority, it's the same answer as scenario 2: a new chain starts.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Service Provider
- Posts: 49
- Liked: 3 times
- Joined: Mar 04, 2021 2:17 pm
- Full Name: Kim Svane
- Location: Denmark
- Contact:
Re: Retention and changing of jobs
Hi Niels
So the best way here is to change the retention for the policy, by going into the schedule and prolonging the yearly retention ?
So the best way here is to change the retention for the policy, by going into the schedule and prolonging the yearly retention ?
Kim Svane @ any.cloud
-
- Product Manager
- Posts: 5838
- Liked: 1220 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Retention and changing of jobs
That will affect every VM in that policy but most likely is the better option. I think the best way to handle this is to discuss it with your customer. They will have a period of double chains after which it will be cleared out (and some extra costs). It's a bit hard for us to make that choice
.

Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Service Provider
- Posts: 49
- Liked: 3 times
- Joined: Mar 04, 2021 2:17 pm
- Full Name: Kim Svane
- Location: Denmark
- Contact:
Re: Retention and changing of jobs
For sure, already talked with them. And suggested this method.
I just wanted to be sure that it was thé wy to go
Thanks
I just wanted to be sure that it was thé wy to go

Thanks

Kim Svane @ any.cloud
Who is online
Users browsing this forum: No registered users and 3 guests