topic Re: Fail to Create Snapshot in Disk Enclosures

Fail to Create Snapshot

Keynes Lee — Sat, 30 Aug 2008 10:55:03 GMT

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!

Re: Fail to Create Snapshot

IBaltay — Sat, 30 Aug 2008 12:21:02 GMT

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

Re: Fail to Create Snapshot

Keynes Lee — Sat, 30 Aug 2008 13:16:48 GMT

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!

Re: Fail to Create Snapshot

IBaltay — Sat, 30 Aug 2008 13:30:31 GMT

what EVAs are there pls?

Re: Fail to Create Snapshot

IBaltay — Sat, 30 Aug 2008 13:40:29 GMT

can you check it you have available free space on the destination EVA pls?

Re: Fail to Create Snapshot

IBaltay — Sat, 30 Aug 2008 13:42:18 GMT

it seems like you have no free space to finish the replication of this vdisk at the destination EVA

Re: Fail to Create Snapshot

Keynes Lee — Sat, 30 Aug 2008 13:57:03 GMT

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

Re: Fail to Create Snapshot

IBaltay — Sat, 30 Aug 2008 17:02:53 GMT

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.

Re: Fail to Create Snapshot

Keynes Lee — Sat, 30 Aug 2008 18:01:09 GMT

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

I can't see this function.

Thanks

Re: Fail to Create Snapshot

IBaltay — Sat, 30 Aug 2008 18:09:15 GMT

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

Re: Fail to Create Snapshot

Keynes Lee — Sat, 30 Aug 2008 18:16:18 GMT

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

Re: Fail to Create Snapshot

IBaltay — Sat, 30 Aug 2008 18:18:57 GMT

ok, but did you save it pls? Because otherwise it stayed as it was

Re: Fail to Create Snapshot

IBaltay — Sat, 30 Aug 2008 19:22:05 GMT

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.