2015-08-06 02:02 AM
in the old world, when I used SnapVault via Protection manager, the destination volume would have been resized by dfpm.
We are in the process of migrating our backup to SnapProtect.
How are secondary volume sizes handled? Do I have to resize manually, or is this done by SP?
Thanks for any info
2015-08-07 12:44 AM
2015-08-07 03:02 PM
Do you see anything on the vault logs about volume resize attempts? I had a look at the provisioning policy in use at my shop but there doesn't seem to be a setting to enable or disable resizing.
2015-08-10 08:06 AM
You might try changing the "Autosize Grow Threshold Percentage:" and the "-Autosize Increment (for flexvols only):" settings for the volume.
I set mine to Grow at 85% and in increments of 100GB. The defaults were not working for me. It seems the volume would fill up faster than it could trigger an autosize.
> vol modify -volume <volume_name> -autosize-increment 100GB
> vol modify -volume <volume_name> -autosize-grow-threshold-percent 85
2015-08-11 12:56 AM
all I could find was a message in SP's job manager (No space left on device):
3748 a30 07/23 03:07:30 2201 Scheduler Set pending cause [DataFabric Manager Backup Job id [9abdbbcbe8f6ed2e:-454c5e88:14eb8365c1b:-22e0] did not complete successfully for Dataset id [9cbbf396-4214-4295-8727-50999bfad63a:app_type=OCU
No mention of resizing, though...
At the moment I am trying to figure out how to get snapvault logs from the filer...