Sponsored Content
Full Discussion: Cluster 6.1 storage move
Operating Systems AIX Cluster 6.1 storage move Post 302949019 by bakunin on Monday 6th of July 2015 05:38:34 AM
Old 07-06-2015
Quote:
Originally Posted by snchaudhari2
The plan that our architect implemented in summary is :
shutdown the source servers,
replicate the old luns with new luns,
remove the old luns and allocate new luns.
Bring the servers up.
The problem with this plan is:

1. the new LUNs will have different WWNs and therefore the volume group information of the system will not be consistent. Basically you will have to build the cluster resources anew.

2. You need a (complete) downtime to do this as your storage guy planned. What i described will need no downtime at all. To reconfigure all the VGs and RGs plan at least 1-2 hours (30 min to actually do it, 30-90 min in contingency) and you will not know if everything went well until you do an "extended verification and synchronisation". (Technically speaking, you will be creating new VGs, which just happen to have the same name as the old ones and you will build new ressource groups from them, which happen to have the same name as the old ones.)

I hope this helps.

bakunin
 

5 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Veritas Storage Foundation basic and Core cluster solaris 10 release 7 install

After much hitting my head to the wall with this meesages root@crasher /workzone/dvd4_sfb-sol_x64]#./installer -verbose -installonly 5.0MP3 Installation Program Copyright (c) 2008 Symantec Corporation. All rights reserved. Symantec, the Symantec... (1 Reply)
Discussion started by: tristezo2k
1 Replies

2. UNIX for Advanced & Expert Users

Any ideas how to accomplish this storage move?

We have a datacenter in another part of the country with about a 100Mb WAN between that datacenter and the local datacenter. The remoted datacenter has about 20TB of data on roughly 75 servers that all must be moved to this datacenter with minimal downtime. Please help me come up with the best way... (2 Replies)
Discussion started by: keelba
2 Replies

3. Solaris

Sun Cluster/Storage question

Hi Bros, I am a newbie to this cluster environment...my workplace is a mess of Sun solaris server, oracle database, Cisco switch, router, MS Server, Windows PC..so and so..now my boss ask me to come out with a procedure for maintenance of storage array in our sun cluster environment..I read few... (12 Replies)
Discussion started by: xavierantony
12 Replies

4. Red Hat

Storage Cluster ?

Hi I want the Sync file server together (at the moment) All server to a web server What can I do to update Joomla or WordPress files even when taken together are equal Databases together are replicated What is the solutions ? Thanks (2 Replies)
Discussion started by: mnnn
2 Replies

5. Linux

Move OS to storage disk

Hi We have RHEL 7.3 running from local disk and we want to move it to storage. I am unable to find any proper procedure to do this activity. Please help. (4 Replies)
Discussion started by: powerAIX
4 Replies
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 dynam- ically 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.10 12 Mar 2002 clinfo(1M)
All times are GMT -4. The time now is 01:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy