Moving System From One Drive Type To Another

I have Server 2008 with Hyper-V installed on a WD5000KS drive. I would like to move it to a
WD5000AAKS drive on the same machine. Both drives hold 500GB but the heads, cynders and sectors are
not the same. Is there a relatively safe way to move the operating system?

 

Yes, you've got several options.

1. Hardware mirror (Raid 1).
If your system supports hardware mirroring, just add the second disk as a
mirror to your original disk and allow it to synchronize. Then simply break
the mirror, remove the original disk and continue working with the new one.

2. Software mirror. This is the one I dislike the most, but have used
successfully in the past.
The same procedure as above, however, your disk will no longer be "basic",
but "dynamic". No big deal, but worth to know that it will break multi boot
and some service partitions if they exist.

3. Disk imaging. You can use Microsoft's ImageX, or third party solutions.

4. Backup restore solution. Either Microsoft's or third party solutions.

The choice is yours. Options 1 and 2 give you minimum down time. Options 3
and 4 have incresed downtime.

"Stewart Berman" <saberman@nospam.nospam> wrote in message
news:qfpfu4pjgdh02173n6moi5n9h3btc24b26@4ax.com...
>I have Server 2008 with Hyper-V installed on a WD5000KS drive. I would
>like to move it to a
> WD5000AAKS drive on the same machine. Both drives hold 500GB but the
> heads, cynders and sectors are
> not the same. Is there a relatively safe way to move the operating
> system?

 

On 04/17/09 02:29, Dusko Savatovic wrote:
> 1. Hardware mirror (Raid 1).
> If your system supports hardware mirroring, just add the second disk as
> a mirror to your original disk and allow it to synchronize. Then simply
> break the mirror, remove the original disk and continue working with the
> new one.

Be careful doing this as depending on what RAID controller you use you
may not be able to do it. Some RAID controllers translate and or other
wise change the geometry of the drive to support the RAID (by adding a
header and / or footer).

> 2. Software mirror. This is the one I dislike the most, but have used
> successfully in the past.
> The same procedure as above, however, your disk will no longer be
> "basic", but "dynamic". No big deal, but worth to know that it will
> break multi boot and some service partitions if they exist.

This is probably the easiest way to do it, but does have the
disadvantage of the dynamic disk.

> 3. Disk imaging. You can use Microsoft's ImageX, or third party solutions.

This (via Acronis TrueImage) would be my preferred method.

> 4. Backup restore solution. Either Microsoft's or third party solutions.

