| |
|---|
| | |
|---|
| | |
|---|
| | :Author: Tim Daneliuk (tundra@tundraware.com) |
|---|
| | |
|---|
| | :Version: ``$Id: baremetal.rst,v 1.107 2014/08/23 00:37:24 tundra Exp $`` |
|---|
| | :Version: ``$Id: baremetal.rst,v 1.108 2014/08/23 00:41:03 tundra Exp $`` |
|---|
| | |
|---|
| | |
|---|
| | Précis |
|---|
| | ------ |
|---|
| |
|---|
| | application, system setting and so forth. |
|---|
| | |
|---|
| | The purpose here was to do just that - create images capable of being |
|---|
| | "poured" onto, say, a blank, new hard drive, but *using only standard |
|---|
| | linux commands and tools*. |
|---|
| | linux command line tools*. |
|---|
| | |
|---|
| | |
|---|
| | .. warning:: Doing this wrong can **clobber your systems and its |
|---|
| | data**. What you see here is just a simple example for |
|---|
| |
|---|
| | In our examples below, we're imaging a CentOS 6.5 machine. The only thing |
|---|
| | 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 |
|---|
| | could then restore any data files you have from your standard backup/restore tools. |
|---|
| | ``sda1`` - The ``/boot`` partition - about 500MB |
|---|
| | |
|---|
| | ``sda2`` - The rest of the operating system, in this case contained |
|---|
| | in LVM containers - about 52GB |
|---|
| | |
|---|
| | 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 could then restore any data files you |
|---|
| | have from your standard backup/restore tools. |
|---|
| | |
|---|
| | |
|---|
| | Backup Procedure |
|---|
| | ---------------- |
|---|
| |
|---|
| | |
|---|
| | reboot machine to make it operational again |
|---|
| | |
|---|
| | |
|---|
| | How long this takes depends on what your write speed to the shared storage is |
|---|
| | and how big your partitions are. In this case ``sda1`` is only about 100MB |
|---|
| | and completed rather quickly. But ``sda2`` was about 52GB and took around |
|---|
| | 25 min to complete on a slow nfs mount - about 26MB/min in this case or about |
|---|
| | a quarter of the capacity of the 1Ge network connecting the NAS. |
|---|
| | How long this takes depends on what your write speed to the shared |
|---|
| | storage is and how big your partitions are. In this case ``sda1`` is |
|---|
| | only about 100MB and completed rather quickly. But ``sda2`` was about |
|---|
| | 52GB and took around 25 min to complete on a slow nfs mount - about |
|---|
| | 26MB/min in this case or about a quarter of the capacity of the 1Ge |
|---|
| | network connecting the NAS. |
|---|
| | |
|---|
| | The ``bs=12`` is environment-specific and you'll have to find a setting for this |
|---|
| | that makes best use of your network and NAS or other storage device. |
|---|
| | |
|---|
| | |
|---|
| | Restore Procedure |
|---|
| | ----------------- |
|---|
| | |
|---|
| | Now, imagine that your OS is borked or the hard disk had to be replaced and you |
|---|
| | need to take the image from the backup above and getting running on the machine. |
|---|
| | Now, imagine that your OS is borked or the hard disk had to be |
|---|
| | replaced and you need to take the image from the backup above and |
|---|
| | getting running on the machine. |
|---|
| | |
|---|
| | |
|---|
| | :: |
|---|
| | |
|---|
| |
|---|
| | |
tundra
authored
on 22 Aug 2014