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

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#1 General matters » Backup issues » 2021-10-14 08:47:34

derilium
Replies: 1

Using XSI Backup Pro 1.2.9 and have 2 errors on the backups.

The first is after moving a backup file to a datastore, all the other VM's backup without a problem but this one fails in creating a directory on the target NFS datastore

error: vmkfstools error, details: Failed to clone disk: Not a directory (1310729).

mkdir: can't create directory '/vmfs/volumes/

On another server we have an issue

vmkfstools error, details: Failed to clone disk: The destination file system does not support large files (12).

Other than a disconnect and reconnect of the NFS data store nothing has changed.

#2 Re: General matters » Permissions issues and cron not starting » 2020-09-15 11:09:54

No joy, ran the command as root (was logged in as root and no error appeared) changed the cron to run at a later time, cleared the xsi backup log then checked the log /scratch/XSI/XSIBackup-Free/jobs/001: line 1: /scratch/XSI/XSIBackup-Free/: Permission denied.

If i run the backup command manually from the same command line it runs fine without any problem.

#3 Re: General matters » Permissions issues and cron not starting » 2020-09-15 09:33:11

Thanks, i've run that command so will see what happens, the strange thing is i have logged in as root on putty and installed XSI Backup from that user so everything is being run as that user so there shouldn't be a permissions problem

#4 General matters » Permissions issues and cron not starting » 2020-09-14 17:07:06

derilium
Replies: 4

I've been having a fight with this for a while, version 11 running on two servers will not run cron and did not send emails.
sorted the email problem by deleting the files that are used to connect to the email server (gmail) and generated my own.
Then i couldn't get cron to work so removed all traces of XSI backup and installed the latest version which now seems to install to scratch instead of the original default location (i initially changed it when installing but that didn't seem to work)

The backup works fine manually but will not work with cron even though it is pointing to the same location.

re-installed cron and ran the update against cron to confim it went into the cron tab.

now when it runs i get /scratch/XSI/XSIBackup-Free/jobs/001: line 1: /scratch/XSI/XSIBackup-Free/: Permission denied

I have checked the permissons and added 770 to all and i am running this as root.

any idea's

#5 Re: General matters » terminate called after throwing an instance of 'Vmacore::SystemExcep » 2019-10-09 09:56:00

Just adding to this, i am backing up to a datastore that is hosted on a NAS which is also being used by another ESXI server, which backs up fine. also the datastore on the ESXI has ample storage space.

So both are fine and i am still seeing this error.

#6 Re: General matters » terminate called after throwing an instance of 'Vmacore::SystemExcep » 2019-10-08 14:57:52

Are you saying that it looks like the hardware is failing or is it something else?

#7 Re: General matters » terminate called after throwing an instance of 'Vmacore::SystemExcep » 2019-10-08 08:33:52

Thanks for coming back with a possible fix, doesn't look like that is the issue.

Any other idea's would be greatly appreciated as running it during the day is a pain

stat -f /
  File: "/"
    ID: 100000000 Namelen: 127     Type: visorfs
Block size: 4096
Blocks: Total: 467340     Free: 299380     Available: 299380
Inodes: Total: 655360     Free: 648781

#8 General matters » terminate called after throwing an instance of 'Vmacore::SystemExcep » 2019-10-07 09:30:35

derilium
Replies: 6

Strange one this one, my backup that runs on a cron fails with the following error:-

terminate called after throwing an instance of 'Vmacore::SystemException'
  what():  No space left on device

I have checked both the main datastore and also the backup datastore and both enough space, if i run the backup manually xsibackup run job001 then it runs fine, but fails on the cron.

Any idea's

#9 Re: General matters » SMTP not working in 11.2.8 » 2019-09-27 12:10:40

Just like to say thanks to support and a big thanks to NikolaiAB as his fix worked great and i'm now getting my emails again...

#10 General matters » XSIBackup Pro 11.2.10 issue with PEM » 2019-09-10 11:13:30

derilium
Replies: 1

Having an issue sending email, i have removed any reference to pem, rsa etc when changing mail servers, i have ran the test xsibackup --check-smtp --use-smtp=1 etc and i receive this error

Unable to load client certificate private key file
Pem routines:Pem_read_bio:no start line:pem_lib.c:697: expecting any private key
Firewall rule smtpout-25 closed

I have tried with the free version, gave up and then installed the pro version and am having the same error on 3 different VM hosts.

#11 Re: General matters » SMTP not working in 11.2.8 » 2019-09-10 10:01:49

The plot thickens, i have tried with a different mail server smtp-mail.outlook.com, cleared down the keys, pem, pub etc and re-ran the check and now i'm getting unable to load the client certificate private key file. routings:PEM_read_bio:no start line:pem_lib.c:697:expecting: any private key

There is definitely something wrong with this version, i may have to revert back

#12 Re: General matters » SMTP not working in 11.2.8 » 2019-09-09 10:45:18

Any chance of a copy of the 11.2.9 free version to confirm, it does seem a bit odd and i'm not the only person having this issue

#13 Re: General matters » SMTP not working in 11.2.8 » 2019-09-03 07:29:11

In your screenshot above its for 11.2.9 XSIBackup-Pro and i am running 11.2.8 Free, do you have a copy of 11.2.9 Free as there is a mismatch in the version number?

#16 Re: General matters » SMTP not working in 11.2.8 » 2019-08-30 07:01:00

6.5.0 Update 3 (Build 14320405) on both servers

#17 Re: General matters » SMTP not working in 11.2.8 » 2019-08-29 15:39:41

So if you replace request.key, xsibackup_id_rsa, xsibackup_id_rsa.pub and xsibackup_id_rsa.pem with ones from a know working earlier version it works

