We are using Veeam Agent for Oracle Solaris 4.6.1.1789 on a SPARC kernel zone running Solaris 11.4 SRU 71. The documentatiob explicitly states that for file level backups, UNIX wildcards are only allowed in include/exclude lists for files, not in directories. I decided to try directory wildcards anyway.

In an include list, I indeed get an error when I specify a wildcard. However, when I use a wildcard in an exclude list, the wildcard is silently accepted:
Code: Select all
# veeamconfig job info --id d3d00216-2025-4b7f-8066-33647945ffa9
Backup job:
ID: {d3d00216-2025-4b7f-8066-33647945ffa9}
Name: test_rpool
Repository ID: {d08ef0f0-c17a-4c8d-9e70-c5a1ab78116b}
Repository name: [...] Backup Repository
Creation time: 2025-04-29 14:47:45
Options:
Compression: Zstd9
Max points: 7
Block size: 8192 KB
File system indexing is disabled
Objects for backup:
Include Directory: /
Exclude Directory: /dev
Exclude Directory: /devices
Exclude Directory: /home
Exclude Directory: /net
Exclude Directory: /nfs4
Exclude Directory: /proc
Exclude Directory: /system
Exclude Directory: /global
Exclude Directory: /etc/mnttab
Exclude Directory: /tmp
Exclude Directory: /etc/dfs/sharetab
Exclude Directory: /media
Exclude Directory: /opt/pp* <--- wildcard
Implicitly excluded directories:
//root/var/share/sstore/repo <--- does not exist
/dev/fd
/system/contract
/system/object
/system/volatile
/tmp/veeam
/var/share/sstore/repo
Also, I noticed that the "Implicitly excluded directories" list contains two entries for the "sstore" repository. The first one ("//root/var/share/sstore/repo") does not exist. How do I get rid of this spurious entry?
Thanks,
VAB