Disk Enclosures
cancel
Showing results for 
Search instead for 
Did you mean: 

Fail to Create Snapshot

Keynes Lee
Regular Advisor

Fail to Create Snapshot

I created a DR GROUP. And waited for the synchronization completed.

I tried to create a SNAPSHOT from the destination vidsk. But it "ALWAYS" says:

Operation Failed
The condition of the object is 'in-progress'. The command cannot be execute while object is in this condition.

Sigh... what a SIMPLE message. I tried all the day but still can't find out the root cause or any solution ITRC.

Please help me!
12 REPLIES
IBaltay
Honored Contributor

Re: Fail to Create Snapshot

Hi,
you could review this doc to check if your replication is e.g. synchronous or asynchronous (standard or enhanced) and all other things around the correct installation.
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01489857/c01489857.pdf

in asynchronous mode (even enhanced) is always a possibility of destination vdisks i/o inconsistency (write history log overflow) and thus the snapshot from the destination EVA needs not be consistent...

also
this thread could help you (you should use:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1136035
the pain is one part of the reality
Keynes Lee
Regular Advisor

Re: Fail to Create Snapshot

Thanks for replying!

I created the DR group in Synchronization mode.
And actually, I created several DR group. But only this one can't make a snapshot.

I found some another logs as below

In EVA Management Agent Eventlog
Code 3028, Status Description Unavailable

In RSM
Replication failed - Command View error replication failed for volume: HR_PROD_1 - CommandView error: Code=600017 Description=Error cannot create object.:The condition of the object is 'in-progress'. The command cannot be execute while object is in this condition.

Waiting for you kindly reply! Thank you very much!
IBaltay
Honored Contributor

Re: Fail to Create Snapshot

what EVAs are there pls?
the pain is one part of the reality
IBaltay
Honored Contributor

Re: Fail to Create Snapshot

can you check it you have available free space on the destination EVA pls?
the pain is one part of the reality
IBaltay
Honored Contributor

Re: Fail to Create Snapshot

it seems like you have no free space to finish the replication of this vdisk at the destination EVA
the pain is one part of the reality
Keynes Lee
Regular Advisor

Re: Fail to Create Snapshot

Thanks for replying!

We are using EVA8000

And I think there should be enough space. As there is another Disk Group, LUN size : 1.9TB can make snapshot every time.

But the one which only using size 200GB, can complete the synchronization but just can't make a snapshot.

Capacity as below
Total : 7380.06 GB
Occupancy: 5954.87 GB
IBaltay
Honored Contributor

Re: Fail to Create Snapshot

a) Maybe the quickest way is to recreate the failed DR group (vdisk). It could be that it timed out during the initial replication load
b) also you can try to move the the destination vdisk to the second controller. Wait for the completion allocation and check it.
the pain is one part of the reality
Keynes Lee
Regular Advisor

Re: Fail to Create Snapshot

Would you please tell me how to move the vdisk to another controller ?

I can't see this function.

Thanks
IBaltay
Honored Contributor

Re: Fail to Create Snapshot

it can be moved e.g. via the command view,
you will go to the vdisk and look into its presentation.
If the set preferred path was Controller A (failover/failback), you will change it to controller B
the pain is one part of the reality
Keynes Lee
Regular Advisor

Re: Fail to Create Snapshot

I tried that, but nothing occurred. It still using the original controller.

Seems there is some problem with Command View.

I'll keep try that. Thanks for your help
IBaltay
Honored Contributor

Re: Fail to Create Snapshot

ok, but did you save it pls? Because otherwise it stayed as it was
the pain is one part of the reality
IBaltay
Honored Contributor

Re: Fail to Create Snapshot

hi, here is the rsm 4.0 doc page:
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual〈=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=471572

maybe u can have a look into the admin guide
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01376123/c01376123.pdf
and look/analyze the logs
and there are also some troubleshooting tips there:

also in the user guide
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01491168/c01491168.pdf
there are some troubleshooting ideas e.g trace log, etc.



the pain is one part of the reality