cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Lock Changer.cfg error in event logs

Bruce_Summers_2
Level 3
Hi,

10.1 5629 sp1
The customer is using removable media shared from another machine. New removable drives or old drives which have been formated and no longer contain the b2d folder recieve the following error at the start of the backup job. The job throws two of the following errors in the event logs and then starts.

An error occurred while processing a B2D command.
Changer: LockAndRefreshChangerConfig() Unable to Lock Changer.cfg (\\Srv04\Backuptest\VERITAS\B2D\Changer.cfg).

Sometimes it will also give an error about readblock failures before the job starts. The shared removeable media is shared out with full rights to everyone and the permissions are full to everyone. Why the errors?
2 REPLIES 2

shweta_rege
Level 6
Hello,


As a preliminary step check if the media server is in paused state. If yes, change the state. Refer to the following technotes:

Device jobs remain in a "pending" or "Queued" state indefinitely; and "scheduled" jobs do not run at their appropriate time

http://seer.support.veritas.com/docs/191594.htm

Scheduled jobs are reported as "Missed" in the Activity Monitor.

http://seer.support.veritas.com/docs/245689.htm


1. Verify if the B2D folder is online.


Refer the following Document:



http://seer.support.veritas.com/docs/248709.htm

3. Refer to the following technotes:



http://seer.support.veritas.com/docs/236295.htm

4. Create a new Backup to Disk folder and perform the backup. Verify the results.




Thank You,

Shweta

Bruce_Summers_2
Level 3
After further investigation. The errors appear when the changer.cfg file does not exist on the removable media. BE places two errors in the event logs and then creates the changer.cfg file and continues the backup operation. Why do the errors occur when the changer.cfg file is not present and how do we stop the errors?