©XSIBackup-Free: Free Backup Software for ©VMWare ©ESXi

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


Forum menu Menu

You are not logged in.

Pages: 1

#1 Re: General matters » Backup VM with snapshots: unable to delete snapshots (solved) » 2019-10-21 14:47:36

bullet_flame

Disks are OK, it's not the reason.

I upgraded Xsibackup-DC to version 1.0.0.2 and it restored VM with snapshots without any issues.

So I suppose it was a bug of version 1.0.0.1 used by me previously.

PS:
When I deleted all the snapshots and recovered VM from backup - I was needed to remove VM from inventory and register again to see all the snapshots.
Also it's possible to reload vmx file without unregister/register action:

vim-cmd vmsvc/reload Vmid

Maybe it's will be good to add automatic reload of vmx file configuration after restore.
And also to add key to delete all existing snapshots before backup.

#2 Re: General matters » Backup VM with snapshots: unable to delete snapshots (solved) » 2019-10-15 13:37:37

bullet_flame

It seems I found workaround:

I tried to make disk consolidation and got the same error :

Consolidate VMDisks	VM-Deb-x64-02
root	10/15/2019 16:26:22	10/15/2019 16:26:22	Failed - Unable to access file since it is locked

The same error when tried to revert snapshot:

 Revert To Snapshot	VM-Deb-x64-02
root	10/15/2019 16:27:15	10/15/2019 16:27:15	Failed - Unable to access file since it is locked

After that tried to consolidate disks again and it was successful :

 Consolidate VMDisks	
VM-Deb-x64-02
root	10/15/2019 16:27:28	10/15/2019 16:27:28	Completed successfully

So twice consolidation helped in my case.
All operations with the snapshots became successful.

#3 Re: General matters » Backup VM with snapshots: unable to delete snapshots (solved) » 2019-10-15 09:16:31

bullet_flame

Thanks a lot for feedback !

So I deployed another VM from scratch and no issues during backup process were detected.
Possibly it was something wrong with my first VM.

After that I deleted all the existing snapshots and tried to restore.
When restoration finished I checked that snapshots don't appeared and tried to re-register VM.
After re-registration 2 snapshots made by me became in place and additional temporary xsi snapshot.
This xsi snapshot can't be deleted.

I checked that no lock files are presented inside VM folder.

#4 General matters » Backup VM with snapshots: unable to delete snapshots (solved) » 2019-10-14 13:46:32

bullet_flame
Replies: 8

Hello !

Currently I'm testing trial version of xsi-dc and discovered very strange issue in case of VM with snapshots.

During backup procedure xsi-dc reported that it's impossible to delete temporary snapshot with name like xsi7834010995546.
Also it's impossible to delete manually the single snapshot afterwards or all snapshots.

Failed - A general system error occurred: vim.fault.GenericVmConfigFault

And it's impossible to delete this VM:

Failed - Unable to access file since it is locked

Announced feature All pre-existing snapshots are preserved doesn't work.

Of course it's great solution, but some features need to be fixed. Or maybe I'm doing something wrong.

#5 Re: General matters » Error of getting VM files location hosted on ESXi 6.5 AMD CPU » 2019-02-19 13:40:25

bullet_flame

No worries ! I checked how it works with new ESXi 6.5 deployment on the same hardware.
With datastore created by default with vmfs5 everything is OK.
With datastore formatted to vmfs6 the same errors were happened.

