- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Moving Oracle to new SAN without breaking ServiceG...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 07:48 AM
тАО06-03-2010 07:48 AM
Moving Oracle to new SAN without breaking ServiceGuard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 08:09 AM
тАО06-03-2010 08:09 AM
Re: Moving Oracle to new SAN without breaking ServiceGuard
But, if you look at the definition of the cluster, you should be able to see what changes need to be made to remedy the situation, and change the package to use the new volume groups, instead of the old. Once you've looked at a working script, you can see it's a bit complicated, but straightforward.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 08:58 AM
тАО06-03-2010 08:58 AM
Re: Moving Oracle to new SAN without breaking ServiceGuard
i think its possible only if you shutdown the DB server.
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 09:32 AM
тАО06-03-2010 09:32 AM
Re: Moving Oracle to new SAN without breaking ServiceGuard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2010 01:48 PM
тАО06-03-2010 01:48 PM
Re: Moving Oracle to new SAN without breaking ServiceGuard
Of course, stopping Oracle may still be useful because it frees all the system resources (mainly I/O capacity) for the data migration.
First, find your "Managing Serviceguard" manual (also available at http://docs.hp.com High Availability section) appropriate for your Serviceguard version. Read Chapter 7 (Cluster and Package Maintenance), subchapter "Reconfiguring a cluster", sub-title "Updating the Cluster Lock configuration". If your Serviceguard version allows on-line cluster lock reconfiguration, the instructions will be there. Otherwise, there will be the instructions for off-line cluster lock reconfiguration only.
The general idea in on-line data migration is to add LUNs from the new SAN to the old VGs one by one. You do this on the node that is currently running the package.
As you don't mention VxVM, I assume you're using the default LVM.
If you have MirrorDisk installed, you can then use it to mirror each LV to the new LUN, then delete the old side of the mirror set. If you don't have MirrorDisk, you can still do an on-line migration using the pvmove command. Once an old LUN becomes completely free, you can use vgreduce to remove it from the VG.
The cluster lock LUN(s) will require special attention, but the procedures are described in the "Managing Serviceguard" manual (see above).
You must also make the failover node aware of the migration. Create a new map file for the package VG on the primary node (using "vgexport -p -s -m
Once all old LUNs are free, you can disconnect the old SAN and use "rmsf -a
We've done multiple data migrations in this way quite successfully.
MK