Advance disk, High Water Mark and New jobs

Hi Marianne,

Thanks for taking time and providing a suggestion. Will try to stick to this rule in my next upgrade process.

Due to a limited change window, I had to take a 3 phased approach for the Master and media server upgrades. As part of the upgrade, I am also migrating from Veritas volume manager to zfs, hence just the post upgrade preparation itself took me around 7 hours. And I also had to include times for the upgrade, testing (liase with app and server teams) and rollback without affecting the scheduled backup times. :-(

As a temporary fix(till the issue resolves), I am planning on implementing the below. I guess this should will remove the duplicated images and stop disk from hitting the high water mark.??

During a quiet time, executing a cronjob to force image cleanups:

nbdevconfig -changedp -dp AdvanceDiskPool2 -stype AdvancedDisk -hwm 0 -lwm 0

nbdelete -allvolumes -force
bpimage -cleanup -allclients

nbdevconfig -changedp -dp AdvanceDiskPool2 -stype AdvancedDisk -hwm 90 -lwm 40

I would appreciate any comments/suggestions on the above approach.

- Amar