Unsolved
This post is more than 5 years old
60 Posts
0
1613
Open Replicator
Hi,
Does anyone can answer, is there any precaution that has to be taken while doing Solaris 10 server migration using open replicator
Unsolved
This post is more than 5 years old
60 Posts
0
1613
Hi,
Does anyone can answer, is there any precaution that has to be taken while doing Solaris 10 server migration using open replicator
Top
Vaibhav2025
13 Posts
1
April 11th, 2013 11:00
Hello Ashwini,
I have performed few Solaris migrations using Open Replicator. All that was required was to confirm that the host was array compliant, if not do the necessary updates and the OR worked just fine.
Balaji6583123
3 Posts
0
October 22nd, 2013 06:00
Hi Ashwini,
Were you able to perform the migration os solaris servers without any problem?
I haev 5 Solaris servers moving from one site (source is DMX) to another (destination is VMAX).I am using Open replicator as well.I have made sure that all the servers' components are compliant with Enginuity matrix of the destination VMAX?
Is there anything else to be take care of?
Balaji
anand2405
20 Posts
0
October 22nd, 2013 06:00
Hi Ashwini/Balaji
As mentioned by Vaibhav you must check for the host compliance with the Storage, just follow the Host integration guide for Solaris with Vmax, have the necessary flags and PER bits set.
Based on the hot/cold or pull/push methodology you are using the state of the volumes should be maintained, other than that there is no other precautions to be taken.
anand
Balaji6583123
3 Posts
0
October 22nd, 2013 07:00
Thanks Anand for the prompt response.
Is there any special flag to be used here for Solaris OS.There are none so far on this FA,.We are planning to use 1E0 and 2E0 for host access on the VMAX.
Below are the SCSI flag settings
1E0
SCSI Flags
{
Negotiate_Reset(N) : Disabled
Soft_Reset(S) : Disabled
Environ_Set(E) : Disabled
HP3000_Mode(B) : Disabled
Common_Serial_Number(C) : Enabled
Disable_Q_Reset_on_UA(D) : Disabled
Sunapee(SCL) : Disabled
Siemens(S) : Disabled
Sequent(SEQ) : Disabled
Avoid_Reset_Broadcast(ARB) : Disabled
Server_On_AS400(A4S) : Disabled
SCSI_3(SC3) : Enabled
SPC2_Protocol_Version(SPC2) : Enabled
SCSI_Support1(OS2007) : Enabled
WP_Bypass(WPBP) : Disabled
2E0
SCSI Flags
{
Negotiate_Reset(N) : Disabled
Soft_Reset(S) : Disabled
Environ_Set(E) : Disabled
HP3000_Mode(B) : Disabled
Common_Serial_Number(C) : Enabled
Disable_Q_Reset_on_UA(D) : Disabled
Sunapee(SCL) : Disabled
Siemens(S) : Disabled
Sequent(SEQ) : Disabled
Avoid_Reset_Broadcast(ARB) : Disabled
Server_On_AS400(A4S) : Disabled
SCSI_3(SC3) : Enabled
SPC2_Protocol_Version(SPC2) : Enabled
SCSI_Support1(OS2007) : Enabled
WP_Bypass(WPBP) : Disabled
Secondly the hosts will be using Veritas cluster server and VxVM for managing the VMAX volumes after migration.
Is there any special flag to set for these as well??
Can you also elaborate a bit more about the PER bits as well?
Thanks in advance,
Balaji
anand2405
20 Posts
1
October 22nd, 2013 07:00
the flags which are set is correct, except for the OS2007 I do not see that mentioned in the elab navigator. Also the Host Connectivity guide talks about the requirements for the the VxVM and the SPC2 flag. Kindly go through the Connectivity guide.
Anand
asadmadani
4 Posts
0
October 21st, 2015 12:00
flag os2007 is for windows but you can let it be enabled. SPC2 is the flag for solaris which I see is enabled. You are good with flag setting.