VMware-Forum

Hallo Leute,

ich habe folgendes Problem mit dem ghettoVCB Script, das nächtlich als Cronjob läuft. Die Backups werden auf ein NAS abgelegt. Laut den Logfiles "...due to error in VMDK backup":


2014-09-24 00:00:02 -- info: ============================== ghettoVCB LOG START ==============================

2014-09-24 00:00:02 -- info: CONFIG - VERSION = 2013_26_11_2
2014-09-24 00:00:02 -- info: CONFIG - GHETTOVCB_PID = 108334
2014-09-24 00:00:02 -- info: CONFIG - VM_BACKUP_VOLUME = /vmfs/volumes/backup1/vm-backup
2014-09-24 00:00:02 -- info: CONFIG - VM_BACKUP_ROTATION_COUNT = 1
2014-09-24 00:00:02 -- info: CONFIG - VM_BACKUP_DIR_NAMING_CONVENTION = 2014-09-24_00-00-01
2014-09-24 00:00:02 -- info: CONFIG - DISK_BACKUP_FORMAT = zeroedthick
2014-09-24 00:00:02 -- info: CONFIG - POWER_VM_DOWN_BEFORE_BACKUP = 0
2014-09-24 00:00:02 -- info: CONFIG - ENABLE_HARD_POWER_OFF = 0
2014-09-24 00:00:02 -- info: CONFIG - ITER_TO_WAIT_SHUTDOWN = 3
2014-09-24 00:00:02 -- info: CONFIG - POWER_DOWN_TIMEOUT = 5
2014-09-24 00:00:02 -- info: CONFIG - SNAPSHOT_TIMEOUT = 15
2014-09-24 00:00:02 -- info: CONFIG - LOG_LEVEL = info
2014-09-24 00:00:02 -- info: CONFIG - BACKUP_LOG_OUTPUT = /vmfs/volumes/backup1/vm-logs/ghettoVCB-2014-09-24_00-00-01-108334.log
2014-09-24 00:00:02 -- info: CONFIG - ENABLE_COMPRESSION = 0
2014-09-24 00:00:02 -- info: CONFIG - VM_SNAPSHOT_MEMORY = 0
2014-09-24 00:00:02 -- info: CONFIG - VM_SNAPSHOT_QUIESCE = 0
2014-09-24 00:00:02 -- info: CONFIG - ALLOW_VMS_WITH_SNAPSHOTS_TO_BE_BACKEDUP = 1
2014-09-24 00:00:02 -- info: CONFIG - VMDK_FILES_TO_BACKUP = all
2014-09-24 00:00:02 -- info: CONFIG - VM_SHUTDOWN_ORDER =
2014-09-24 00:00:02 -- info: CONFIG - VM_STARTUP_ORDER =
2014-09-24 00:00:02 -- info: CONFIG - RSYNC_LINK = 0
2014-09-24 00:00:02 -- info: CONFIG - EMAIL_LOG = 0
2014-09-24 00:00:02 -- info:
2014-09-24 00:00:06 -- info: Initiate backup for virtual-server NEU
2014-09-24 00:00:06 -- info: Creating Snapshot "ghettoVCB-snapshot-2014-09-24" for virtual-server NEU
2014-09-24 01:38:12 -- info: Removing snapshot from virtual-server NEU ...
2014-09-24 01:38:12 -- info: Backup Duration: 98.10 Minutes
2014-09-24 01:38:12 -- info: ERROR: Unable to backup virtual-server NEU due to error in VMDK backup!

2014-09-24 01:38:16 -- info: Initiate backup for virtual-server2 NEU
2014-09-24 01:38:16 -- info: Creating Snapshot "ghettoVCB-snapshot-2014-09-24" for virtual-server2 NEU
Destination disk format: VMFS zeroedthick
Cloning disk '/vmfs/volumes/srv02 NEU/virtual-server2/virtual-server2.vmdk'...

Clone: 0% done.
Clone: 1% done.
Clone: 2% done.
Clone: 3% done.
Clone: 4% done.DISKLIB-FLAT : Unable to reserve the space: The specified feature is not supported by this version. But the disk will be created: "/vmfs/volumes/backup1/vm-backup/virtual-server2 NEU/virtual-server2 NEU-2014-09-24_00-00-01/virtual-server2-flat.vmdk".

