Minor edits and commentary.

Fork: 0

tundra / baremetal

Browse code Minor edits and commentary. master
1 parent 7a2ba8f commit b04ef188c6172428bf04c82746c95be17c48571b tundra authored on 22 Aug 2014

Patch

Unified Split

Showing 1 changed file

                Ignore Space
               Show notes
              View
            
          
          18 ■■■■■
          baremetal.rst
 :Author: Tim Daneliuk (tundra@tundraware.com)
 
:Version: ``$Id: baremetal.rst,v 1.104 2014/08/22 23:39:02 tundra Exp $``
:Version: ``$Id: baremetal.rst,v 1.105 2014/08/22 23:43:04 tundra Exp $``
 
 
Précis
------
 
      http://sourceforge.net/projects/systemrescuecd/
 
You will also need access to a place to store and retrieve your images.
In the examples below, we used a NAS nfs share, though you could also
In the examples below, we used a NAS NFS share, though you could also
use another local hard drive, SAN connected storage or even a USB-connected
drive.
 
 
             image.  There are ways around this.  This document is not
             the place to find these ways.
 
 
Conclusions & Limitations
-------------------------
 
- This seems to work fine in the limited configuration that was tested.
Observations
------------
 
- Upside:
 
    1) You can use standard Linux commands to do imaged backups of
       imaging this way requires a machine outage.
 
    2) Every block in the partition gets copied whether it is used or
       not.
 
- These tests were conducted on slow, consumer grade servers connected
  via 1Ge through an unmanaged switch. In an Enterprise class
  networking and NAS environment, we'd expect to see considerably
  faster backup and reimaging times, thereby minimizing server outage
  times.
 
- In *theory* this should also work on SAN-booted machines so long as
  the exact same LUN (WWID and size) is presented for the restore as
  was used for the backup.  However, this was not tested and theory
 :Author: Tim Daneliuk (tundra@tundraware.com)
+:Version: ``$Id: baremetal.rst,v 1.104 2014/08/22 23:39:02 tundra Exp $``
+:Version: ``$Id: baremetal.rst,v 1.105 2014/08/22 23:43:04 tundra Exp $``
 Précis
 ------
       http://sourceforge.net/projects/systemrescuecd/
 You will also need access to a place to store and retrieve your images.
+In the examples below, we used a NAS nfs share, though you could also
+In the examples below, we used a NAS NFS share, though you could also
 use another local hard drive, SAN connected storage or even a USB-connected
 drive.
              image.  There are ways around this.  This document is not
              the place to find these ways.
+Conclusions & Limitations
+-------------------------
+- This seems to work fine in the limited configuration that was tested.
+Observations
+------------
 - Upside:
 ) You can use standard Linux commands to do imaged backups of
        imaging this way requires a machine outage.
 ) Every block in the partition gets copied whether it is used or
        not.
+- These tests were conducted on slow, consumer grade servers connected
+  via 1Ge through an unmanaged switch. In an Enterprise class
+  networking and NAS environment, we'd expect to see considerably
+  faster backup and reimaging times, thereby minimizing server outage
+  times.
 - In *theory* this should also work on SAN-booted machines so long as
   the exact same LUN (WWID and size) is presented for the restore as
   was used for the backup.  However, this was not tested and theory

Show line notes below