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

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#2 Re: General matters » Backup fails - Error code 3923 can't access device /dev/disks/UUID » 2021-08-17 23:51:38

Hi Team,

This issue seems resolved with the provided release.
We will continue to monitor the status and let you know if there are further issues

#3 Re: General matters » Backup fails - Error code 3923 can't access device /dev/disks/UUID » 2021-08-17 23:14:47

Here is the output for your reference

[root@jp-tokyo-esxi2:~] vim-cmd vmsvc/getallvms
Vmid        Name                         File                          Guest OS          Version                                            Annotation
1      JP-TOKYO-DNS2    [VM] JP-DNS2/JP-DNS2.vmx                 centos7_64Guest         vmx-13                                             
10     JP-VEEAM         [VM] JP-VEEAM/JP-VEEAM.vmx               windows9Server64Guest   vmx-13                                             
11     JP-PANOPTA       [VM] JP-PANOPTA/JP-PANOPTA.vmx           ubuntu64Guest           vmx-13                                             
7      JP-FAC-TEST      [VM] JP-FAC-TEST/JP-FAC-TEST.vmx         other26xLinuxGuest      vmx-10    FortiAuthenticator Virtual Appliance by Fortinet Technologies Inc. (https://www.fortinet.com)
8      JP-Ubuntu-Test   [VM] JP-Ubuntu-Test/JP-Ubuntu-Test.vmx   ubuntu64Guest           vmx-13                                             
[root@jp-tokyo-esxi2:~]
[root@jp-tokyo-esxi2:~]
[root@jp-tokyo-esxi2:~] vmware -v
VMware ESXi 7.0.1 build-17551050
[root@jp-tokyo-esxi2:~]

We will try the suggested version and update later

#4 Re: General matters » Backup fails - Error code 3923 can't access device /dev/disks/UUID » 2021-08-17 08:54:05

Hi team,

Thanks a lot for your response. Below is your requested information

[root@jp-tokyo-esxi2:~] ls -al /vmfs/volumes/
total 3588
drwxr-xr-x    1 root     root           512 Aug 17 08:52 .
drwxr-xr-x    1 root     root           512 Feb 26 07:46 ..
drwxrwxrwx    1 root     root           706 Aug 17 02:19 308f2f08-3e85e816
drwxr-xr-x    1 root     root             8 Jan  1  1970 582d37d9-ff441041-c789-f8511512c1da
drwxr-xr-t    1 root     root         73728 Aug 17 02:34 5d0c9541-3f06c58c-f3ba-0cc47afdd2be
drwxr-xr-t    1 root     root         77824 Mar  8 00:50 5d0ca287-dc7c5890-0873-0cc47afdd2be
drwxr-xr-x    1 root     root             8 Jan  1  1970 5faccf62-4e451b9c-6331-0cc47afdd2be
drwxr-xr-t    1 root     root         77824 Jan 15  2021 5facd03d-2dfad930-a2d8-0cc47afdd2be
lrwxr-xr-x    1 root     root            35 Aug 17 08:52 BOOTBANK1 -> 5faccf62-4e451b9c-6331-0cc47afdd2be
lrwxr-xr-x    1 root     root            35 Aug 17 08:52 BOOTBANK2 -> 582d37d9-ff441041-c789-f8511512c1da
lrwxr-xr-x    1 root     root            35 Aug 17 08:52 ESXi -> 5d0c9541-3f06c58c-f3ba-0cc47afdd2be
lrwxr-xr-x    1 root     root            35 Aug 17 08:52 OSDATA-5facd03d-2dfad930-a2d8-0cc47afdd2be -> 5facd03d-2dfad930-a2d8-0cc47afdd2be
lrwxr-xr-x    1 root     root            35 Aug 17 08:52 VM -> 5d0ca287-dc7c5890-0873-0cc47afdd2be
lrwxr-xr-x    1 root     root            17 Aug 17 08:52 nasbackup -> 308f2f08-3e85e816
[root@jp-tokyo-esxi2:~]
[root@jp-tokyo-esxi2:~]
[root@jp-tokyo-esxi2:~]
[root@jp-tokyo-esxi2:~]
[root@jp-tokyo-esxi2:~] esxcli storage vmfs extent list
Volume Name                                 VMFS UUID                            Extent Number  Device Name                           Partition
------------------------------------------  -----------------------------------  -------------  ------------------------------------  ---------
ESXi                                        5d0c9541-3f06c58c-f3ba-0cc47afdd2be              0  naa.60030480253bc9002450c8c504acb6bc          8
VM                                          5d0ca287-dc7c5890-0873-0cc47afdd2be              0  naa.60030480253bc9002450c8be043f7568          2
OSDATA-5facd03d-2dfad930-a2d8-0cc47afdd2be  5facd03d-2dfad930-a2d8-0cc47afdd2be              0  naa.60030480253bc9002450c8c504acb6bc          7

#5 General matters » Backup fails - Error code 3923 can't access device /dev/disks/UUID » 2021-08-17 06:07:49

netsky
Replies: 7

I downloaded the latest version of xsibacup DC today and tried on ESXi 7.0 free but got the below error

[root@jp-tokyo-esxi2:/vmfs/volumes/5d0c9541-3f06c58c-f3ba-0cc47afdd2be/XSIBackup-DC/etc/jobs] ./panopta-backup
|---------------------------------------------------------------------------------|
||-------------------------------------------------------------------------------||
|||   (c)XSIBackup-Free 1.5.0.13: Backup & Replication Software                 |||
|||   (c)33HOPS, Sistemas de Informacion y Redes, S.L. | All Rights Reserved    |||
||-------------------------------------------------------------------------------||
|---------------------------------------------------------------------------------|
                   (c)Daniel J. Garcia Fidalgo | info@33hops.com
|---------------------------------------------------------------------------------|
System Information: ESXi, Kernel 7 Major 0 Minor 1 Patch 0
-------------------------------------------------------------------------------------------------------------
License: unlicensed trial version, remaining trial time: 150:00:42 | (c)XSIBackup-Free
-------------------------------------------------------------------------------------------------------------
PID: 4828487, Running job as: root
-------------------------------------------------------------------------------------------------------------
(c)XSIBackup-Free replicating data to /vmfs/volumes/VM/VMBackup
-------------------------------------------------------------------------------------------------------------
Performing --replica action
-------------------------------------------------------------------------------------------------------------
Backup folder '/vmfs/volumes/VM/VMBackup'
-------------------------------------------------------------------------------------------------------------
Item number 1 in this job
-------------------------------------------------------------------------------------------------------------
Available space in backup volume:           2999722180608 (2.79 TB)
-------------------------------------------------------------------------------------------------------------
JP-PANOPTA Hardware Version is: 13
-------------------------------------------------------------------------------------------------------------
Virtual Machine Name: JP-PANOPTA
-------------------------------------------------------------------------------------------------------------
(c)ESXi 7.0 or higher detected, all snapshots were removed for VM JP-PANOPTA(11)
-------------------------------------------------------------------------------------------------------------
Creating snapshot VM : JP-PANOPTA (powered on)
-------------------------------------------------------------------------------------------------------------
*** Snapshot was successfully created ***
-------------------------------------------------------------------------------------------------------------
Virtual Machine: JP-PANOPTA
-------------------------------------------------------------------------------------------------------------
Backup start date: 2021-08-17T05:59:22
-------------------------------------------------------------------------------------------------------------
2021-08-17 05:59:22 | Backing up 17 files, total size is 58.30 GB
-------------------------------------------------------------------------------------------------------------
    NUMBER                                                         FILE             SIZE          PROGRESS
-------------------------------------------------------------------------------------------------------------
    1/17                                                 JP-PANOPTA.vmx          2.89 KB    | Done   0.00%
-------------------------------------------------------------------------------------------------------------
2021-08-17T05:59:22 | Error code 3923 at file xsibackup.c, line 3923 | Error description: can't access device /dev/disks/UUID
-------------------------------------------------------------------------------------------------------------
    2/17                                           JP-PANOPTA-flat.vmdk         50.00 GB    | Done   0.00%
-------------------------------------------------------------------------------------------------------------
2021-08-17T05:59:23 | Error code 279 at file copy-in.c, line 279 | Error description: can't open input file: /dev/disks/UUID


The backup command is as below

/vmfs/volumes/ESXi/XSIBackup-DC/xsibackup \
--replica \
"VMs(JP-PANOPTA)" \
"/vmfs/volumes/VM/VMBackup" \



/vmfs/volumes/VM is internal datastore. We tried with NFS datastore but experienced the same error

#6 General matters » xsibackup-free license » 2021-01-16 23:56:05

netsky
Replies: 1

We downloaded and installed the xsibackup-dc 1.4.3.0 successfully.
However, after 2-3 days, it asks for license to run the replica backup.
Do we need to input a license for free version? if Yes, how to get a license key for free version?

Thanks and best regards,

#7 Re: General matters » Backup 11.0.1 free version - cron does not work (solved) » 2018-07-24 03:10:45

I finally make it works.
I had to break down the command into multiple lines and put the exec=yes before the pipeline as written in the guide.

Thank you very much for your support!

#8 Re: General matters » Backup 11.0.1 free version - cron does not work (solved) » 2018-07-20 00:12:12

I checked at the time cron job started and found the message indicated that backup completed in the cron job log just few minutes after that.
Checking the backup target folder and no data there.
Also, it usually took about 1 hour for the backup job to complete.

I did check by running the job manually as well and it started without any issues.
Removing the cron job of the old version did not help to resolve the issue

#9 Re: General matters » Backup 11.0.1 free version - cron does not work (solved) » 2018-07-18 23:11:22

Yes, the cron is setup properly. I was able to confirm the message in the cron log. However, the backup process did not run as expected.

[root@esxi:~] more /var/spool/cron/crontabs/root
#min hour day mon dow command
1    1    *   *   *   /sbin/tmpwatch.py
1    *    *   *   *   /sbin/auto-backup.sh
0    *    *   *   *   /usr/lib/vmware/vmksummary/log-heartbeat.py
*/5  *    *   *   *   /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
00   1    *   *   *   localcli storage core device purge
0    1    *   *   *   /bin/esxi-conf-backup.sh
0       2    *   *   *   /vmfs/volumes/DATA/xsibackup-11.0.1/xsi-dir/jobs/001
*/1 * * * * '/vmfs/volumes/DATA/xsi-dir/xsibackup-cron' >> '/vmfs/volumes/DATA/xsi-dir/xsibackup-cron.log' 2>&1

#10 General matters » Backup 11.0.1 free version - cron does not work (solved) » 2018-07-18 07:04:50

netsky
Replies: 8
admin wrote:

(*) Please, note that this post is fairly old and that (c)XSIBackup has evolved to a next generation of (c)VMWare (c)Backup software. It follows the same design principles as (c)XSIBackup Classic, yet it's much more powerful.

You can still download (c)XSIBackup Classic, although it's older software and only compatible with (c)ESXi up to version 6.7U3

Dear Support team,

We just installed the 11.0.1 version and the test backup run without any issues.
We have setup the cron job within jobs/ directory as guided.

The cron job was confirmed to be appear in /var/spool/cron/crontabs/root file.

The backup script is as below

echo "Starting xsibackup job 001 .." >> /var/log/cron.log
/vmfs/volumes/DATA/xsibackup-11.0.1/xsi-dir/xsibackup --backup-point=/vmfs/volumes/ExtUSB/VMBackup --backup-type=all --snapshot=doquiesce --date-dir=yes
echo "Backup job completed ..." >> /var/log/cron.log


By checking the cron.log, we are able to confirmed that the cronjob started but it seems the backup had stopped immediately after started.
We run the script manually and it worked without any issues.


There is another issue with the free version.
The below command did not execute successfully. It stopped right away.
/vmfs/volumes/DATA/xsibackup-11.0.1/xsi-dir/xsibackup --backup-point=/vmfs/volumes/ExtUSB/VMBackup --backup-type=all --snapshot=doquiesce --date-dir=yes >> /var/log/cron.log

When removing the pipeline, it worked perfectly.

Would you please suggest on how to troubleshoot and fix this issue?

#11 Re: General matters » Skip VM listing » 2017-12-05 08:22:45

Many thanks for your response.
Got it. I think it would be nice just to scan the information one time, store in a fie and use it for the next time. It will save a lot of time in case there are a lot of VMs in the environment.
In my case, it took more than 1 hours just to list the VM.

#12 General matters » Skip VM listing » 2017-12-05 07:26:52

netsky
Replies: 2

Hi Team,

Are there any ways to skip the VM listing process and goes directly to the backup process of specific VM.
In our environment, there are many VMs and it took a lot of time in VM listing process.

Best regards,

Pham

Board footer