LFC1980
asked on
Moving HDDs from one server to the other
Hi
I want to compare the outcome to2 different situations..
(1)
You have a serverr called ABC1, which has a single HDD for system files, and 2 SCSI HDDs that comprises a 72GB mirroed volume with 65GB of read only data. Users access this by a shortcut on their PCs
ABC1 is due to be replaced. Before it's replaced a new server is built.
The new server needs to be online with the currentc data and re-estab;lish redundancy as quickly a possbile. Also need to make sure the shortcuts will stil work.
The solution says "you name the new server ABC1 (i.e. same as the old), and move both disks from the old server to the new one. Then scan the disks for changes, and then conect the new server to the network.
Situation (2)
You have a server called XYZ1, which has a simple volume that stores critical data, the server experinces hard ware failure and stops working
You have a spare server availble called XYZ2. However, it does not have enough disk to hold the data from XYZ1
It says you install the disks from XYZ1 to XYZ2 and restart, but the disks do not appear in disk managment.
The soluiton says, you should "scan for changes" and also "import foriegn disks"
My questions are. Why didn't we have to "import" in the first example. And which comes first, the import stage or the scan stage?
I want to compare the outcome to2 different situations..
(1)
You have a serverr called ABC1, which has a single HDD for system files, and 2 SCSI HDDs that comprises a 72GB mirroed volume with 65GB of read only data. Users access this by a shortcut on their PCs
ABC1 is due to be replaced. Before it's replaced a new server is built.
The new server needs to be online with the currentc data and re-estab;lish redundancy as quickly a possbile. Also need to make sure the shortcuts will stil work.
The solution says "you name the new server ABC1 (i.e. same as the old), and move both disks from the old server to the new one. Then scan the disks for changes, and then conect the new server to the network.
Situation (2)
You have a server called XYZ1, which has a simple volume that stores critical data, the server experinces hard ware failure and stops working
You have a spare server availble called XYZ2. However, it does not have enough disk to hold the data from XYZ1
It says you install the disks from XYZ1 to XYZ2 and restart, but the disks do not appear in disk managment.
The soluiton says, you should "scan for changes" and also "import foriegn disks"
My questions are. Why didn't we have to "import" in the first example. And which comes first, the import stage or the scan stage?
ASKER
But in the first case they are mirrored. I thought Mirroed volumes were dynamic
This is from a Microdoft study guide if it makes a difference
This is from a Microdoft study guide if it makes a difference
You're right, the study guide has it back to front in both cases. You don't import basic disks, you do import dynamic disks and when MS say mirrored they mean software mirroring unless they specifically say hardware.
ASKER
So in the first situation they should have imported aswell, correct?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cheers
You also need to transfer the reg key HKLM\system\CCS\services\l