Login or Register to Ask a Question and Join Our Community


Solaris

Need Help On Solaris Cluster Steps For San Migration

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Need Help On Solaris Cluster Steps For San Migration
# 1  
Old 07-30-2013
Need Help On Solaris Cluster Steps For San Migration
I am going to do a SAN Array migration and need the sequence of steps required on the Solaris cluster before moving the old array luns to new array luns.

Here are the steps and I need info on the bold pointsSmilie I might even be wrong on the sequence of steps please correct me if I am wrong)

1. need to move all the cluster services to a single node
2. perform host remediations on the node 2
3. reboot node 2 and move the cluster services to node 2
4. perform host remediations on node 1
5. reboot node 1 and move the cluster services to node 1, shutdown node 2
6. perform the cleanup steps to remove old array luns
7. make sure that the applications dont come back automatically on reboot
8. make necessary changes so that when we reboot the node 1 will be able to use new array luns( because after this step we will remove the old array luns and present new array luns)
9. shutdown node 1
10. start Array migration procedure from old array to new array
11. once we are comfortable with the percentage completed we can turn on node 1
12. turn on node 1 and mount the new volumes from new array
13. turn on node 2 and failover to node 2 to check cluster services are running properly
14 once everything looks fine( this finishes the migration)
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

How to identify if disk is attached to SAN and assist in migration.?

I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX. it has one ldom created on it luxadm probe output --- No Network Array enclosures found in /dev/es Found Fibre Channel device(s): Node... (7 Replies)
Discussion started by: kpatel786
7 Replies

2. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

3. Red Hat

Volume group not activated at boot after SAN migration

I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
Discussion started by: rbatte1
4 Replies

4. HP-UX

SAN Migration question

Hi, I am very new to HP-UX, and we're going to be doing a SAN migration. We're going to take down the machine, and zone it to the new SAN. My question is, will the device names change and will that interfere with the LVM? If the new disks come in with different device names, how would I... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

5. AIX

SAN Migration

Hi all, We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP. Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies

6. AIX

HACMP two-node cluster with two SAN storages mirrored using LVM

HACMP two-node cluster with mirrored LVM. HACMP two-node cluster with two SAN storages mirrored using LVM. Configured 2 disk heartbeat networks - 1 per each SAN storage. While performing redundancy tests. Once one of SAN storage is down - cluster is going to ERROR state. What are the guidelines... (2 Replies)
Discussion started by: OdilPVC
2 Replies

7. HP-UX

SAN Migration of HP-UX hosts

Hello gurus, I am a SAN Admin - not very familiar with the HPUX administration - so need help with the steps in regards to the migration I need to do at my client place. Environment: Migrating from CX4 to VMAX - using OR/Hot Pull. Here are the steps I have put together - HPUX gurus please... (5 Replies)
Discussion started by: jps460
5 Replies

8. Filesystems, Disks and Memory

SAN Disk w/o Cluster

Scenario: I've got 2 M5000's connected to a 9985 SAN storage array. I have configured the SAN disks with stmsboot, format and newfs. I can access the same SAN space from both systems. I have created files from both systems on the SAN space. Question: Why can't I see the file created... (3 Replies)
Discussion started by: bluescreen
3 Replies

9. Filesystems, Disks and Memory

First steps on Ibm SAN DS4500

Hello everyone ! Im new on Ibm San DS4500. Can you give me some tips to this, because I dont want to make a mistake. I have some questions. How can I know how much space get on the san, I cant find it. How can add more space to a partition. Do you have some tutorial about this. I... (0 Replies)
Discussion started by: lo-lp-kl
0 Replies

10. HP-UX

SAN migration

Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch. Any... (0 Replies)
Discussion started by: Hils
0 Replies
Login or Register to Ask a Question

LEARN ABOUT HPUX

fcd_disable_mgmt_lun

fcd_disable_mgmt_lun(5) 					File Formats Manual					   fcd_disable_mgmt_lun(5)

NAME

       fcd_disable_mgmt_lun - select whether or not management luns are discovered in the legacy representation of mass storage devices

VALUES

   Failsafe
   Default
   Allowed values
       Enable discovery of management luns for array devices.

       Disable discovery of management luns for array devices.

   Recommended values
DESCRIPTION

       Management  luns  provide  the means to access the control ports of Fibre Channel disk arrays.  They are represented in both the legacy and
       the agile view of storage devices.  The legacy representation of a management lun is typically created under a separate	virtual  extension
       bus node.  The entry for a legacy management lun looks like this:

       On  a  system with a large number of storage devices connected, creation of management luns can result in an insufficient number of virtual
       extension buses for the legacy representation of data luns.  Since the number of extension buses on  a  system  is  limited  to	256,  luns
       requiring  virtual extension buses above 256 will be unusable through legacy device special files.  Disabling the discovery and creation of
       management luns will free up virtual extension buses for use by data luns.

       The default value for this tunable is

   Who Is Expected to Change This Tunable?
       System administrators who expect to use a large number of storage devices requiring more than 256 extension  buses  through  legacy  device
       special files.

   Restrictions on Changing
       Changes to this tunable take effect immediately.  However, existing management luns will not be removed.

   When Should the Tunable Be Turned On?
       This tunable should be turned on when the system runs out of extension buses for configuring the legacy representation of data luns.

   What Are the Side Effects of Turning the Tunable Off?
       None.

   When Should the Tunable Be Turned Off?
       When the functionality provided by the management lun is desired.

   What Are the Side Effects of Turning the Tunable On?
       Existing management luns in the legacy representation will show up in the state.

   What Other Tunables Should Be Changed at the Same Time?
       None.

WARNINGS

       All  HP-UX kernel tunable parameters are release specific.  This parameter may be removed or have its meaning changed in future releases of
       HP-UX.

       Installation of optional kernel software, from HP or other vendors, may cause changes to tunable  parameter  values.   After  installation,
       some  tunable  parameters may no longer be at the default or recommended values.  For information about the effects of installation on tun-
       able values, consult the documentation for the kernel software being installed.	For information about optional kernel  software  that  was
       factory installed on your system, see at

AUTHOR

       was developed by Hewlett-Packard Company.

SEE ALSO

       ioinit(1M), ioscan(1M), kctune(1M).

							     Tunable Kernel Parameters					   fcd_disable_mgmt_lun(5)