Mon full backup (Synthetic full)
Tue 7 times incremental (forward) all incrementals starts at 18:00 and the last incremental ends at 22:30
Wed 7 times incremental (forward) all incrementals starts at 18:00 and the last incremental ends at 22:30
Thr 7 times incremental (forward) all incrementals starts at 18:00 and the last incremental ends at 22:30
Fri 7 times incremental (forward) all incrementals starts at 18:00 and the last incremental ends at 22:30
Sat GFS backup
Now i get on saturday the following message on the GFS backup job: 27-10-2018 00:00:19 :: No GFS candidate for Weekly media set was found for today, waiting.
This is the same schedule i user at other customer sites and there it works fine. This customer uses Veeam Backup and Replication 9.5 (build 9.5.0.1536)
Case # 03261276
I have changed the following registry settings on the Veeam B&R server
Code: Select all
MaxSnapshotsPerDatastore 12
(https://bp.veeam.expert/architecture-overview/interaction_with_vsphere)
Change done for this issue
The default number of concurrently open snapshots per datastore in Veeam Backup & Replication is 4. This behavior can be changed by creating the following registry key:
•Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
•Key: MaxSnapshotsPerDatastore
•Type: REG_DWORD
•Default value: 4
Code: Select all
TapeWaitForActiveStorageTimeoutInHours 0
(https://forums.veeam.com/tape-f29/basic-question-about-gfs-t51856.html)
Description: Specify a value in hours that GFS jobs should wait for the active restore point (locked by the source job). By default GFS job waits for up to 7 days till the lock is released.
If the value is 0, GFS job will immediately switch to the previous storage.
Code: Select all
TapeGFSBackupWaitTimeout 0
(https://forums.veeam.com/tape-f29/basic-question-about-gfs-t51856.html)
Change done for this issue
the new restore points for up to 24h before failing over to taking the previous restore point. If the value is 0, a GFS job will start at 12AM using an existing restore point.