Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrading a Data drive in 6.5

Status
Not open for further replies.

Pauzotah

Technical User
Jun 17, 2006
36
GB
Hi all,

I will soon be upgrading a data drive on my 6.5 server.

I have scanned the web and have come to the opinion that i need to dismount the current drive and then mount the new one in its place and then copy all the data onto the new drive. I will be retaining the old drives name and data directory structure.

What i am concerned about is file rights. By dismounting and mounting a new drive will i have to restore from backup the file rights or will the dismounting process preserve the file rights of users for their areas.

I have a good backup of all data and our tree so restoring isnt an issue but i want to make completely sure there is no easier way of doing this.

Thanks in advance
 
I don't know the answer to your question, but if you're concerned about maintaining file rights take a look at trustbar.nlm. It backs up all rights in a volume to an xml file and restores them quickly. Very painless.
 
Hi,

why did you not just set up a "mirror" between the old Disk and the new one ?

I expect, the new one will be bigger then the old one, or ?
After the sync is finsihed, break the mirror and extend the pool with the rest of the partition.

Cheers
Andreas

Cheers Novelli
Novell Master CNE + CDE
 
OK, i have the newer bigger drive in place. It is synced with the older smaller drive. I have looked everywhere for info on breaking a mirror or at least removing a drive from a mirror but found very little.

Some advice says to use NSSMU while other parts say iManager or NRM.

I tried to break the mirror earlier by downing the Server then removing the older drive, but all that did was decrease the mirrored state slowly.

Any advice on a safe break using NW6.5 SP3 ?
 
Hi,

shutdown Server, remove the "old" Disk, be sure that the boot partition (if on this disk) is also on the new one.
Stafrt server and use nssmu (command line tool) to remove old partition from mirror set

Cheers
Andreas

Cheers Novelli
Novell Master CNE + CDE
 
OK thanks.

I was thinking a while ago about another solution.

What if i copied the data from the old data drive to a temp drive, then downed the Server replaced the old with the new and then powered and named the new drive the same as the old. Copy the data back to the new drive and then click on the create and edirectory connection in NRM. Would this work and also re enable all the drive mapping of the users using the data drive ?
 
There are lots of ways you could do this. From your workstation, you could copy all the server data to a bunch of floppies. Make sure you number them correctly. Then replace the drive and restore them one by one. You could also hook up a laptop and copy everything to its drive. Then you could run home, copy it to your pc as a backup. Then you could build a brand new server and recreate all user accounts and other NDS objects. Once you're done there, you could copy the data back from your laptop and then restore all the trustee assignments and login scripts. If you really wanted to get creative, you could hire a pack of mules to come and pack up your data, haul it to Florida where they will load it onto a Cruise ship for offshore storage protection. Then when you are finished replacing the drives, just call in the mules again and they'll call the ship, get your data and then haul your data back to your location for you. Those mules are hard workers. If you give them a carrot, they'll even recreate your eDirectory tree for you. Except they don't speak english so some of your schema extensions might need to be fixed manually.

This is another way of saying that No, your alternate solution is not a practical way of doing things. Go with what was already recommended and save yourself a lot of time. You're just going to shoot yourself in the foot if you try to do it the way you are mentioning. You'll lose your tree and all your permissions, login scripts, users, printers, etc. not worth it.

Marvin
 
Thanks all for your help......and Marvin, i think i get the idea, sorry to have obviously hit a nerve. I have always looked at other possible solutions before making my final decision.

It sometimes helps...honest !
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top