Quantum Forum for DXi V5000
v3.1 - Only forever retention if not scheduled by VMPro
Hi there !
In our configuration, we do not use the internal scheduler of VMPro and we have to use an external one.
For this, we have developped scripts which allow us to start backup and then check their status.
With the v3.0.1, there was no problem at all but since we upgraded to 3.1, it's not possible anymore to set a backup retention if we do not use the VMPro Scheduler.
Without the internal scheduler, the retention is forced to "forever".
Does it exist a way to change or configure the retention for a backup when executing it with command lines ?
Thanks for your help.
Replies to This Discussion
-
Permalink Reply by Mark Thacker on
-
Interesting that you are using external scripts. With 3.1, there are significant new advancements in our scheduling capabilities for polices as well as multiple targets and retention periods per period of backup (daily, weekly, monthly, yearly). So, it might be worth re-evaluating the need for an external scheduler.
For policies that are scheduled, you can set a retention copy count of 0 which means forever. So, if you have any sort of a policy defined that you are manually kicking off, you might want to re-check the retention period and make sure it's zero. Actually, double-check the product manual to ensure that I'm write about it being 0.
-
Permalink Reply by FIX Benoit on
-
Hi !
I can't use the internal scheduler even if it's great now :)
It's mandatory for our customer because of other batches. Another "problem" is that the customer have another backup tools (for physical server) and the Production team wanted only 1 product to monitor and check. Maybe we could backup /export but the smartmotion feature is far more powerfull.
What we need is the possibility to set custom retention period without enable schedule in the vmpro.
We do not want "forever" retention. But I can confirm that the retention period is 0 for infinite.
© 2024 Created by Quantum Forum V.
Powered by
