You are not logged in.
Pages: 1
Interestingly, when I tried to manualy unregister a VM hosted on EXSi server which is registered with vCenter I got orphaned VM in vCenter inventory.
Two questions about that:
1) The unregister process should remove the VM from inventory?
2) The "--disable-vmotion" argument should disabe the vmkernel interface itself or just temporary remove the interface capacity to do vmotion?
Good afternoon everyone,
I use vCenter 6.5 managing 15 hosts with HA and DRS enabled.
After adding the "--options = unreg-xsibak" option in the backup schedule, most of the "_XSIBAK" VMs were marked as "orphaned".
Is that normal?
Thanks for replying!
I believe I found the cause of the problem, one of our coworkers was using the VMDK stored in the backup storage in an active VM, so the XSI was not able to remove the folder, which caused the timeout .
It would be interesting to have a warning about this in the log files.
After analyzing the target datastore, I believe that xsi is not able to delete the old backup folders. I can not find a reason for this, other servers are working normally and have identical installation.
Sure! sorry for the delay, here is the server configuration and log output:
xsibackup-cron line:
"/vmfs/volumes/datastore_esx5/xsi-dir/xsibackup" --time="Mon 03:00|Tue 03:00|Wed 03:00|Thu 03:00|Fri 19:30|Sat 03:00|Sun 03:00" --backup-point="/vmfs/volumes/backup_2" --date-dir=yes --backup-room=30000 --backup-type=running --mail-from=(EMAIL CONFIG OMITTED BY ME) --subject = "Host_10-90-0-5 - DateDir Backup"
#####################################################################################
# #
# (c) XSIBACKUP-FREE 9.0.1 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com #
# #
#####################################################################################
XSIBackup PID: 76173465 esx5.mydomain.edu.br
Mon, 18 Sep 2017 03:00:02 +0000 IPv4: 10.90.0.5/255.255.0.0
VMware ESXi 5.5.0 build-1331820 (c) Rsync 3.1.0 as opt. dependency
---------------------------------------------------------------------------------------------------------------------------------
2017-09-18T03:00:05| Found --backup-point at [ /vmfs/volumes/backup_2 ]
---------------------------------------------------------------------------------------------------------------------------------
2017-09-18T03:00:05| The backup room has been limited to 30000 gb.
2017-09-18T03:00:05| Getting list of all VMs...
---------------------------------------------------------------------------------------------------------------------------------
2017-09-18T03:00:06| 23 classificados [infra] osclass/osclass.vmx
...
--- Gigantic list of VMs
...
---------------------------------------------------------------------------------------------------------------------------------
2017-09-18T03:06:12| VMs to backup:
---------------------------------------------------------------------------------------------------------------------------------
2017-09-18T03:06:12| 23 classificados [infra] osclass/osclass.vmx ubuntu64Guest vmx-10
...
--- Another gigantic list of VMs
...
---------------------------------------------------------------------------------------------------------------------------------
2017-09-18T03:06:23| Needed room: 12942 Gb.
2017-09-18T03:06:23| Available room: -282 Gb.
---------------------------------------------------------------------------------------------------------------------------------
2017-09-18T03:06:23| Not enough room to make the backup, some older folders will be deleted
---------------------------------------------------------------------------------------------------------------------------------
2017-09-18T03:06:33| Excerpt
---------------------------------------------------------------------------------------------------------------------------------
2017-09-18T03:06:33| Hot backup selected for VM: [classificados], will not be switched off
---------------------------------------------------------------------------------------------------------------------------------
2017-09-18T03:06:36| [classificados] Info: attempting to free 107089 mb at [ /vmfs/volumes/backup_2 ]
---------------------------------------------------------------------------------------------------------------------------------
Killed
Good afternoon everyone!
A few days ago I'm having trouble with the scheduled cron jobs.
On several servers I have received the message below:
Destination disk format: VMFS thin-provisioned
Cloning disk '/vmfs/volumes/infra/compras-ti/compras-ti-000001.vmdk'...
Clone: 100% done.
2017-09-13T03:36:57| Excerpt
---------------------------------------------------------------------------------------------------------------------------------
2017-09-13T03:36:57| Hot backup selected for VM: [cofre], will not be switched off
---------------------------------------------------------------------------------------------------------------------------------
2017-09-13T03:37:00| [cofre] Info: attempting to free 3688039 mb at [ /vmfs/volumes/backup_2 ]
---------------------------------------------------------------------------------------------------------------------------------
Killed
Up until a few days ago the backup worked normally.
The destination datastore has 36TB and has free space.
What am I doing wrong?
Pages: 1