This Question is Possibly Answered
1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
Iuridae wrote:
Hi Dex,
I assume that the read-only LUNs will be added once a test failover/failover will occure?
Yes these LUNs will be seen when the failover is completed.
Hi Dex,
I assume that the read-only LUNs will be added once a test failover/failover will occure?
Yes these LUNs will be seen when the failover is completed.
If you find this information useful, please award points for "correct" or "helpful".
1 bindToController succesfull
1 Current CGN=508
1 2009-01-20:: 16:41:35:INFO:main:Done with failover
1
1 Error:
1
1 ",
1 msg = "Message exceeds database maximum string length."
1 }
1] ,
1 msg = "Message exceeds database maximum string length."
1 }
We have been struggling with that error and haven't found a solution to it. First impression is that some column in SRM datastore is to short.
We are running SRM 1.0 update 1 and SRA 1.00.35.07 and recieves that error when we run a test failover.
Any help would be appreciated.
"Message exceeds database maximum string length." error is harmless. However, it might indicate that storage operation failed. Details about storage failure are in the SRM logs. Could you post these logs from recovery site?
-Masha
-Masha
This message indicates that you've run out of free disks during the testFailover process. See note on restriction in 01.00.35.07 Readme. This restriction will be lifted in an upcoming SRA release.
Yes, thats correct. When we made some disk unconfigured the error disappeared.
For the snapshot to work there need to be free disks thats isn't a part of a raid-set.
Config: 2 x IBM DS 5100 firmware 07.36.12.00, synchrone replication
VMware ESX 3.5 U3 including all January 2009 updates
VMware SRM version 1.0.1 build 128004
Problem: We have problems with configuring the SRA. The first problem was the following error during the first screen in the SRA
LUN's with duplicate IDs or numbers..................
We had the following config:
host a lun a mapped with lun id 0 (vmware cluster)
host b lun b mappeld with lun id 0 (Windows cluster host)
I changed all the LUN id with unique numbers. Now the error went away,
The following problem is that the SRA does not see replicated datastores in the last screen in the SRA. The LUNs are all in sync and replicated.
In the SRM logs i found the following errors:
2009-02-12 15:49:25.084 'SanConfigManager' 4144 verbose Recomputing LUN groups for array pair '600a0b80004771f400000000493389ff' --> '600a0b80004770680000000049364b17'
2009-02-12 15:49:25.084 'SanConfigManager' 4144 verbose Found 20 replicated LUN pairs
2009-02-12 15:49:25.084 'SanConfigManager' 4144 verbose No lun groups created since there are no replicated datastores
Has anybody a suggestion for this problem?
www.ivobeerens.nl
VMware ESX 3.5 U3 including all January 2009 updates
VMware SRM version 1.0.1 build 128004
Problem: We have problems with configuring the SRA. The first problem was the following error during the first screen in the SRA
LUN's with duplicate IDs or numbers..................
We had the following config:
host a lun a mapped with lun id 0 (vmware cluster)
host b lun b mappeld with lun id 0 (Windows cluster host)
I changed all the LUN id with unique numbers. Now the error went away,
The following problem is that the SRA does not see replicated datastores in the last screen in the SRA. The LUNs are all in sync and replicated.
In the SRM logs i found the following errors:
Has anybody a suggestion for this problem?
www.ivobeerens.nl
There will be a new IBM SRA build out shorly that should resolve this error. Upgrade the SRA at both sites once it releases. I'll check to see how soon.
i've got a new SRA (it's not on the VMware site) from IBM that solves the SRA problem but introduces another.
www.ivobeerens.nl
www.ivobeerens.nl
i've got a new SRA (it's not on the VMware site) from IBM that solves the SRA problem but introduces another.
Could you provide detail about the new problem?
-Masha
when i run i recovery plan with one vm with one disk everything is okay. When i run the recovery plan with a vm with two or more disks (one two of more luns) the test recovery fails on the prepare strorage.
www.ivobeerens.nl
here is the SRM recovery plan log:
| 2. Prepare Storage | Error: Non-fatal error information reported during execution of array integration script: testFailover Output: 2009-02-13:: 13:47:54:INFO:main:Command is testFailover2009-02-13:: 13:47:54:INFO:main:Calling failover :: Command "C:\Program Files\VMware\VMware Site Recovery Manager\external\perl-5.8.8\bin\perl.exe" "C:/Program Files/VMware/VMware Site Recovery Manager/scripts/SAN/IBM/failover.pl" temp46122009-02-13:: 13:47:54:QUITE:main:Logging data for failover2009-02-13:: 13:47:54:INFO:failover:Parsing the failover input.....2009-02-13:: 13:47:54:INFO:testFailover:Parsing the testFailover input.....2009-02-13:: 13:47:54:INFO:MAIN:Entry (2009-02-13 01:47:54) |
00:00:36 |
| 2.1. Attach Disks for Protection Group "PG01" | Error: Non-fatal error information reported during execution of array integration script: testFailover Output: 2009-02-13:: 13:47:54:INFO:main:Command is testFailover2009-02-13:: 13:47:54:INFO:main:Calling failover :: Command "C:\Program Files\VMware\VMware Site Recovery Manager\external\perl-5.8.8\bin\perl.exe" "C:/Program Files/VMware/VMware Site Recovery Manager/scripts/SAN/IBM/failover.pl" temp46122009-02-13:: 13:47:54:QUITE:main:Logging data for failover2009-02-13:: 13:47:54:INFO:failover:Parsing the failover input.....2009-02-13:: 13:47:54:INFO:testFailover:Parsing the testFailover input.....2009-02-13:: 13:47:54:INFO:MAIN:Entry (2009-02-13 01:47:54) |
www.ivobeerens.nl
This was a local build intended to be a possible hotfix to an issue. There are later versions which are in test now. Please PM me for details.
Actions
VMworld Sessions & Labs
Online access to the latest VMworld Sessions & Labs and online services.
Learn morePurchase PSO Credits Online
Purchase credits to redeem training and consulting services online.
Buy Now