Calirification of restoration to different sized disks.

Fork: 0

tundra / baremetal

Browse code Calirification of restoration to different sized disks. master
1 parent 1512f04 commit 4775c0c35d03c30c63142505d453b63c3dee1de9 tundra authored on 23 Aug 2014

Patch

Unified Split

Showing 1 changed file

                Ignore Space
               Show notes
              View
            
          
          42 ■■■■■
          baremetal.rst
 :Author: Tim Daneliuk (tundra@tundraware.com)
 
:Version: ``$Id: baremetal.rst,v 1.111 2014/08/23 15:31:28 tundra Exp $``
:Version: ``$Id: baremetal.rst,v 1.112 2014/08/23 15:35:10 tundra Exp $``
 
 
Précis
------
Because this is partition based - that is, you are imaging and
restoring *partitions*, not disks - you can actually restore to a
physical disk that is a different size than the one from which the
image was taken.  Obviously, there has to be enough room for all the
data on the new disk.  This makes it easy to lay your operating system
down on a new, larger disk.  Do an image of the old disk, restore it
to the new disk, and then, while still running under the ``System
Rescue CD``, run ``parted`` or ``gparted`` to expand the partitions to
use the additional disk space.
 
.. warning:: **Do NOT try this with a machine that boots from SAN!!!**
             SAN-booted machines put information into their
             bootloaders about the boot LUN's WWID and the necessary
             configuration of HBAs to see those LUNs.  If you present
             a bigger LUN with a different WWID, the OS bootstrap will
             probably fail, even though you can properly restore the
             image.  There are ways around this.  This document is not
             the place to find these ways.
data on the new disk. You can even restore to a *smaller* disk overall,
so long as your full partitions will fit on it.  This might be the
case if, say, you original installation's partitions did not use
all of the disk's space.
 
More commonly, thought, this makes it easy to lay your operating
system down on a new, larger disk.  Do an image of the old disk,
restore it to the new disk, and then, while still running under the
``System Rescue CD``, run ``parted`` or ``gparted`` to expand the
partitions to use the additional disk space.
 
.. warning:: **Do NOT try restoring to anything other than the original
             disk with a machine that boots from SAN!!!** SAN-booted
             machines put information into their bootloaders about the
             boot LUN's WWID and the necessary configuration of HBAs
             to see those LUNs.  If you present a bigger LUN with a
             different WWID, the OS bootstrap will probably fail, even
             though you can properly restore the image.  There are
             ways around this.  This document is not the place to find
             these ways.
 
 
Observations
------------
 :Author: Tim Daneliuk (tundra@tundraware.com)
+:Version: ``$Id: baremetal.rst,v 1.111 2014/08/23 15:31:28 tundra Exp $``
+:Version: ``$Id: baremetal.rst,v 1.112 2014/08/23 15:35:10 tundra Exp $``
 Précis
 ------
 Because this is partition based - that is, you are imaging and
 restoring *partitions*, not disks - you can actually restore to a
 physical disk that is a different size than the one from which the
 image was taken.  Obviously, there has to be enough room for all the
+data on the new disk.  This makes it easy to lay your operating system
+down on a new, larger disk.  Do an image of the old disk, restore it
+to the new disk, and then, while still running under the ``System
+Rescue CD``, run ``parted`` or ``gparted`` to expand the partitions to
+use the additional disk space.
+.. warning:: **Do NOT try this with a machine that boots from SAN!!!**
+             SAN-booted machines put information into their
+             bootloaders about the boot LUN's WWID and the necessary
+             configuration of HBAs to see those LUNs.  If you present
+             a bigger LUN with a different WWID, the OS bootstrap will
+             probably fail, even though you can properly restore the
+             image.  There are ways around this.  This document is not
+             the place to find these ways.
+data on the new disk. You can even restore to a *smaller* disk overall,
+so long as your full partitions will fit on it.  This might be the
+case if, say, you original installation's partitions did not use
+all of the disk's space.
+More commonly, thought, this makes it easy to lay your operating
+system down on a new, larger disk.  Do an image of the old disk,
+restore it to the new disk, and then, while still running under the
+``System Rescue CD``, run ``parted`` or ``gparted`` to expand the
+partitions to use the additional disk space.
+.. warning:: **Do NOT try restoring to anything other than the original
+             disk with a machine that boots from SAN!!!** SAN-booted
+             machines put information into their bootloaders about the
+             boot LUN's WWID and the necessary configuration of HBAs
+             to see those LUNs.  If you present a bigger LUN with a
+             different WWID, the OS bootstrap will probably fail, even
+             though you can properly restore the image.  There are
+             ways around this.  This document is not the place to find
+             these ways.
 Observations
 ------------

Show line notes below