Many edits and corrections.

Fork: 0

tundra / baremetal

Browse code Many edits and corrections. master
1 parent b04ef18 commit 1594d57e146926257fa9a2e7ababf52103d62ed2 tundra authored on 22 Aug 2014

Patch

Unified Split

Showing 1 changed file

                Ignore Space
               Show notes
              View
            
          
          61 ■■■■■
          baremetal.rst
 :Author: Tim Daneliuk (tundra@tundraware.com)
 
:Version: ``$Id: baremetal.rst,v 1.105 2014/08/22 23:43:04 tundra Exp $``
:Version: ``$Id: baremetal.rst,v 1.106 2014/08/23 00:15:14 tundra Exp $``
 
 
Précis
------
previous image onto the disk.
 
To do this, we reboot our target machine using the *Linux System Rescue CD*.
This CD has all the tools on it we need to do both image creation and
restoration.  You can find the iso image for this disk here::
restoration.  You can find the iso image for this disk here:
 
      http://sourceforge.net/projects/systemrescuecd/
 
You will also need access to a place to store and retrieve your images.
we need to image is the *operating system itself*.  In this example, we know
there are 2 partitions of interest:
 
    ``sda1`` - The ``/boot`` partition
 
    ``sda2`` - The rest of the operating system, in this case contained in LVM containers
 
The idea is that if the machine were to go dead, a disk failed, or what have you, this 
would be sufficient to get the replacement booting properly again.  Presumably, you
Backup Procedure
----------------
 
::
 
    Boot from  the System Rescue CD
 
    mount nas1:/shared /shared                     # Mount shared storage
 
need to take the image from the backup above and getting running on the machine.
 
 
::
 
    Boot from  the System Rescue CD
 
    mount nas1:/shared /shared                     # Mount shared storage
 
physical disk that is a different size than the one from which the
image was taken so long as there is 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 thenm, while still running under the ``System Rescue CD``, run
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!!!**
  work, but you have to tweak it to ensure you preserve those boot loaders
  and custom slicing tables.
 
 
Copyright And Licensing
=======================
Copyright
---------
 
This document is Copyright (c) 2014, TundraWare Inc., Des Plaines, IL
60018, All Rights Reserved.
 
 
License Terms
-------------
 
Permission is hereby granted for the free duplication and dissemination of
this document if the following conditions are met:
 
  - The document is distributed in whole and without modification,
    preserving the content in its entirety.
 
  - No fee may be charged for such distribution beyond a usual and
    ordinary fee for duplication.
 
  - You acknowledge that this document describes an EXPERIMENTAL
    PROCEDURE for learning purposes.  It has not been tested in all
    possible hardware, software, operating system, and network
    configurations.  You should not trust this approach unless you
    prove these procedures are satisfactory in YOUR OWN ENVIRONMENT.
 
  - By using this material in any way, you acknowledge you are doing
    so at your own risk.  You agree to hold TundraWare Inc.  harmless
    for any damage, direct or indirect, that this may or does cause to
    your computational environment, including, but not limited to,
    your or others' hardware, software, network, or data.  You FURTHER
    AGREE TO HOLD TUNDRAWARE INC. HARMLESS FOR ANY ECONOMIC DAMAGE OR
    ANY OTHER ADVERSE CONSEQUENCE, DIRECT OR INDIRECT, CAUSED BY THE
    USE OF THIS MATERIAL.
 
- The document is distributed in whole and without modification,
  preserving the content in its entirety.
 
- No fee may be charged for such distribution beyond a usual and
  ordinary fee for duplication.
 
- You acknowledge that this document describes an EXPERIMENTAL
  PROCEDURE for learning purposes.  It has not been tested in all
  possible hardware, software, operating system, and network
  configurations.  You should not trust this approach unless you prove
  these procedures are satisfactory in YOUR OWN ENVIRONMENT.
 
- By using this material in any way, you acknowledge you are doing so
  at your own risk.  You agree to hold TundraWare Inc.  harmless for
  any damage, direct or indirect, that this may or does cause to your
  computational environment, including, but not limited to, your or
  others' hardware, software, network, or data.  You FURTHER AGREE TO
  HOLD TUNDRAWARE INC. HARMLESS FOR ANY ECONOMIC DAMAGE OR ANY OTHER
  ADVERSE CONSEQUENCE, DIRECT OR INDIRECT, CAUSED BY THE USE OF THIS
  MATERIAL.
 
 
