All Posts

When I perform a simulated (test) failover, I get 100% success and everything looks good. However, the moment I try to perform a real failiover, the following error message is displayed "Non-Fatal error information reported during execution of array integration script". Both arrays are talking to each other and the SRM servers can communication with the arrays and each other. The summary page of SRM shows everything as connected and configured, so I don't know what's causing this. As the product's only 1 week old, I don't expect many responses, but this is my message in a bottle. Cheers

Sadly, the error is 'Error occurred' so I'm not sure what's up. I've configured 2 SRM's to communicate which is working. I have a pair of Clarrion's setup using Mirrorview. The SRA is installed and listed in the Manager Type drop down box. When I provide the IP details for the SP and enter the credentials, I click connect and see this error.

I've been working with the beta for sometime. I have about 247 A4 pages of material I've written - I'm hoping to release a book on SRM in the next couple of months. I still have some outstanding questions which I think a VMware employee, or a member of the SRM Team is best placed to answer. 1. Templates Currently templates are not included in SRM, which makes sense as they they not business critical. But I've been thinking there would be nothing stopping anyone - converting a template into VM, storing that on the recovery site - triggering failover, and then converting them into template at the recovery site. I'm think there maybe parts of a DR recovery plan which require the creation of a new virtual machine and templates are the best way. Example. Suppose I have a substantial VDI deployment - it would be costly to replicate/snapshot them when I would redeploy them as part of a pool. To do that I need my templates 2. Stretched VLANs Does the SRM team have any thoughts recommendations on Stretched VLANs. Changing IPs is a roll PITA, even with a guest customization for each and every VM!!! I'm thinking the best route out of this altogether is a stretched VLAN configuration - it would also simply inventory mappings - as the VM would not move from one network to another 3. Placeholder/Shadow VMs Does it really matter where you put your placeholders - local storage seems tempting but if an ESX host goes down its placeholders wouldn't be available. Would the SRM team recommend relatively small LUNs on shared storage that every ESX hosts could see - are there any positions or recommendations on this 4. VM Response Time When you create a recovery plan we can control start-up times. This is a one size fits all value - with no way to customize it on a per-VM basis. After all services on some VMs will take longer to start on another. Does the SRM team plan to change this? In the meantime are there any work arounds? 5. Repair Arrays Button What exactly is the button for - in what ways/scenarios might my array get "damaged" that needs repairing? 6. Powering of VMs before failback I notice that some instructions from the storage vendors require you to power off VMs before starting the failback process. This is ensure they are quiesced. Strictly speaking is this neccessary? We do test runs with VMs powered on. Is it a limitation that varies from storage vendor to storage vendor? Well, that's about it for my questions. I've almost completed the 1st draft of my book on SRM - it needs to go through some levels of proof-reading both from a readability stand-point but also from a technical stand-point. I've got some key guys waiting in the wings who have volunteered to do that for me. Hopefully, I should have "Authors Limited Edition" ready for VMworld - with the book being available for order on lulu.com soon after. Not decided on a price yet - cross that bridge when I get to it! Regards Mike Laverick RTFM Education http://www.rtfm-ed.co.uk/?cat=14 ps sorrry if these questions are RTFM - not had time to review the offical docs that got released with the GA. That's my next step...