Alternate method to move /Storage to a new disk
| Article: TECH135356 | | | Created: 2010-01-07 | | | Updated: 2011-12-30 | | | Article URL http://www.symantec.com/docs/TECH135356 |
Problem
Alternate method to move /Storage to a new disk when FSsync fails
Solution
For customers attempting to relocate /Storage to a new disk there is the FSsync script. Please see the following SymWISE document: TECH64302
If however the script fails or there are problems with it's use then this is an alternate method to complete the process safely.
Here are the steps to try. This assumes the new storage is mounted at /Storage_new.
--------------------------------------------------------
1) Shutdown PureDisk:
If however the script fails or there are problems with it's use then this is an alternate method to complete the process safely.
Here are the steps to try. This assumes the new storage is mounted at /Storage_new.
--------------------------------------------------------
1) Shutdown PureDisk:
# service puredisk stop
# service syslog stop
# service syslog stop
2) Use the following command to start copying the data directory. This can be used while the system is running, however depending upon the environment it could impact performance some:
# screen -L rsync -aux --delete --progress /Storage/data/ /Storage_new/data/
- press ctrl-A followed by ctrl-D (to detach from the screen)
To follow the output of the command:
- # tail -f screenlog.0 (to follow the output of the command)
To reattach to the screen session:
- # screen -r
- press ctrl-A followed by ctrl-D (to detach from the screen)
3) We can verify if anything is still accessing /Storage with this command:
# lsof /Storage
4) Once we've verified that nothing is writing to it we will run another rsync on the /Storage partition. This will catch any changes to any of the files written and update them on the /Storage_new partition:
# screen -L rsync -aux --delete --progress /Storage/ /Storage_new/
5) This is optional, but is a good idea if you have the time. You can verify that the data in /Storage_new matches the data in /Storage:
# diff -r /Storage /Storage_new
6) At this point you can unmount /Storage and /Storage_new and mount the new storage to /Storage. Restart the PureDisk services with these command:
# service puredisk start
# service syslog start
# screen -L rsync -aux --delete --progress /Storage/data/ /Storage_new/data/
- press ctrl-A followed by ctrl-D (to detach from the screen)
To follow the output of the command:
- # tail -f screenlog.0 (to follow the output of the command)
To reattach to the screen session:
- # screen -r
- press ctrl-A followed by ctrl-D (to detach from the screen)
3) We can verify if anything is still accessing /Storage with this command:
# lsof /Storage
4) Once we've verified that nothing is writing to it we will run another rsync on the /Storage partition. This will catch any changes to any of the files written and update them on the /Storage_new partition:
# screen -L rsync -aux --delete --progress /Storage/ /Storage_new/
5) This is optional, but is a good idea if you have the time. You can verify that the data in /Storage_new matches the data in /Storage:
# diff -r /Storage /Storage_new
6) At this point you can unmount /Storage and /Storage_new and mount the new storage to /Storage. Restart the PureDisk services with these command:
# service puredisk start
# service syslog start
|
|
Legacy ID
357292
Article URL http://www.symantec.com/docs/TECH135356
Terms of use for this information are found in Legal Notices
Thank you.