Forum ©XSIBackup: ©VMWare ©ESXi Backup Software
MenuYou are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: General matters » remote backup not working » 2018-03-13 18:05:08
Not completely related but I would also remove the --remote-xsipath. I was told to only use this if the auto detect takes too long and that it's better to let it do the auto detection whenever possible.
The list of all VMs appears to be blank. Add "--debug-info=yes" and it will append some debug stuff to the email.
#2 Re: General matters » remote backup not working » 2018-03-13 17:27:36
My issue ended up being that I needed to specify "--backup-prog=vmkfstools" in the remote command. While it defaults to this it was explained to me that with --host, since it is executing remotely, it needs this argument to be specified.
#3 Re: General matters » onediff and xsitools question » 2018-02-22 19:26:02
So with the ESXi that is on the same LAN as the NAS what command would I execute to make a copy of the files on NAS rather than a backup of the VMs on that particular ESXi server?
#4 General matters » remote backup not working » 2018-02-22 18:36:19
- ajarrett
- Replies: 6
Remote executing a backup with --host used to work but is not working now.
Command I'm using
/vmfs/volumes/m630-1_local/xsi-dir/xsibackup backupID=01 --host=<host> --time="Sun 00:00" --remote-xsipath=/vmfs/volumes/m630-2_local/xsi-dir --backup-point=/vmfs/volumes/Nas_Backup/VRTX-VMs --date-dir=yes --backup-type=custom --backup-vms="nervepoint" --mail-from=<from@email> --mail-to=<to@email> --smtp-srv=<smtphost> --smtp-port=25 --smtp-auth="none" --smtp-usr=any --smtp-pwd=any --debug-info=yes --exec=yes
The command executes.. copies the files over (subsequent executions states file already present). Then says Executing remote backup on <IP address>
When I check ./xsibackup --watch=<IP> I get the below.
###############################################################################
#
# (c) XSIBACKUP-PRO 10.2.10 | Backup for (c) VMWARE ESXi Hypervisor by 33hops.com
#
###################################################################################
Monitoring XSIBackup activity at <IP>
You can stop watching at any time by pressing [Control+C]
The remote backup process will continue at <IP>...
----------------------------------------------------------
Backup Id: 01Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T14:55:26| ADVICE: no SSD disks, please consider adding an SSD cache disk to improve performance
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T18:12:17| ###############################################################################
2018-02-22T18:12:17| XSIBACKUP-PRO 10.2.10: new execution request
2018-02-22T18:12:17| ###############################################################################
2018-02-22T18:12:17|
2018-02-22T18:12:18| NOTICE: (c) XSIBackup will kill any previous processes, make sure you don't overlap backup jobs
---------------------------------------------------------------------------------------------------------------------------------
XSIBackup PID: 416333 m630-2
Thu, 22 Feb 2018 18:12:18 +0000 IPv4: <IP>/255.255.255.224
VMware ESXi 6.5.0 build-6765664 (c) Rsync 3.1.0 as opt. dependency
---------------------------------------------------------------------------------------------------------------------------------
Backup Id: 01Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
---------------------------------------------------------------------------------------------------------------------------------
2018-02-22T18:12:20| ADVICE: no SSD disks, please consider adding an SSD cache disk to improve performance
---------------------------------------------------------------------------------------------------------------------------------
But then nothing else. I see the Backup ID is correctly specified but that's it.
#5 Re: General matters » onediff and xsitools question » 2018-01-30 21:15:47
I see your point. I do actually have another esxi on the other side that can be used and is attached to the same NAS storage.
What would be the command that I would issue to that esxi server to duplicate the backups that have already been completed?
#6 Re: General matters » onediff and xsitools question » 2018-01-29 20:02:19
Any thoughts on this or is it even possible since we are backing up to a datastore connected NAS? As mentioned I can't run the xsibackup on the backup location so that it looks local there as it's a NAS not a esxi host as what it appears the xsitools is expecting. Or if you have another solution for making a copy at a remote location I'm willing to try just about anything.
When I was creating backups local they were completing in a few minutes even doing full backups. Now that the backup is crossing the WAN it takes several hours which the onediff would fix if I could keep incrementals as well.
#7 Re: General matters » onediff and xsitools question » 2018-01-22 02:05:59
A sample of my test backup commands.
/vmfs/volumes/m630-1_local/xsi-dir/xsibackup backupID=00 --time="Sun 00:00" --backup-prog=onediff --backup-point=/vmfs/volumes/Nas_Backup/VRTX-VMs/onediff --backup-type=custom --backup-vms="WVM12R2-DC02" --mail-from=xsibackup@domain.com --mail-to=email@domain.com --smtp-srv=smtp --smtp-port=25 --smtp-auth="none" --smtp-usr=any --smtp-pwd=any --on-success="backupid->01" --on-error="backupid->01"
/vmfs/volumes/m630-1_local/xsi-dir/xsibackup backupID=01 --backup-prog=xsitools:z --backup-point="/vmfs/volumes/Nas_Backup/VRTX-VMs/onediff/xsit-$( date +'%Y-%m')" --backup-type=custom --backup-vms="WVM12R2-DC02" --mail-from=xsibackup@domain.com --mail-to=email@domain.com --smtp-srv=smtp --smtp-port=25 --smtp-auth="none" --smtp-usr=any --smtp-pwd=any --override=xsibakfilter
The second command initiates another backup across the WAN. What I would like to do is make a copy on the NAS of the backup created by the first command. I realize this will have a disk performance hit but will still be faster than another copy across the WAN. How do I specify in the xsibackup command with xsitools just to make a copy of those files rather than make another backup of the local VMs?
The destination (/vmfs/volumes/Nas_Backup/) is a datastore located on a NAS not another esxi server.
#8 Re: General matters » onediff and xsitools question » 2018-01-17 12:17:12
I’m not concerned with the performance hit as the destination is purely for vm backups.
Can you provide me an example of the command necessary to run the xsitools and specifying a source other than the vms stored locally on the esxi server you are running from?
#9 General matters » onediff and xsitools question » 2018-01-16 17:35:13
- ajarrett
- Replies: 8
I'm wanting to something similar to what is described in the blog post https://33hops.com/xsibackup-pro-onedif … olicy.html.
The issue is that I'm backing up to a NAS that is connected as a datastore. If I run xsibackup using xsitools I do not have a way to specify the source location for the backups so it just backs up the VMs on the local server. Any thoughts on how I could accomplish this backup scenario? Presently I'm doing full backups every weekend but would like to switch to onediff backups but keep a few of the past backups.
Pages: 1