2
VMware Sicherung .tvzc in Player oder Workstation zum laufen bringen, wie?
Hallo Administratoren, haben hier ein etwas doofes problem, von nen Snapshot haben wir ne Sicherung gemacht allerdings kann ich den nicht mehr zurück auf den ESX kopieren und zum laufen bringen.
ich hab die datei sicherung.tvzc, wie bekomm ich das in ner nen VM Player oder Workstation zum laufen? im ESX Server fährt das ding nicht mehr hoch also muss ich das in dem Player zum laufen bringen. jemand ne idee?
ich hab die datei sicherung.tvzc, wie bekomm ich das in ner nen VM Player oder Workstation zum laufen? im ESX Server fährt das ding nicht mehr hoch also muss ich das in dem Player zum laufen bringen. jemand ne idee?
Auf Facebook teilen
Auf Twitter teilen
Auf Reddit teilen
Auf Linkedin teilenBitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben
Content-ID: 144932
Url: https://administrator.de/forum/vmware-sicherung-tvzc-in-player-oder-workstation-zum-laufen-bringen-wie-144932.html
Ausgedruckt am: 22.12.2024 um 11:12 Uhr
2 Kommentare
Neuester Kommentar
Hallo,
hast du schonmal gegoogelt? Wahrscheinlich nicht. Die Suche nach ".tvzc", direkt der zweite Link verweist auf die Lösung.
Details:
vRanger is unavailable to restore
Solution :
This is a how-to restore a vRanger / VCB backup by hand
Note:
These instructions assume that a backup has been taken using the vRanger product, but for whatever reason, the VM from which the backup was taken is not available to be restored. All of the actions/ commands can be executed on the target Host using Putty, except where noted to use WinSCP.
1. Locate the .tvzc files that were created when the backup was made. These files should be located either in the storage associated with the VM, or the box from which vRanger was run.
2. If the backed up VM is gone/ deleted from disk in the VIC, make sure to also delete all the .vmdk files associated with that VM from the Host. This prevents issues when registering the .tvzc files for the restore.
3. Download vcbrestore.zip from http://www.vi###core.com/Downloads/ProductSupport/vcbrestore.zip. Extract vcbrestore to the tmp directory on the Host where the restore will reside using WinSCP.
4. Run chmod 777 /tmp/ vcbrestore in the tmp directory on the Host where the restore will reside.
5. Create a directory on the VMFS volume of the Host where the restore will reside, naming the directory in accordance with the VM that is to be restored. (i.e. if the backed up VM was named ?test01?, the directory should also be named ?test01?)
6. Using WinSCP (disable Transfer Resume), move the .tvzc files from their storage location to the VMFS directory on the Host where the restore will reside.
Example:
Use WinSCP to copy test01.tvzc files from storage to the Host in the directory you created. i.e. /vmfs/volumes/storage/test01
7. List the files in the .tvzc
/tmp/vcbrestore ?D ?I ./test01.tvzc ?O /dev/stdout |tar tvf - -O
where ?test01? is the name of the tvzc file
8. Extract each file needed in the directory.
/tmp/vcbrestore ?D ?I ./test01.tvzc ?O /dev/stdout |tar xvf ? ?file names?
Note: The file names can be stringed together in one command line vs. executing individual commands for file extraction by putting a space between the various file names.
9. Rename the .vzsnp files.
This is accomplished by actually moving the files within the same directory and removing the .vzsnp extension from the files.
Example:
mv ./test01.vmdk.vzsnp ./test01.vmxf
10. Register the .vmx file to the Host
vmware-cmd ?s register <full path to the .vmx file>
Viel Erfolg damit.
Grüße
EDIT: verdammt, Chewbacca war schneller...
hast du schonmal gegoogelt? Wahrscheinlich nicht. Die Suche nach ".tvzc", direkt der zweite Link verweist auf die Lösung.
Details:
vRanger is unavailable to restore
Solution :
This is a how-to restore a vRanger / VCB backup by hand
Note:
These instructions assume that a backup has been taken using the vRanger product, but for whatever reason, the VM from which the backup was taken is not available to be restored. All of the actions/ commands can be executed on the target Host using Putty, except where noted to use WinSCP.
1. Locate the .tvzc files that were created when the backup was made. These files should be located either in the storage associated with the VM, or the box from which vRanger was run.
2. If the backed up VM is gone/ deleted from disk in the VIC, make sure to also delete all the .vmdk files associated with that VM from the Host. This prevents issues when registering the .tvzc files for the restore.
3. Download vcbrestore.zip from http://www.vi###core.com/Downloads/ProductSupport/vcbrestore.zip. Extract vcbrestore to the tmp directory on the Host where the restore will reside using WinSCP.
4. Run chmod 777 /tmp/ vcbrestore in the tmp directory on the Host where the restore will reside.
5. Create a directory on the VMFS volume of the Host where the restore will reside, naming the directory in accordance with the VM that is to be restored. (i.e. if the backed up VM was named ?test01?, the directory should also be named ?test01?)
6. Using WinSCP (disable Transfer Resume), move the .tvzc files from their storage location to the VMFS directory on the Host where the restore will reside.
Example:
Use WinSCP to copy test01.tvzc files from storage to the Host in the directory you created. i.e. /vmfs/volumes/storage/test01
7. List the files in the .tvzc
/tmp/vcbrestore ?D ?I ./test01.tvzc ?O /dev/stdout |tar tvf - -O
where ?test01? is the name of the tvzc file
8. Extract each file needed in the directory.
/tmp/vcbrestore ?D ?I ./test01.tvzc ?O /dev/stdout |tar xvf ? ?file names?
Note: The file names can be stringed together in one command line vs. executing individual commands for file extraction by putting a space between the various file names.
9. Rename the .vzsnp files.
This is accomplished by actually moving the files within the same directory and removing the .vzsnp extension from the files.
Example:
mv ./test01.vmdk.vzsnp ./test01.vmxf
10. Register the .vmx file to the Host
vmware-cmd ?s register <full path to the .vmx file>
Viel Erfolg damit.
Grüße
EDIT: verdammt, Chewbacca war schneller...
