is there an option available, that skips IntelliSnap Snap Backups, when Backup Copy operations are currently running for the subclient ?
On NetApp FAS Systems, a new hardware snapshot cannot be created, while a volume clone is active. For some of the backups on large subclients, this leads to failed backups from time to time. This in my environment, this happens to some of the sublients once a month (4-weekly, before switching from Storage Policies to Plans)
Instead of defining Blackout Windows to statically define when snap backups are to be skipped, it can also be helpful to simply skip the snap backup request, when the subclient is active with a backup copy or mount for restore operation.
rgds Klaus
Best answer by Damian Andre
Hi Klaus,
I think its a valid request, but I am not certain there is a way to make new snap backup jobs dependent upon exiting backup copy completion using the traditional job queue framework.
The software generally does backup copies at the storage policy level, so there is a chance a backup copy running for the SP is working with different volumes for the snapshot copy. So in this regard you would not want to delay the snap using assumed logic at the subclient level. Each discovery could end up adding (or removing) volumes to the backup job, and so much more logic would have to go into detecting the volumes that will be affected vs identifying volumes already in use.
That being said, here is some guidance about this issue in our documentation:
That being said, I think if you turn snapshot_clone_dependency or snapshot-clone-dependency volume option to on, that will mitigate that issue (I know the documentation mentions deletions but its applicable to other busy scenarios as well from memory).
I think its a valid request, but I am not certain there is a way to make new snap backup jobs dependent upon exiting backup copy completion using the traditional job queue framework.
The software generally does backup copies at the storage policy level, so there is a chance a backup copy running for the SP is working with different volumes for the snapshot copy. So in this regard you would not want to delay the snap using assumed logic at the subclient level. Each discovery could end up adding (or removing) volumes to the backup job, and so much more logic would have to go into detecting the volumes that will be affected vs identifying volumes already in use.
That being said, here is some guidance about this issue in our documentation:
That being said, I think if you turn snapshot_clone_dependency or snapshot-clone-dependency volume option to on, that will mitigate that issue (I know the documentation mentions deletions but its applicable to other busy scenarios as well from memory).
but I think the mentioned settings apply only to the legacy DataONTAP 7-mode.
There is no such setting for cdot.
therefore it look like I have to live with the failing backups once a month. I already skip one recovery point on the day I run the full backups, but that is not sufficient for all volumes.
I need to meet a RPO of 6 hrs, which I already expanded to 12hrs for the day, I run full backups (not synfull).
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
