|
|
Sponsored Content
Operating Systems
Solaris
Need Help On Solaris Cluster Steps For San Migration
Post 302838925 by sunshinedeepu on Tuesday 30th of July 2013 10:53:27 PM
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 points
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)
Here are the steps and I need info on the bold points
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)
|
|
10 More Discussions You Might Find Interesting
1. HP-UX
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
2. Filesystems, Disks and Memory
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
3. Filesystems, Disks and Memory
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
4. HP-UX
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
5. AIX
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
6. AIX
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
7. HP-UX
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
8. Red Hat
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
9. AIX
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
10. Solaris
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
LEARN ABOUT OPENSOLARIS
clinfo
clinfo(1M) System Administration Commands clinfo(1M) NAME
clinfo - display cluster information SYNOPSIS
clinfo [-nh] DESCRIPTION
The clinfo command displays cluster configuration information about the node from which the command is executed. Without arguments, clinfo returns an exit status of 0 if the node is configured and booted as part of a cluster. Otherwise, clinfo returns an exit status of 1. OPTIONS
The following options are supported: -h Displays the highest node number allowed to be configured. This is different from the maximum number of nodes supported in a given cluster. The current highest configured node number can change immediately after the command returns since new nodes can be dynami- cally added to a running cluster. For example, clinfo -h might return 64, meaning that the highest number you can use to identify a node is 64. See the Sun Cluster 3.0 System Administration Guide for a description of utilities you can use to determine the number of nodes in a cluster. -n Prints the number of the node from which clinfo is executed. EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error occurred. This is usually because the node is not configured or booted as part of a cluster. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5) SunOS 5.11 12 Mar 2002 clinfo(1M)