Attribute Changer 11.30 download the new for windows

This is enough to consider another product backup like Veeam and not looking back.

I have been working in IT for many years, and the support we are receiving from Commvault is not what we are used to from other vendors. Asked managers to escalate the issue to engineering/development and they continue to ignore us. The issue has been at level 2 for more than two weeks. We ask support to deactivate the 'WORM Storage' functionality of all storage policies. The same thing happnes if you have aux copies and the destination database is sealed. Full copy on ALL infraestructure.Īlso a problem if you have agents installed all over the world with low bandwidth and now you need to run a full copy. All lines saturated, having to pause the copies and given the size of the copy, it is possible that when the copy is finished the database will be sealed again.the snowball effect that backup administrators love so much Now when the database is sealed and a new one is created, there is no baseline and the first copy that is executed is a full copy. Our copies are a mix between incremental copies and synthetic copies. Why was the 'WORM Storage' functionality activated at the storage policy level if we did not have it activated at that level? In addition, we have not been able to plan the increase of space in the libraries (run out of space on one of them), nor have we been able to adjust the retention of copies before this functionality was activated. Now we cannot delete backups, nor change the retention of our copies and ALL databases will be sealed every X days, micro-prunning disable. We updated version 11.28 to 11.30 and suddenly the “WORM Storage” feature is activated in ALL storage policies at storage pool level.Īs per the below document, this changes are applied on SP30 onwards, if hardware WORM is enabled: We could change the retention of our copies, delete backups, micro-prunning working, and our databases were NEVER sealed.

We are not aware of having activated this functionality and as support indicated, there is no trace that we have executed a workflow to activate it.ĭespite that, the WORM functionality was not active in any of our Storage Policies, only at the disk library level. Hardware WORM was active on all of our disk libraries.

Attribute Changer 11.30 download the new for windows