| |
|---|
| | |
|---|
| | |
|---|
| | :Author: Tim Daneliuk (tundra@tundraware.com) |
|---|
| | |
|---|
| | :Version: ``$Id: baremetal.rst,v 1.110 2014/08/23 00:50:14 tundra Exp $`` |
|---|
| | :Version: ``$Id: baremetal.rst,v 1.111 2014/08/23 15:31:28 tundra Exp $`` |
|---|
| | |
|---|
| | |
|---|
| | Précis |
|---|
| | ------ |
|---|
| |
|---|
| | On the same network described above, restoring the 52MB ``rootvg`` |
|---|
| | took about 35 mins. |
|---|
| | |
|---|
| | Because this is partition based - that is, you are imaging and |
|---|
| | restoring *partitions* not disks - you can actually restore to a |
|---|
| | 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 |
|---|
| |
|---|
| | |
tundra
authored
on 23 Aug 2014