|
|
Sponsored Content
Operating Systems
AIX
Cluster 6.1 storage move
Post 302949225 by agent.kgb on Wednesday 8th of July 2015 09:30:11 AM
07-08-2015
find another architects! these I would personally pillory 
after the procedure you will receive new LUNs with the same PVIDs on the AIX. The best way in this case is to shutdown the cluster, remove volume groups from the cluster resource groups, export all volume groups to be synced, remove all disks which are in these volume groups from the system, de-zone the LUNs, let them (these funny guys which think they are architects) synchronize the storage, zone new LUNs to the server, configure them (cfgmgr and disk parameters if you need them), import volume groups, rediscover everthing on both sides of the cluster, update the cluster resource group definitions, start the cluster.
I hope, I didn't forget something very important, but from my point of view it is easier to kill the architects and save online time for your users. Implement the solution of bakunin - it is the right one! The only right solution.
after the procedure you will receive new LUNs with the same PVIDs on the AIX. The best way in this case is to shutdown the cluster, remove volume groups from the cluster resource groups, export all volume groups to be synced, remove all disks which are in these volume groups from the system, de-zone the LUNs, let them (these funny guys which think they are architects) synchronize the storage, zone new LUNs to the server, configure them (cfgmgr and disk parameters if you need them), import volume groups, rediscover everthing on both sides of the cluster, update the cluster resource group definitions, start the cluster. I hope, I didn't forget something very important, but from my point of view it is easier to kill the architects and save online time for your users. Implement the solution of bakunin - it is the right one! The only right solution.
This User Gave Thanks to agent.kgb For This Post:
|
|
5 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
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
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
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
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
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
LEARN ABOUT HPUX
vgremove
vgremove(1M) vgremove(1M) NAME
vgremove - remove LVM volume group definition from the system SYNOPSIS
vg_name ... Remarks If a combination of volume groups version 1.0 and 2.0 or higher arguments are supplied, then the arguments might not be processed in the order they are listed on the command line. DESCRIPTION
The command removes from the system the last physical volume of the volume group and the definition of the volume group or groups specified by vg_name .... Since all system knowledge of the volume group and its contents are removed, the volume group can no longer be accessed. To move a volume group from one system to another, use the command instead (see vgexport(1M)). Before executing remove all logical volumes residing on the last physical volume by executing (see lvremove(1M)). Before removing a volume group, two steps are necessary: 1. Remove all the logical volumes belonging to the group by using the command (see lvremove(1M)). 2. Remove all but one physical volume belonging to the volume group by using the command (see vgreduce(1M)). If there is any physical volume group created under vg_name ..., the physical volume group information is also removed from file Options and Arguments recognizes the following option and argument: For each volume group removed, also remove its volume group directory and file vg_name The path name of a volume group. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Remove volume group from the system: SEE ALSO
lvremove(1M), vgchange(1M), vgreduce(1M). vgremove(1M)