server:
- HP ProLiant DL380G6-CD-LFF
- HP CPU X E5504 QC 2.00GHz
- 2x1TB HDs (mirrored)
- HP Smart Array P410i/256MB
Both times I tryed, it broke up after a few hours and restarted. Couldn't observe any error messages before reboot as I wasn't present at that time.
First time all partitions sda2 to sda8 seemed to be saved but the largest partition sda3 (vmfs), which contains 700GB data, only had a 'backup' size of 11GB. Something must have gone wrong, so I repeated the procedure.
Second time I disabled the DMA-option and that time it broke up during sda3 cloning.
my clonezilla version: clonezilla-live-1.2.8-42-i686
options I used (and remember):
- device-image
- local_dev
- savedisk
- disabled ntfs-check
- split to 2GB Files
- used partclone
- highest compression (first z2p, than z2)
What can I do? What goes wrong?
Should I use the AMD64 version?
BR
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"the largest partition sda3 (vmfs), which contains 700GB data, only had a 'backup' size of 11GB. Something must have gone wrong" -> Why are you so sure it went wrong?
VMFS is a special file system, and it might has a lot of blocks marked as used, but actually the data is the same, so with compression, it might be compressed to very small. At least this is why we have here, IIRC, a VMFS partition with data about 100 GB, but the image size for that partition is only about 3 GB.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
my attempts to clone an esxi server failed.
server:
- HP ProLiant DL380G6-CD-LFF
- HP CPU X E5504 QC 2.00GHz
- 2x1TB HDs (mirrored)
- HP Smart Array P410i/256MB
Both times I tryed, it broke up after a few hours and restarted. Couldn't observe any error messages before reboot as I wasn't present at that time.
First time all partitions sda2 to sda8 seemed to be saved but the largest partition sda3 (vmfs), which contains 700GB data, only had a 'backup' size of 11GB. Something must have gone wrong, so I repeated the procedure.
Second time I disabled the DMA-option and that time it broke up during sda3 cloning.
my clonezilla version: clonezilla-live-1.2.8-42-i686
options I used (and remember):
- device-image
- local_dev
- savedisk
- disabled ntfs-check
- split to 2GB Files
- used partclone
- highest compression (first z2p, than z2)
What can I do? What goes wrong?
Should I use the AMD64 version?
BR
Michael
…same with AMD64 version.
"the largest partition sda3 (vmfs), which contains 700GB data, only had a 'backup' size of 11GB. Something must have gone wrong" -> Why are you so sure it went wrong?
VMFS is a special file system, and it might has a lot of blocks marked as used, but actually the data is the same, so with compression, it might be compressed to very small. At least this is why we have here, IIRC, a VMFS partition with data about 100 GB, but the image size for that partition is only about 3 GB.
Steven.