Quick Backup is very useful.
But we cannot set max retention for quick backup.
So if user perform quick backup many times, total backup size is increased.
Do you know a good idea for limiting the number and size, etc.?
-
- Enthusiast
- Posts: 80
- Liked: never
- Joined: Apr 30, 2013 1:19 am
- Full Name: Yukinobu Asami
- Contact:
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Specific limitation for Quick Backup
Hello,
By the definition Quick Backup is not a full-fledged backup and its incremental backups are not counted as restore points because the contain data of selected VM(s).
By the definition Quick Backup is not a full-fledged backup and its incremental backups are not counted as restore points because the contain data of selected VM(s).
Quick backup restore points will be deleted when the job has predefined number of full-fledged restore points in the chain. So, my advice is to set retention policy for backup jobs accordingly. Thanks.Yukinobu wrote:So if user perform quick backup many times, total backup size is increased.
-
- VP, Product Management
- Posts: 27377
- Liked: 2802 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Specific limitation for Quick Backup
Just our of curiosity why do user can run quick backup many times? In order to do some test with production VM? Why not to use on-demand sandbox instead?
Who is online
Users browsing this forum: Baidu [Spider], Semrush [Bot] and 67 guests