If you are running veeam backup replication 9 5 4 2866 if you need to download private fix for update 4b.
Veeam 9 5 full storage not found.
Open the home view.
To upgrade from 9 0 or earlier download the full iso image and consult the user guide s upgrade section.
In such situation veeam backup replication automatically disables automatic license update on the backup server or veeam backup enterprise manager server.
If you are running veeam backup replication 9 5 4 2753 you need to download private fix for update 4a.
Licensing by the contract has been terminated.
After upgrading your build will be version 9 5 0 1536.
By renaming the folder you can still restore from jobs in the renamed folder if need be.
The workaround was simple enough just remove the job from the backups not remove from disk once that is done rename the folder that holds the backup job in the repository and run the job again.
Make sure that no jobs are running close the console and stop all veeam services.
Veeam application and supported reference architecture requires a customer to retain manage local storage.
If you use veeam one to monitor veeam backup replication or veeam cloud connect be sure to install update 3 for veeam one 9 5 first.
Once you add a netapp storage system to veeam backup replication veeam performs the following operations.
In the backup properties window right click the missing restore point and select forget.
Such situation can occur due to connectivity issues between the veeam license update server and veeam backup replication.
In the working area select the backup and click properties on the ribbon or right click the backup and select properties.
Namely the issue backup jobs were listed in the database with a zero entry for the job id or repository id causing veeam to not be able to locate the backup files.
To remove records about missing restore points from the configuration database.
Performs initial system scan veeam gets specific storage information about cluster members ip addresses.
Configuration guide and best practices for netapp and veeam backup replication 9 5.
After opening a ticket with veeam they informed us that this is a known issue caused by unexpected backup entries in the veeambackup sql database.