Document Information
====================
--------------------
 
 
You can find the latest version of this document at:
 :Author: Tim Daneliuk (tundra@tundraware.com)
+:Version: ``$Id: baremetal.rst,v 1.105 2014/08/22 23:43:04 tundra Exp $``
+:Version: ``$Id: baremetal.rst,v 1.106 2014/08/23 00:15:14 tundra Exp $``
 Précis
 ------
 previous image onto the disk.
 To do this, we reboot our target machine using the *Linux System Rescue CD*.
 This CD has all the tools on it we need to do both image creation and
+restoration.  You can find the iso image for this disk here::
+restoration.  You can find the iso image for this disk here:
       http://sourceforge.net/projects/systemrescuecd/
 You will also need access to a place to store and retrieve your images.
 we need to image is the *operating system itself*.  In this example, we know
 there are 2 partitions of interest:
     ``sda1`` - The ``/boot`` partition
     ``sda2`` - The rest of the operating system, in this case contained in LVM containers
 The idea is that if the machine were to go dead, a disk failed, or what have you, this
 would be sufficient to get the replacement booting properly again.  Presumably, you
 Backup Procedure
 ----------------
 ::
     Boot from  the System Rescue CD
     mount nas1:/shared /shared                     # Mount shared storage
 need to take the image from the backup above and getting running on the machine.
 ::
     Boot from  the System Rescue CD
     mount nas1:/shared /shared                     # Mount shared storage
 physical disk that is a different size than the one from which the
 image was taken so long as there is 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 thenm, while still running under the ``System Rescue CD``, run
+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!!!**
   work, but you have to tweak it to ensure you preserve those boot loaders
   and custom slicing tables.
+Copyright And Licensing
+=======================
+Copyright
+---------
 This document is Copyright (c) 2014, TundraWare Inc., Des Plaines, IL
 , All Rights Reserved.
+License Terms
+-------------
 Permission is hereby granted for the free duplication and dissemination of
 this document if the following conditions are met:
+  - The document is distributed in whole and without modification,
+    preserving the content in its entirety.
+  - No fee may be charged for such distribution beyond a usual and
+    ordinary fee for duplication.
+  - You acknowledge that this document describes an EXPERIMENTAL
+    PROCEDURE for learning purposes.  It has not been tested in all
+    possible hardware, software, operating system, and network
+    configurations.  You should not trust this approach unless you
+    prove these procedures are satisfactory in YOUR OWN ENVIRONMENT.
+  - By using this material in any way, you acknowledge you are doing
+    so at your own risk.  You agree to hold TundraWare Inc.  harmless
+    for any damage, direct or indirect, that this may or does cause to
+    your computational environment, including, but not limited to,
+    your or others' hardware, software, network, or data.  You FURTHER
+    AGREE TO HOLD TUNDRAWARE INC. HARMLESS FOR ANY ECONOMIC DAMAGE OR
+    ANY OTHER ADVERSE CONSEQUENCE, DIRECT OR INDIRECT, CAUSED BY THE
+    USE OF THIS MATERIAL.
+- The document is distributed in whole and without modification,
+  preserving the content in its entirety.
+- No fee may be charged for such distribution beyond a usual and
+  ordinary fee for duplication.
+- You acknowledge that this document describes an EXPERIMENTAL
+  PROCEDURE for learning purposes.  It has not been tested in all
+  possible hardware, software, operating system, and network
+  configurations.  You should not trust this approach unless you prove
+  these procedures are satisfactory in YOUR OWN ENVIRONMENT.
+- By using this material in any way, you acknowledge you are doing so
+  at your own risk.  You agree to hold TundraWare Inc.  harmless for
+  any damage, direct or indirect, that this may or does cause to your
+  computational environment, including, but not limited to, your or
+  others' hardware, software, network, or data.  You FURTHER AGREE TO
+  HOLD TUNDRAWARE INC. HARMLESS FOR ANY ECONOMIC DAMAGE OR ANY OTHER
+  ADVERSE CONSEQUENCE, DIRECT OR INDIRECT, CAUSED BY THE USE OF THIS
+  MATERIAL.
 Document Information
+====================
+--------------------
 You can find the latest version of this document at:

Show line notes below