- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, we are making progress. I did to things, that let us get a lot further:
- set the serach path for the perl bin folder (as on p62 of "0003 - Implementing DR solutions with IBM Storwize V7000 and VMware Site Recovery Manager.pdf")
- set "Test MDisk Group ID" (for the SRA configuration on the SRM Server) to 0 instead of the actuall name of the Pool (there is no such thing as a MDisk Group ID - so I'm assuming they mean the pool name)
Having done this - now the SRA creates a flash copy (when I run a recovery plan test), but the flash copy map just sits at 0%. So it seems to create the empty snapshot volume, but can't copy the contents of the "real" replicated volume to it.
Then we realised that when we create a Flash Copy Snapshot manually - it does the same thing. We thought that it was finished after the first few seconds when a target volume is created, but it turns out it's just sitting there at 0% when trying to copy into the snapshot volume.
We've logged a call with IBM, so we'll see if they can advise us what's not right with our SAN. Then maybe the SRA scripts will actually work. The good thing is - after I cancel the test recovery plan (and wait a while for it to actually cancel and finish) - the cleanup script works fine. So it seems that the SRA scripts are actually comminicating with the SAN OK.