Auxiliary Copy Not Running

Problem: Auxiliary copy not running properly in Commvault Galaxy
Error: While accessing a drive the Serial Number obtained is different from expected Serial Number.

Change before the problem arise: None

Now, there are several possibilities for the error.
1: One or more of the drives from the library were replaced but after replacing a drive they were not updated on media agent using "Library and drive configuration"
2: Media agent is not avaialble
3: Drive is not working / marked offline / faulty

Possible Solution for 1:
- Suspend all Jobs
- Stop the media agent services on all media agents
- Go to Control Panel > Library and drive configuration > Select all Media agents > Run Detection on all media agents.

This will update all the drive serial numbers and register them with comcell. Now if any of the drives were replaced, they will be updated in comcell.

Now, resume all the jobs. If you still get the same error then kill that job and initiate another job. Even after initiating a new job, you get the same error then try the work around in 2.

Possible work around for 2:

Keep in mind that all jobs should be suspended at this time but all the media agent services should be working.

This is when you find that media agent on which the library is supposed to be "seen" i.e. the media agent which controls the library is unavailable.

- Try to change the library controller to another media agent
Comcell > Storage Resources > Media agents > Expand"Avaialbe Media agent" > select the library > Right click > Properties > Library controller > Change > Select the alternative library controller > Reset controller.

- Go to Policies > Storage Policies > Select the Policy for which you are running an auxilary copy > Right click > Properties > Data Path > Add > Add the datapath which is the library controller you just selected in the previous step.
- Mark the new datapath as default
- remove the old data path
- kill the current auxiliary copy job
- start new auxiliary copy job
- make sure that it selected "new" library controller(the one you just selected) as the controller for the job.

This will resolve the issue.

The only solution for 3:

- Replace the drive and follow the solution for 1:

There are few other possibilities depending on the errors you receive, if you need more details then feel free to drop me a comment with details, I will be happy to help if I can.


PS: The problem I discovered while trying to resolve this issue is the library was lost from SAN path because of the HBA being disabled by the admin team on the media agent that was the data path for the auxiliary copy, i.e. Possible Case 1.


Cheers!!

Mihir Sangani