All told, it probably takes about 8 to 11 seconds per item to delete it, then you need to navigate through the items list again to find the next aged item and repeat this process. Unfortunately, it only allows you to select one item at a time, then click delete, and then click through an “are you sure” warning. The StoreOnce 4.x WebUI includes the option to list the items in the Catalyst store, and delete them. Because Veeam wasn’t detecting them, I couldn’t use the VBR interface to just select them and delete them from disk. This however was much easier to say than to do. All I needed to do was delete these orphaned files!

Deleting these orphaned Veeam files would easily free up enough space in the source Catalyst store to match what was available in the in inherited StoreOnce. Upon further investigation I discovered that the customer’s Catalyst store had several thousand orphaned Veeam backups from over the years that were no longer present in the VBR database, nor where they picked up by Veeam when rescanning the repository. The only issue was the size of the existing StoreOnce Catalyst store was larger than the available capacity on the inherited StoreOnce, which already had the capacity expansion licensed and installed.

We made the decision to enable Catalyst copy from the customer’s existing StoreOnce to the inherited StoreOnce to enhance the customers backup and recovery strategy.

Recently, I had a customer go through a merger, and they inherited another StoreOnce located at a remote site.

Veeam delete vib file