Subscribe

OCUM doesn't start protection task because storage service member is locked

[ Edited ]

Hi,

I experience lock state on storage service member and I wondering if it's possible to release this lock using  <storage-service-modify>API  or something similar.

To solve this issue, i had to restart OCUM appliance, that is not very useful.

 

Message was

Storage service member 'gdcsvm201.swatchgroup.net:/gdc_fcp_sap_gdc01889_05' of storage service 'CC-its-commserve_SP-16_Copy-44' is currently locked by another operation ([3eb5e92fe4418864:3eeba592:150b570a9c1:-47c8]).

 

 

 

Regards,

François

 

 

Re: OCUM doesn't start protection task because storage service member is locked

Did you confirm that there wasn't a conflicting job happening to lock the snapshots / volume during that time?

Re: OCUM doesn't start protection task because storage service member is locked

Yes no Simpana job that was running anymore. no conflict.
The lock was on storage service member record in ocum (MySQL db ).
Nothing to do with volume or snapshot.
But probably that coming from a job which not finished leaving a dead lock.

Re: OCUM doesn't start protection task because storage service member is locked

Did you find a solution to this problem?

 

-Jacl

Re: OCUM doesn't start protection task because storage service member is locked

[ Edited ]

Not yet.

Actually support said caching tables are populated during job start and should be cleaned at the end.

Unfortunatly sometime no clean occurs and lock stays indefinitely until reboot.

Bug numbers 850522 & 953795 are opened for that.

 

François

 

 

Re: OCUM doesn't start protection task because storage service member is locked

So does this mean the job would never complete or run until reboot?

 

I have the same error on one of my jobs..... i dnt understand