#18 Re: General matters » SMTP not working in 11.2.8 » 2019-08-29 15:37:47

Just a heads up it has something to do with the way the key is generated, i replaced the key with an older one and it then works.
The new key generates an OpenSSL the old one is an RSA

The only problem is now i only have a key for one of the servers

#19 General matters » SMTP not working in 11.2.8 » 2019-08-28 11:43:33

derilium
Replies: 20

I upgraded to the new version from a version 9 which was all working, only issue was that an error happened after updating to the latest ESXI. with that in mind i upgraded to the latest version (11.2.8) and took the information regarding SMTP into the new config files.

The backup run but never sends an email, its connects to the gmail server but then drop the connection.


Using SMTP server #2: smtp.gmail.com:465
Open firewall: 2019-08-28T11:24:45|  Opening port 465 for SMTPout-465 service...
USING KEY: xsibackup_id_rsa
Firewall rule SMTPout-465 closed.
Killed

and nothing is sent, this is the free version

a connection can be established using NC and also ping requests work

Any help would be greatly appreciated

#20 Re: General matters » Installed XSIBackup 11.0.2 on a blank ESXI server with a few issues » 2018-08-16 09:38:18

Now that i never knew, i've always install the specific manufacturer build as it comes with all the correct drivers, vibs etc. i will make a note of that

#21 Re: General matters » Installed XSIBackup 11.0.2 on a blank ESXI server with a few issues » 2018-08-16 07:51:51

Sorry my fault, should have been more clear...the VM host has VM's on it, its just never had xsi-backup on it. it was cleanly built 2 days ago using a Dell ESXI image, once the manual backup is done will run through and get the errors

#22 General matters » Installed XSIBackup 11.0.2 on a blank ESXI server with a few issues » 2018-08-15 11:06:16

derilium
Replies: 5

Have installed the pro version on a clean ESXI 6.5 server, have run through the GUI and configured the job, cron etc
When moving through the gui some errors are thrown up (something about eval...it doesnt stay up long enough to read)
The job didn't fire last night and also there is nothing in the log to say there was a problem.

I'm probably missing something here, the earlier versions (Version 9+)seem to just work upon install, change of config file  and a reboot of the server, this version seems to be a bit of a struggle.

I have been really impressed with the software over the years and really commend the guys for making it

rob

#23 Re: General matters » Problem getting XSIBackup Pro squeduled under cron » 2018-07-20 11:15:21

Thanks for coming back to me, i can only assume the install must have not gone through ok as i don't have a xsibackup.log in the location you mention, its in the xsi-dir/var/logs folder and the file is empty

As for the one line i get 67694 67694 busybox /usr/lib/vmware/busybox/bin/busybox crond

I think the only option would be to uninstall and start again, would you agree and if thats the case whats the best way of doing it?

#24 Re: General matters » Problem getting XSIBackup Pro squeduled under cron » 2018-07-20 07:55:57

Thanks, i have removed the line, ran the update on cron and its still not firing (it was scheduled for last night and didn't kick in) anything else that i have missed.

#25 General matters » Problem getting XSIBackup Pro squeduled under cron » 2018-07-19 13:53:22

derilium
Replies: 5

I have been using different versions of XSIbackup over the years and it has been a great bit of software, it has been very easy to deploy and get up and running. On the latest version 11.0.2 Pro i'm really struggling to get it to run on a schedule using cron.

I have a job called 001 containing this:-

# This is a backup job file example. It starts with the path to your
# xsibackup file and ends with the redirection to the log file. Please
# do make sure that you keep first and last lines, changing paths to
# match your working environment.

"/vmfs/volumes/datastore001/xsi-dir" \
--backup-prog=vmkfstools \
--certify-backup=yes \
--backup-point=/vmfs/volumes/VMDatastore/backups/$( date +%Y%m'00000000' ) \
--backup-type=Running \
--backup-how=Hot \
--remote-xsipath=/vmfs/volumes/datastore001/xsi-dir \
--use-smtp=2 \
--mail-to=robert.burnhope@bbsr.co.uk \
--backup-id=001 \
--description="VMKFSTOOLS backup of production VMs" \
--on-success="backupId->002" \
--on-error="backupId->002" \
--exec=yes >> "/vmfs/volumes/datastore001/xsi-dir/var/logs/xsibackup.log"

I have a root-crontab:-
# This crontab belongs to the root user, thus it starts by root-
# Add cron jobs to this file in the classic crond Linux way.
# This is an example of a backup job being run everyday at 2:00 a.m.
# change according to your needs and run ./xsibackup --update-cron
# min hour day mon dow command
0 13 * * * "/vmfs/volumes/datastore001/xsi-dir/jobs/001"

There is nothing in the xsibackup.log but in xsibackup-cron.log there is multiple /bin/sh: /vmfs/volumes/datastore001/xsi-dir/xsibackup-cron: not found

If i run the command to backup the VM's manually ./xsibackup --backup-point=/vmfs/volumes/fa325c13-314f304a/backups --backup-type=running --date-dir=yes --mail-from=no-reply@someemail.com --mail-to=jo.bloggs@someemail.com --smtp-srv=smtp.soememail.com --smtp-port=465 --smtp-usr=bbsysnoreply@gmail.com --smtp-pwd=password --test-mode=true the test works and also by removing test it completes the backup

to add to this i have a root cron containing this:-
#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
*/1 * * * * '/vmfs/volumes/datastore001/xsi-dir/xsibackup-cron' >> '/vmfs/volumes/datastore001/xsi-dir/xsibackup-cron.log' 2>&1
0 13 * * * "/vmfs/volumes/datastore001/xsi-dir/jobs/001" # Added by XSIBackup


Where am i going wrong?

thanks

rob

Board footer