ls: /vmfs/volumes/DataStore2/*.vmx: No such file or directory
cat: can't open '': No such file or directory

My mention that this issue happened by the reason of partial compatibility between old HP ProLiant BL465c G6 and ESXi 6.5 .
Officially it's not supported by ESXi 6.5 .

#6 Re: General matters » Error of getting VM files location hosted on ESXi 6.5 AMD CPU » 2019-02-18 11:07:53

bullet_flame

Thanks, it seems that problem like this Cannot create VMFS datastore
I received the same error during datastore creation.

#7 Re: General matters » Error of getting VM files location hosted on ESXi 6.5 AMD CPU » 2019-02-18 09:47:39

bullet_flame

Today I tried recreate datastore from vmfs6 to vmfs5. Now it works without any errors.

#8 General matters » Error of getting VM files location hosted on ESXi 6.5 AMD CPU » 2019-02-17 16:00:01

bullet_flame
Replies: 5

Hello !

I deployed xsibackup free on ESXi 6.5 build 10884925 with Intel CPU (HP G7). It worked absolutely correctly.

But for further testing I deployed 2 ESXi 6.5 servers and updated it to latest build 11925212 (AMD CPU  Opteron 2435 - HP Blade G6).
By unknown reason xsibackup tried to search files of VM in root folder of datastore instead VM's folder.

After that during single backup command I got this:
./xsibackup --backup-point=/vmfs/volumes/DataStore1/backup --backup-type=custom --backup-vms="vmdeb02"

VMs to backup:
----------------------------------------------------------------------------------------------------------
5      vmdeb02    [DataStore2] vmdeb02/vmdeb02.vmx     debian9_64Guest    vmx-13                                                                                                           
----------------------------------------------------------------------------------------------------------
Needed room: 3 Gb.
Sparse size: 50 Gb.
Available room: 127 Gb.
----------------------------------------------------------------------------------------------------------
[vmdeb02] Starting backup (size is 3861M on 51200M file)
----------------------------------------------------------------------------------------------------------
XSIBackup will backup your VMs while they are running and will quiesce guest services too, so that users
can continue to use the VM while the backup is taking place. You can also run cold and warm --backup-how
----------------------------------------------------------------------------------------------------------
Hot backup selected for VM: [vmdeb02], the VM is off though
----------------------------------------------------------------------------------------------------------
ls: /vmfs/volumes/DataStore2/*.vmx: No such file or directory
cat: can't open '': No such file or directory
[vmdeb02] info: boot partition is MBR
----------------------------------------------------------------------------------------------------------
Removing snapshots, please wait...
----------------------------------------------------------------------------------------------------------
Syncronizing config files
----------------------------------------------------------------------------------------------------------
No .vmx config file found for vmdeb02 (5)
cat: can't open 'ls: /vmfs/volumes/DataStore2/*.vmx: No such file or directory': No such file or directory
No .vmsd file found for vmdeb02 (5)
cat: can't open 'ls: /vmfs/volumes/DataStore2/*.vmx: No such file or directory': No such file or directory
cat: can't open 'ls: /vmfs/volumes/DataStore2/*.vmsd: No such file or directory': No such file or directory
grep: ls: /vmfs/volumes/DataStore2/*.vmx: No such file or directory: No such file or directory
cat: can't open 'ls: /vmfs/volumes/DataStore2/*.vmx: No such file or directory': No such file or directory
[vmdeb02] error DIFFEXUP: no VMDK disks present, skipping VM, nothing to backup


The same situation in test mode:
./xsibackup --backup-point=/vmfs/volumes/DataStore1/backup --backup-type=running --test-mode=true


Getting list of all VMs...
----------------------------------------------------------------------------------------------------------
4      vmw702    [DataStore2] vmw702/vmw702.vmx     windows7_64Guest   vmx-13   
5      vmdeb02    [DataStore2] vmdeb02/vmdeb02.vmx     debian9_64Guest    vmx-13                                                                                                           
6      vmw1002   [DataStore2] vmw1002/vmw1002.vmx   windows9_64Guest   vmx-13   
----------------------------------------------------------------------------------------------------------
VMs to backup:
----------------------------------------------------------------------------------------------------------
5      vmdeb02    [DataStore2] vmdeb02/vmdeb02.vmx     debian9_64Guest    vmx-13                                                                                                           
----------------------------------------------------------------------------------------------------------
Needed room: 3 Gb.
Sparse size: 50 Gb.
Available room: 127 Gb.
----------------------------------------------------------------------------------------------------------
[vmdeb02] Starting backup (size is 3862M on 51200M file)
----------------------------------------------------------------------------------------------------------
XSIBackup will backup your VMs while they are running and will quiesce guest services too, so that users
can continue to use the VM while the backup is taking place. You can also run cold and warm --backup-how
----------------------------------------------------------------------------------------------------------
Hot backup selected for VM: [vmdeb02], will not be switched off
----------------------------------------------------------------------------------------------------------
ls: /vmfs/volumes/DataStore2/*.vmx: No such file or directory
cat: can't open '': No such file or directory
[vmdeb02] info: boot partition is MBR
----------------------------------------------------------------------------------------------------------
Test mode activated VMs will not be cloned, please remove --test-mode=true to allow backups
----------------------------------------------------------------------------------------------------------
No errors detected in backup
----------------------------------------------------------------------------------------------------------
Backup finished
Tip: no chained backups scheduled, set --on-success and/or --on-error arguments to chain a backup
----------------------------------------------------------------------------------------------------------
XSIBACKUP_EXIT_STATUS=0
Killed
[root@ruspbesx3111:/vmfs/volumes/5c64215a-6f651e98-0f7b-18a905705b7e/xsi-dir] vi conf/
dialogrc      root-crontab  smtpsrvs      xsiopts
[root@ruspbesx3111:/vmfs/volumes/5c64215a-6f651e98-0f7b-18a905705b7e/xsi-dir] vi conf/xsiopts
[root@ruspbesx3111:/vmfs/volumes/5c64215a-6f651e98-0f7b-18a905705b7e/xsi-dir] ./xsibackup --backup-point=/v
mfs/volumes/DataStore1/backup --backup-type=running --test-mode=true
###############################################################################
#
#  (c) XSIBACKUP-FREE 11.0.1 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com
#
###################################################################################

NOTICE: (c) XSIBackup kills any user launched jobs, make sure you don't overlap manual jobs
----------------------------------------------------------------------------------------------------------
XSIBackup PID:           127058                                    esxhost02.domain.local
Sun, 17 Feb 2019 15:46:03 +0000                                IPv4: 192.168.1.10/255.255.255.0
VMware ESXi 6.5.0 build-11925212                              (c) Rsync 3.1.0 as opt. dependency
----------------------------------------------------------------------------------------------------------
Backup Id:              unknown                         Six-Core AMD Opteron(tm) Processor 2435
----------------------------------------------------------------------------------------------------------
Message: crontab is installed for user root
----------------------------------------------------------------------------------------------------------
ADVICE: no SSD disks, please consider adding an SSD cache disk to improve performance
----------------------------------------------------------------------------------------------------------
sh: rsync: unknown operand
Backup user is: root
----------------------------------------------------------------------------------------------------------
--backup-point found at /vmfs/volumes/DataStore1/backup (filesystem: VMFS-6)
----------------------------------------------------------------------------------------------------------
E-mail Warnings
----------------------------------------------------------------------------------------------------------
The e-mail report will not be sent because of the followig reasons:
The --mail-from string has not been set
The --smtp-srv string has not been set
The --smtp-port string has not been set
The --smtp-usr string has not been set, you need --smtp-usr if --smtp-auth is other than -none-
The --smtp-pwd string has not been set, you need --smtp-pwd if --smtp-auth is other than -none-
----------------------------------------------------------------------------------------------------------
Getting list of all VMs...
----------------------------------------------------------------------------------------------------------
4      vmw702    [DataStore2] vmw702/vmw702.vmx     windows7_64Guest   vmx-13    
5      vmdeb02    [DataStore2] vmdeb02/vmdeb02.vmx     debian9_64Guest    vmx-13                                                                                                           
6      vmw1002   [DataStore2] vmw1002/vmw1002.vmx   windows9_64Guest   vmx-13    
VMs to backup:
----------------------------------------------------------------------------------------------------------
5      vmdeb02    [DataStore2] vmdeb02/vmdeb02.vmx     debian9_64Guest    vmx-13                                                                                                           
----------------------------------------------------------------------------------------------------------
Needed room: 3 Gb.
Sparse size: 50 Gb.
Available room: 127 Gb.
----------------------------------------------------------------------------------------------------------
[vmdeb02] Starting backup (size is 3862M on 51200M file)
----------------------------------------------------------------------------------------------------------
XSIBackup will backup your VMs while they are running and will quiesce guest services too, so that users
can continue to use the VM while the backup is taking place. You can also run cold and warm --backup-how
----------------------------------------------------------------------------------------------------------
Hot backup selected for VM: [vmdeb02], will not be switched off
----------------------------------------------------------------------------------------------------------
ls: /vmfs/volumes/DataStore2/*.vmx: No such file or directory
cat: can't open '': No such file or directory
[vmdeb02] info: boot partition is MBR
----------------------------------------------------------------------------------------------------------
Test mode activated VMs will not be cloned, please remove --test-mode=true to allow backups
----------------------------------------------------------------------------------------------------------
No errors detected in backup
----------------------------------------------------------------------------------------------------------
Backup finished
Tip: no chained backups scheduled, set --on-success and/or --on-error arguments to chain a backup
----------------------------------------------------------------------------------------------------------
XSIBACKUP_EXIT_STATUS=0
Killed

P.S. After rollback to old ESXi 6.5 build problem still exists. Possibly this issue connected with AMD CPU hardware.

Pages: 1

Board footer