- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- migrating to new disk
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
тАО07-06-2001 11:37 AM
тАО07-06-2001 11:37 AM
this started with 1 4gig disk each, the database got too big and the largest filesystem was moved to a new 4gig, again it grows and the largest filesystem is moved to a third 4gig, the first problem file grows and is extended to a 4th 4gig disk. now I arrive, I get 2 18gig disks I want to stripe these as one space and then allocate for the filesystems
first I want to move everything to the 36gig space and then stripe the 4 4gig's into 1 16gig then move some things back. PLEASE what is the most foolproof and least painfull way to do this! cpio, mirror, tape? all the mount points need to keep the orignal names i.e. /uvdata /uvdata2 /uvdata3....
this used to be the production system it is now the development/'failover' system but the production files are bigger than the filesystems. this is the reason to add lots of space. Thanks in advance. Ed
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2001 02:21 AM
тАО07-07-2001 02:21 AM
Re: migrating to new disk
I think mirroring is the best option for U.
With rgds, Shahul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2001 10:23 PM
тАО07-08-2001 10:23 PM
Re: migrating to new disk
Assuming all the 4gig disks are in one vg, if "Max PE per PV" is large enough to accommodate the 18gig disks, them mirroring may work well. Otherwise, a new vg will be required and the migration will be more involved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2001 06:37 AM
тАО07-09-2001 06:37 AM
Re: migrating to new disk
Thanks for any help you can give me.
Ed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2001 09:50 AM
тАО07-09-2001 09:50 AM
Re: migrating to new disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2001 11:25 AM
тАО07-09-2001 11:25 AM
Re: migrating to new disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2001 04:07 PM
тАО07-09-2001 04:07 PM
Re: migrating to new disk
Since the existing vgs cannot accommodate the full capacity of the 18g disks, I'd go with creating a new bootable vg with all the necessary filesystems and copy the data over with cpio. This would be a good time to determine if you want to resize any logical volumes (like swap). After successfully booting into the new vg, the previous vgs can be obliterated, the new vg renamed to vg00, the physical volumes recreated, and another new vg created to which some data can be moved. This is pretty involved, but the pay-off is a clean configuration... I'll throw together some more notes tonight while I have time...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-10-2001 10:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2001 02:54 PM
тАО07-11-2001 02:54 PM
Re: migrating to new disk
I thank you for your help and I am going over all the commands putting in my numbers and choosing sizes for the file systems.
I am changing the game plan to suit my boss,
the 2x18s will be for the data,
then 2x4s for root/sys files
1x 4 for /tmp
( our database uses var to reindex and some files are more than 1gig)
the last 4 will be held for whatever happens next.
1x 9gig will come out
1x 9gig for junk space/moving stuff/extra copies just in case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-12-2001 08:44 AM
тАО07-12-2001 08:44 AM
Re: migrating to new disk
It IS a posix shell script, but I never intended for it to be run. Even if it were complete, accurate, and started first with `set -ex` to exit on error and echo all commands and parameters as they are executed, I still wouldn't run it. I tend to document my procedures as a script because the instructions are exact and cannot be misunderstood. So if you are comfortable with the changes you've made, you can run the script and keep an eye on it while arguing with an end user on the phone about taking up 73% of /home because he or she refuses to delete anything. Since it's a posix shell script, you can (as long as you're in the posix shell) literally execute the if, while, for, until, case, etc blocks interactively.