Depending on what type of backup / restore technology you use (disk
image (ala #3 above) or tape or something else) this could be the most
labor intensive method. If you use tape with out bare metal support,
there is a good chance that you will be installing a skeleton OS and
then restoring the tape over top of it.

> The choice is yours. Options 1 and 2 give you minimum down time. Options
> 3 and 4 have incresed downtime.

Option 2 will probably allow you to continue using the server even while
it is mirroring the drive, all be it with some speed degradation.

Option 3 is probably the most flexible, including working with different
(smaller) sized drives.

Options 1 and 4 have other complications that IMHO make them non
options. Though option 4 would probably be a good exercise to test your
backups.



Grant. . . .

 

"Dusko Savatovic" <nospam.savatovic@gmail.com> wrote:

>Yes, you've got several options.
>
>1. Hardware mirror (Raid 1).
>If your system supports hardware mirroring, just add the second disk as a
>mirror to your original disk and allow it to synchronize. Then simply break
>the mirror, remove the original disk and continue working with the new one.
>

It has hardware mirror but it won't do it with a different disk type.

>2. Software mirror. This is the one I dislike the most, but have used
>successfully in the past.
>The same procedure as above, however, your disk will no longer be "basic",
>but "dynamic". No big deal, but worth to know that it will break multi boot
>and some service partitions if they exist.
>

Does this mean the original source disk will also be changed? I am not crazy about doing that.

If only the mirror drive will be dynamic I would give it a try as there is only one primary
partition on the drive.

>3. Disk imaging. You can use Microsoft's ImageX, or third party solutions.
>

This looks like the best option -- assuming the disk imaging with translate the absolute head,
cylinder, track addresses in the MBR.

>4. Backup restore solution. Either Microsoft's or third party solutions.
>

One test of that is enough for a lifetime.

>The choice is yours. Options 1 and 2 give you minimum down time. Options 3
>and 4 have incresed downtime.
>
>"Stewart Berman" <saberman@nospam.nospam> wrote in message
>news:qfpfu4pjgdh02173n6moi5n9h3btc24b26@4ax.com...
>>I have Server 2008 with Hyper-V installed on a WD5000KS drive. I would
>>like to move it to a
>> WD5000AAKS drive on the same machine. Both drives hold 500GB but the
>> heads, cynders and sectors are
>> not the same. Is there a relatively safe way to move the operating
>> system?

 

I think I will try (3) first. The Server is a test bed and can be down for a day if necessary.

Grant Taylor <gtaylor@riverviewtech.net> wrote:

>On 04/17/09 02:29, Dusko Savatovic wrote:
>> 1. Hardware mirror (Raid 1).
>> If your system supports hardware mirroring, just add the second disk as
>> a mirror to your original disk and allow it to synchronize. Then simply
>> break the mirror, remove the original disk and continue working with the
>> new one.
>
>Be careful doing this as depending on what RAID controller you use you
>may not be able to do it. Some RAID controllers translate and or other
>wise change the geometry of the drive to support the RAID (by adding a
>header and / or footer).
>
>> 2. Software mirror. This is the one I dislike the most, but have used
>> successfully in the past.
>> The same procedure as above, however, your disk will no longer be
>> "basic", but "dynamic". No big deal, but worth to know that it will
>> break multi boot and some service partitions if they exist.
>
>This is probably the easiest way to do it, but does have the
>disadvantage of the dynamic disk.
>
>> 3. Disk imaging. You can use Microsoft's ImageX, or third party solutions.
>
>This (via Acronis TrueImage) would be my preferred method.
>
>> 4. Backup restore solution. Either Microsoft's or third party solutions.
>
>Depending on what type of backup / restore technology you use (disk
>image (ala #3 above) or tape or something else) this could be the most
>labor intensive method. If you use tape with out bare metal support,
>there is a good chance that you will be installing a skeleton OS and
>then restoring the tape over top of it.
>
>> The choice is yours. Options 1 and 2 give you minimum down time. Options
>> 3 and 4 have incresed downtime.
>
>Option 2 will probably allow you to continue using the server even while
>it is mirroring the drive, all be it with some speed degradation.
>
>Option 3 is probably the most flexible, including working with different
>(smaller) sized drives.
>
>Options 1 and 4 have other complications that IMHO make them non
>options. Though option 4 would probably be a good exercise to test your
>backups.
>
>
>
>Grant. . . .

 

I went with Windows Automatic Installation Kit and ImageX.

I have a 5 1/4 exposed slot that lets me plug in SATA drives. Put one and booted the PE CD.

Created the image of the C: drive.

Used Diskpart to partition, format and assign a drive letter to the target drive.

Applied the image. Made the partition active

Restarted and changed the boot order to go to the target drive.

Booted fine. Then checked Disk Management and discovered that the new target drive was mounted as
E: and the original drive was still C: with the paging file, etc. on it.

Unfortunately, the bios on the machine will not let me disable a SATA drive. So I will have to open
it up and disconnect the internal drives and try booting again. Once I am sure the new target drive
will mount as C: and work I'll swap it for the internal drive.

Stewart Berman <saberman@nospam.nospam> wrote:

>"Dusko Savatovic" <nospam.savatovic@gmail.com> wrote:
>
>>Yes, you've got several options.
>>
>>1. Hardware mirror (Raid 1).
>>If your system supports hardware mirroring, just add the second disk as a
>>mirror to your original disk and allow it to synchronize. Then simply break
>>the mirror, remove the original disk and continue working with the new one.
>>
>
>It has hardware mirror but it won't do it with a different disk type.
>
>>2. Software mirror. This is the one I dislike the most, but have used
>>successfully in the past.
>>The same procedure as above, however, your disk will no longer be "basic",
>>but "dynamic". No big deal, but worth to know that it will break multi boot
>>and some service partitions if they exist.
>>
>
>Does this mean the original source disk will also be changed? I am not crazy about doing that.
>
>If only the mirror drive will be dynamic I would give it a try as there is only one primary
>partition on the drive.
>
>>3. Disk imaging. You can use Microsoft's ImageX, or third party solutions.
>>
>
>This looks like the best option -- assuming the disk imaging with translate the absolute head,
>cylinder, track addresses in the MBR.
>
>>4. Backup restore solution. Either Microsoft's or third party solutions.
>>
>
>One test of that is enough for a lifetime.
>
>>The choice is yours. Options 1 and 2 give you minimum down time. Options 3
>>and 4 have incresed downtime.
>>
>>"Stewart Berman" <saberman@nospam.nospam> wrote in message
>>news:qfpfu4pjgdh02173n6moi5n9h3btc24b26@4ax.com...
>>>I have Server 2008 with Hyper-V installed on a WD5000KS drive. I would
>>>like to move it to a
>>> WD5000AAKS drive on the same machine. Both drives hold 500GB but the
>>> heads, cynders and sectors are
>>> not the same. Is there a relatively safe way to move the operating
>>> system?

 

Cleaned the traget drive and reran ImageX /Apply.

Hit a problem booting with a winload.exe missing or corrupt message.

Booted installation DVD and ran bootrec /rebuildbcd.

All is well now or at least appears to be.

Stewart Berman <saberman@nospam.nospam> wrote:

>I went with Windows Automatic Installation Kit and ImageX.
>
>I have a 5 1/4 exposed slot that lets me plug in SATA drives. Put one and booted the PE CD.
>
>Created the image of the C: drive.
>
>Used Diskpart to partition, format and assign a drive letter to the target drive.
>
>Applied the image. Made the partition active
>
>Restarted and changed the boot order to go to the target drive.
>
>Booted fine. Then checked Disk Management and discovered that the new target drive was mounted as
>E: and the original drive was still C: with the paging file, etc. on it.
>
>Unfortunately, the bios on the machine will not let me disable a SATA drive. So I will have to open
>it up and disconnect the internal drives and try booting again. Once I am sure the new target drive
>will mount as C: and work I'll swap it for the internal drive.
>
>Stewart Berman <saberman@nospam.nospam> wrote:
>
>>"Dusko Savatovic" <nospam.savatovic@gmail.com> wrote:
>>
>>>Yes, you've got several options.
>>>
>>>1. Hardware mirror (Raid 1).
>>>If your system supports hardware mirroring, just add the second disk as a
>>>mirror to your original disk and allow it to synchronize. Then simply break
>>>the mirror, remove the original disk and continue working with the new one.
>>>
>>
>>It has hardware mirror but it won't do it with a different disk type.
>>
>>>2. Software mirror. This is the one I dislike the most, but have used
>>>successfully in the past.
>>>The same procedure as above, however, your disk will no longer be "basic",
>>>but "dynamic". No big deal, but worth to know that it will break multi boot
>>>and some service partitions if they exist.
>>>
>>
>>Does this mean the original source disk will also be changed? I am not crazy about doing that.
>>
>>If only the mirror drive will be dynamic I would give it a try as there is only one primary
>>partition on the drive.
>>
>>>3. Disk imaging. You can use Microsoft's ImageX, or third party solutions.
>>>
>>
>>This looks like the best option -- assuming the disk imaging with translate the absolute head,
>>cylinder, track addresses in the MBR.
>>
>>>4. Backup restore solution. Either Microsoft's or third party solutions.
>>>
>>
>>One test of that is enough for a lifetime.
>>
>>>The choice is yours. Options 1 and 2 give you minimum down time. Options 3
>>>and 4 have incresed downtime.
>>>
>>>"Stewart Berman" <saberman@nospam.nospam> wrote in message
>>>news:qfpfu4pjgdh02173n6moi5n9h3btc24b26@4ax.com...
>>>>I have Server 2008 with Hyper-V installed on a WD5000KS drive. I would
>>>>like to move it to a
>>>> WD5000AAKS drive on the same machine. Both drives hold 500GB but the
>>>> heads, cynders and sectors are
>>>> not the same. Is there a relatively safe way to move the operating
>>>> system?

 

I thought all was well -- unfortunately the Hypervisor did not.

I finally used Server backup and full pc restore to transfer the system.

Stewart Berman <saberman@nospam.nospam> wrote:

>Cleaned the traget drive and reran ImageX /Apply.
>
>Hit a problem booting with a winload.exe missing or corrupt message.
>
>Booted installation DVD and ran bootrec /rebuildbcd.
>
>All is well now or at least appears to be.
>
>Stewart Berman <saberman@nospam.nospam> wrote:
>
>>I went with Windows Automatic Installation Kit and ImageX.
>>
>>I have a 5 1/4 exposed slot that lets me plug in SATA drives. Put one and booted the PE CD.
>>
>>Created the image of the C: drive.
>>
>>Used Diskpart to partition, format and assign a drive letter to the target drive.
>>
>>Applied the image. Made the partition active
>>
>>Restarted and changed the boot order to go to the target drive.
>>
>>Booted fine. Then checked Disk Management and discovered that the new target drive was mounted as
>>E: and the original drive was still C: with the paging file, etc. on it.
>>
>>Unfortunately, the bios on the machine will not let me disable a SATA drive. So I will have to open
>>it up and disconnect the internal drives and try booting again. Once I am sure the new target drive
>>will mount as C: and work I'll swap it for the internal drive.
>>
>>Stewart Berman <saberman@nospam.nospam> wrote:
>>
>>>"Dusko Savatovic" <nospam.savatovic@gmail.com> wrote:
>>>
>>>>Yes, you've got several options.
>>>>
>>>>1. Hardware mirror (Raid 1).
>>>>If your system supports hardware mirroring, just add the second disk as a
>>>>mirror to your original disk and allow it to synchronize. Then simply break
>>>>the mirror, remove the original disk and continue working with the new one.
>>>>
>>>
>>>It has hardware mirror but it won't do it with a different disk type.
>>>
>>>>2. Software mirror. This is the one I dislike the most, but have used
>>>>successfully in the past.
>>>>The same procedure as above, however, your disk will no longer be "basic",
>>>>but "dynamic". No big deal, but worth to know that it will break multi boot
>>>>and some service partitions if they exist.
>>>>
>>>
>>>Does this mean the original source disk will also be changed? I am not crazy about doing that.
>>>
>>>If only the mirror drive will be dynamic I would give it a try as there is only one primary
>>>partition on the drive.
>>>
>>>>3. Disk imaging. You can use Microsoft's ImageX, or third party solutions.
>>>>
>>>
>>>This looks like the best option -- assuming the disk imaging with translate the absolute head,
>>>cylinder, track addresses in the MBR.
>>>
>>>>4. Backup restore solution. Either Microsoft's or third party solutions.
>>>>
>>>
>>>One test of that is enough for a lifetime.
>>>
>>>>The choice is yours. Options 1 and 2 give you minimum down time. Options 3
>>>>and 4 have incresed downtime.
>>>>
>>>>"Stewart Berman" <saberman@nospam.nospam> wrote in message
>>>>news:qfpfu4pjgdh02173n6moi5n9h3btc24b26@4ax.com...
>>>>>I have Server 2008 with Hyper-V installed on a WD5000KS drive. I would
>>>>>like to move it to a
>>>>> WD5000AAKS drive on the same machine. Both drives hold 500GB but the
>>>>> heads, cynders and sectors are
>>>>> not the same. Is there a relatively safe way to move the operating
>>>>> system?