You are not logged in.
Warning: Newbie alert! OK, what am I doing wrong? I'm trying to exclude a vmdk.
./xsibackup --backup "VMs(neth3!neth3_1.vmdk)" email@example.com:22:/mnt/backup/xsidata --quiesce --remote-path=/opt/xsibackupdc/xsibackup
2020-09-09T03:17:26 | Error code 2194 at file xsibackup.c, line 2194 | Error description: could not find any VM in list: neth3!neth3_1.vmdk
If I run as:
./xsibackup --backup "VMs(neth3)" firstname.lastname@example.org:22:/mnt/backup/xsidata --quiesce --remote-path=/opt/xsibackupdc/xsibackup
...it runs fine.
You have asumed that the syntax to exclude disks in DC version is the same as in Pro, when it's not.
As stated in the -exclude- section of the manual:
https://33hops.com/xsibackup-dc-full-ma … ml#exclude
Exclusions are performed via the --exclude switch.
I switched to the --exclude="neth3_1.vmdk" per your advice and the manual but it still took a snapshot of the disk and appears to be trying to back it up. That disk is on another datastore from the "system" disk for this VM if that matters.
Use some REGEXP that mathes the full disk path, not just the file name.
Thank you for clarification.
Nonetheless you seem to have some sort of misconception on how snapshots work. You said "it still took a snapshot of the disk". Snapshots can't be controlled on a per disk basis, a snapshot will indeed affect all disks in a VM, excluding the disk at the backup job level is a different thing and has nothing to do with wether the snapshot is taken or not for that particular disk.
I have everything configured and it is working well now. Again, thank you for your patience and help.