While deploying the solution we ran some test restores that went as expected.
Veeam 9 5 error full storage not found.
In the backup properties window right click the missing restore point and select forget.
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.
In the inventory pane select disk under backups.
When creating my new backup jobs in v7 i had mapped the v6 5 backup data in backup repositories.
For backup copy jobs enable the read the entire restore point from source instead of synthesizing it from increments option.
To upgrade from 9 0 or earlier download the full iso image and consult the user guide s upgrade section.
After installing veeam 9 5 update 3 sql logs are not truncated during backup but the truncation task is still marked as a success in the job statistics.
Full storage not found after performing virtual machine restore with veeam.
In the working area select the backup and click properties on the ribbon or right click the backup and select properties.
Make sure that no jobs are running close the console and stop all veeam services.
After upgrading your build will be version 9 5 0 1536.
Install a hotfix for veeam backup replication 9 5 update 4 build 9 5 4 2615.
Sql log backup sessions complete with 0 kb tr.
August 3 2014 backup veeam vmware gregk78.
Stop all services on the veeam backup server that begin with veeam.
If you are running veeam backup replication 9 5 4 2866 if you need to download private fix for update 4b.
I ve just recreated backup jobs without mapping anything and now it s running fine.
Forward incremental with synthetic full backups will not rename vbk files but performance is usually much better with active full backups.
If you are running veeam backup replication 9 5 4 2753 you need to download private fix for update 4a.
I solved my problem.
I am a big fan of veeam for backing up and restoring virtual machines great product and support is very responsive when needed.