Clone: 5% done.
Clone: 6% done.
Clone: 7% done.
Clone: 8% done.
Clone: 9% done.
Clone: 10% done.
Clone: 11% done.
Clone: 12% done.
Clone: 13% done.
Clone: 14% done.
Clone: 15% done.
Clone: 16% done.
Clone: 17% done.
Clone: 18% done.
Clone: 19% done.
Clone: 20% done.
Clone: 21% done.
Clone: 22% done.
Clone: 23% done.
Clone: 24% done.
Clone: 25% done.
Clone: 26% done.
Clone: 27% done.
Clone: 28% done.
Clone: 29% done.
Clone: 30% done.
Clone: 31% done.
Clone: 32% done.
Clone: 33% done.
Clone: 34% done.
Clone: 35% done.
Clone: 36% done.
Clone: 37% done.
Clone: 38% done.
Clone: 39% done.
Clone: 40% done.
Clone: 41% done.
Clone: 42% done.
Clone: 43% done.
Clone: 44% done.
Clone: 45% done.
Clone: 46% done.
Clone: 47% done.
Clone: 48% done.
Clone: 49% done.
Clone: 50% done.
Clone: 51% done.
Clone: 52% done.
Clone: 53% done.
Clone: 54% done.
Clone: 55% done.
Clone: 56% done.
Clone: 57% done.
Clone: 58% done.
Clone: 59% done.
Clone: 60% done.
Clone: 61% done.
Clone: 62% done.
Clone: 63% done.
Clone: 64% done.
Clone: 65% done.
Clone: 66% done.
Clone: 67% done.
Clone: 68% done.
Clone: 69% done.
Clone: 70% done.
Clone: 71% done.
Clone: 72% done.
Clone: 73% done.
Clone: 74% done.
Clone: 75% done.
Clone: 76% done.
Clone: 77% done.
Clone: 78% done.
Clone: 79% done.
Clone: 80% done.
Clone: 81% done.
Clone: 82% done.
Clone: 83% done.
Clone: 84% done.
Clone: 85% done.
Clone: 86% done.
Clone: 87% done.
Clone: 88% done.
Clone: 89% done.
Clone: 90% done.
Clone: 91% done.
Clone: 92% done.
Clone: 93% done.
Clone: 94% done.

2014-09-24 02:34:00 -- info: Removing snapshot from virtual-server2 NEU ...
2014-09-24 02:34:00 -- info: Backup Duration: 55.73 Minutes
2014-09-24 02:34:00 -- info: Successfully completed backup for virtual-server2 NEU!

2014-09-24 02:34:03 -- info: ###### Final status: WARNING: All VMs backed up, but some disk(s) failed! ######

2014-09-24 02:34:03 -- info: ============================== ghettoVCB LOG END ================================

ghettoVCB bemüht "vmkfstools" zum Kopieren der VMDK auf das Backup-Ziel. Dessen Rückgabewert ist für die erste VM nicht Null und das Script sagt dann sinngemäß "irgendein Fehler ist aufgetreten". Genaueres kannst du also vom Script nicht erwarten.

Du müsstest den Kopiervorgang selbst in einer SSH-Shell manuell durchführen um gegebenenfalls über die Bildschirmmeldung mehr über den Fehler zu erfahren.

Im Log steht das:
Clone: 4% done.DISKLIB-FLAT : Unable to reserve the space: The specified feature is not supported by this version. But the disk will be created: "/vmfs/volumes/backup1/vm-backup/virtual-server2 NEU/virtual-server2 NEU-2014-09-24_00-00-01/virtual-server2-flat.vmdk".

Das NAS scheint Probleme mit dem zeroedthick zu haben, ich würde mal thin probieren.

leo hat geschrieben:Im Log steht das:
Clone: 4% done.DISKLIB-FLAT : Unable to reserve the space: The specified feature is not supported by this version. But the disk will be created: "/vmfs/volumes/backup1/vm-backup/virtual-server2 NEU/virtual-server2 NEU-2014-09-24_00-00-01/virtual-server2-flat.vmdk".

Das NAS scheint Probleme mit dem zeroedthick zu haben, ich würde mal thin probieren.

Ahh okay.. Die VM's laufen alle mit zeroedthick.. Kann ich diese trotzdem mit thin sichern?

Ja, das ist kein Problem, bei einem eventuellen Restore geht auch der Weg zurück von thin auf thick.

leo hat geschrieben:Ja, das ist kein Problem, bei einem eventuellen Restore geht auch der Weg zurück von thin auf thick.

Danke!! Ich werde es mal so ausprobieren