Can I safety assume that this full backup is complete with success, just that changed block tracking for incremental backup may not work?
Yep, this message is supposed only to indicate that CBT has not been used for some reason.
Moreover, even incremental backup will be possible, though it’s VB&R proprietary mechanism that will be utilized instead of CBT. If CBT doesn't work, VB&R scans through the VM image and a checksum (hash) is calculated for every data block, then it verifies what blocks have been changed on your VM compared to the VM image stored in the backup file.
Also, Veeam backup to local storage has no issue, but when backing up to a mapped network storage, Veeam will show this error:
Could not perform threshold check for backup location "Y:\" due to space info retrievement fail!
This issue must have been resolved in patch#1
; so, it might be worth updatining your VB&R instance.
How do I get mapped shared storage to work with Veeam without having to backup to local storage first and move to a shared network storage?
Unfortunately, Veeam agents are not supported on SMB share, thereby, data to the SMB share is written from a Windows-based proxying server. The role of default proxying server is played by VB&R server.
Finally, some VMs cannot be backed up. Veeam will just show this:
Waiting for backup infrastructure resources availability
What could be the possible cause?
In nutshell, resource availability issue means that the Veeam proxies have all the jobs they can handle - i.e. each proxy's max concurrent task settings (the Proxy rule is 1 task per 2 CPU). For instance, if a proxy has a setting of 2 concurrent tasks and you schedule 10 jobs to start simultaneously. Then, only the first 2 will be run, meanwhile, the other 8 will be waiting till a job is finished and free up required resources for others to run.
You can either give the proxy more cpus and change the concurrent task setting or add more proxies.
Hope this helps.