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

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#1 Re: General matters » How to delete all XSITool backups of a VM ? » 2019-09-06 14:29:49

NextLevel wrote:

Well, as said, I need to free up some space, so open a new set is not an option, since there is not enough space  smile

Conclusion:

I cannot run any further backups unless I delete all (instead just the ones I don't need).

Feature request: Pruning by VM name from repository or an option to cleanup a repository by search and delete orphaned blocks.

Well the official (and only supported) way is to use different sets of repositories. In the beginning I was also using one XSI repository and tried to cleanup on the go. I'm now using one repository per month (date +%Y-%m) and simply remove the second oldest repository with a cron job. This way I'm always having at least 4 weeks worth of backups.

Nevertheless, I've created a quick and dirty shell script which can "clean up" an XSItools repository (the data blocks). It simply goes through the list of all referenced blocks (the *-flat.vmdk files in the XSItools repo lists the hashes of all the blocks used by this vmdk) and compares this list with the list of physical blocks stored under the data directory in the XSItools repo.

Drop me a note if you want to have a look at this script.

Regards,
Bernhard

#2 Re: © OneDiff » error OVMXCHK1: VMX file check » 2017-10-04 15:01:46

If you want to check what's exactly stored in the first line you could run:
cat vm.vmx | tail -n1 | od -c

The output should look similar to this:

# cat "vmvc.vmx" | head -n1 | head -n1 | od -c
0000000   .   e   n   c   o   d   i   n   g       =       "   U   T   F
0000020   -   8   "  \n
0000024

#3 Re: General matters » CRON job does not start » 2017-09-28 08:01:35

Have you checked /var/log/syslog.log?
In my installation there is an entry every minute which looks like this:
2017-09-28T07:59:01Z crond[418094845]: crond: USER root pid 455405701 cmd '/vmfs/volumes/sas01/xsi-dir/xsibackup-cron' >> '/vmfs/volumes/sas01/xsi-dir/xsibackup-cron.log' 2>&1

In the past I had problems because of syntax errors in the xsibackup-cron file and looking into that file gave me the hint.

#4 Re: General matters » Backup remote server - way to specify datastore name for xsi-dir? » 2017-08-29 20:17:36

I had the same issue, using one standalone ESXi server to start all xsibackup jobs. Most of them run on remote ESXi hosts (which are part of a vSphere Essentials cluster but that doesn't really matter).

For quite some time now, xsibackup-pro loads additional code files in its own directory with the .inc extension. I'm using this feature to set the xsidefaultpath depending on the mode of operation (local or remote execution). On the machine starting all the remote jobs I've created a file called path.inc in the xsibackup directory. The content of the file looks like that:

if [ ! -z "$host" ]
then
  if [ "$host" = "remotehost1" ]
  then
    xsidefaultpath="/vmfs/volumes/remotehost1_datastore1/xsi-dir"
  fi
  if [ "$host" = "remotehost2" ]
  then
    xsidefaultpath="/vmfs/volumes/remotehost2_datastore1/xsi-dir"
  fi
else
  xsidefaultpath="/vmfs/volumes/localhost_datastore1/xsi-dir"
fi

I've also created path.inc files on all the remote hosts which just set the xsidefaultpath to the directory on this particular host.

Hope that helps,
Bernhard

Board footer