The warning “Completing backup copy interval for GFS full creation” appears at the end of a backup copy interval when Veeam needs to “seal” that cycle by creating the GFS full (weekly, monthly, or yearly) restore point. It’s informational—Veeam wraps up the current copy cycle and then either synthesizes a full on the target or performs an active full, depending on your GFS method.
Why It Happens
GFS schedule hit: The day/time for a weekly, monthly, or yearly point has arrived, so Veeam finishes the running copy cycle and creates the archive full.
Full type matters:
- Synthetic: Veeam builds the full from existing files on the repository.
- Active full: Veeam re-reads data from the source machine to create the GFS full.
When to Take Action
Most of the time, no action is needed. If you’re seeing long runs or warnings piling up, check the following:
- Copy interval and schedule: Make sure the interval and allowed windows provide enough time to finish before the GFS day arrives. Tight windows can force a “complete interval now” warning.
- GFS settings: Confirm which weeks or months are selected so the expected date aligns with your operations. Misaligned choices can create unexpected GFS builds.
- GFS method: On dedupe targets (StoreOnce, DD, etc.), consider using Active Full for GFS to reduce random I/O from synthetic builds.
- Target repository performance and space: Synthetic fulls read and write heavily on the target repository. Ensure I/O and free space are adequate.
It’s Veeam saying, “I’m ending this copy cycle now so I can make the scheduled GFS full.” It’s normal. Only make adjustments if it’s colliding with your backup windows or impacting duration—adjust the copy interval or schedule, align GFS dates, and choose Active Full for GFS on dedupe targets.
For more information, please contact us at Support@Managecast.com.