Commvault : Backup capacity utilization based on backup clients

When the Commvault disk library fills up in Commvault, one very useful information to have is the distribution of capacity based on the clients. This information allows the identification of clients that consume the most capacity on the library. 

There are no reports available in the Commcell console that provides this information. However, the following webconsole report (Client Storage Utilization by Storage Policy Copy report) is helpful.

https://cloud.commvault.com/webconsole/softwarestore/#!/135/664/6195
 

Migrate OnCommand performance manager data to unified manager ( Job remain in progress)

Recently, an OCPM (OnCommand performance manager) managed NetApp Cluster data was migrated to OCUM (OnCommand Unified Manager) v7.2P1.

The steps to migrate the cluster data was straight forward and the steps are mentioned here.

The trouble was that after the migration was initiated the job remained IN-PROGRESS for almost 2 weeks and there was no way to ascertain if the job was in progress.

A support case was raised with NetApp and a support bundle was generated. Upon analysis it was found that there was an events table that was too large. Here is a snippet from the logs:

c.n.d.u.m.i.m.o.OpmBaseMigrator (http://OpmBaseMigrator.java:76) - Migrating data from table - continuous_event_participant succeeded in 20,066 sec

2018-11-06 04:59:29,890 INFO  [main] c.n.d.u.m.i.m.o.OpmBaseMigrator (http://OpmBaseMigrator.java:68) - Migrating data from table - continuous_event_participant_stats

2018-11-06 11:47:12,191 INFO  [main] c.n.d.u.m.u.MigrationUtil (http://MigrationUtil.java:96) - Looking for process id - 8,149. Process list command output - Optional[[ 8149 java]]

2018-11-06 11:47:12,265 INFO  [main] c.n.d.u.m.i.MigrationStatusService (http://MigrationStatusService.java:310) - Validate Active Migrations - Found a datasource with id 2 and its java process id 8,149

2018-11-06 11:47:12,269 INFO  [main] c.n.d.u.m.i.MigrationStatusService (http://MigrationStatusService.java:253) - Unable to find data source to migrate or there is no datasource in scheduled status.

If you are running into a similar issue then it is best to raise a support case and share a support bundle with them .

If you are experiencing something similar then feel free to leave a message/note. 

Filter Hyper-V VMs using notes || Commvault content filters

Recently, there was a request to filter a bunch of VMs from backups within Commvault. 

The following process was followed: 

1) Under the subclient properties, a filter was created for the rules that looks for notes as 'nobackup'.  See screenshot below. 

2) The VM engineer was informed to add notes to the hyper-V VM. 

There are two ways to do it: 

2.a)   Hyper-v Manager sees nobackup in Notes when highlighting the VM Settings>Management>Name to edit the Notes section

  

2.b)Virtual Machine Manager sees nobackup in Properties>General>Description and can be edited directly

Commvault V11 SP13 upgrade / update and backup failures

Recently, the Commserve and media agent of a Commvault environment was updated to SP13. Post the update, backups failed to run with client reporting errors related to 'client services not running'.

It was a big mess with all clients being impacted.

The fix to the issue was to download and install the hotfixes for SP13 from cloud.commvault.com and then restart the services.

Hope this helps someone out there.

Leave a comment to let me know that you share my pain. :-) 

Commvault SQL restore fails

Recently, while performing a restore of a SQL DB in Commvault, the restore job failed.  The attempt tab of the restore job showed no details and the events tab had the following entry with a timestamp [note the time stamp as it will be handy when reviewing logs].

Received failed message for job [job ID] , phase [Database Restore]. 

The next step was to login to the SQL client and review the SQLiDA logs. (if the access to the client is not available then right click the Commvault restore job and click on 'view logs' and look for the following section and search for the string 'VD_E_TIMEOUT'

File    : SQLiDA.log

Here is how the logs might look:

Solution: 

1. Restart the commvault services on the client. 
2. Ensure the client is running the latest service pack (in my case the client had to be updated from V11 SP 9 to V11 SP13) 
3. Most importantly, follow the Commvault link and apply both the VDI settings (VDI timeout and VDI retry).  http://documentation.commvault.com/commvault/v11/article?p=18144.htm