I recently upgraded my CommCell from v10 SP13 to SP14. As usual, the upgrade was easy. Centrally deployed, no issues.
The next set of scheduled fulls kicked off a few days later, and soon after there appeared to be an issue with Synthetic Full backups.
In the Job Controller they appeared to be normal. Throughput data was there, there were no errors, and the jobs were not pending or waiting, but rather in the running state. I was concerned though, as they appeared to be still running well after I would have expected them to be complete.
Clicking on the job details showed the “Last Update Times” were over 1 day, where ordinarily these should be a maximum of 5 minutes between updates..
My first action was to Suspend and then Resume the jobs, which sometimes “wakes” them up if they have stalled. This worked initially, but later on they would again show the extended update times. Cycling the services on the Media Agents or Clients had no effect.
When I checked initially, there was no info regarding anything similar on the CommVault forums or on the Knowledge Search on Maintenance Advantage.
However, checking again today showed there has been a HotFix released on the 21st July. HotFix 2, to be precise.
The conditions weren’t a 100% hit, but seemed close enough for a try.
Once the HotFIx was added to the Cache and then applied to the CommCell, Media Agents and then the remaining clients, jobs completed within the expected timeframes and CommVault goes back on it merry way.
The DataLookAhead reader is a particularly common setting to have added to assist with Synthetic Fulls, Aux copies etc. While the info didn’t mention Synth Fulls, I had a hunch their was a match.
Check if you are using this setting by going into a Media Agent’s Properties, then Advanced Settings then Additional COnfigurations;
Data is too important to risk, so if you have upgraded to V10 SP14, install this hotfix to avoid any dramas with Aux copies and Synthetic Fulls.