Too Many Restore Points – Backup Job

KB ID: 1990
Product: Veeam Backup & Replication
Version: 6.x, 7.x, 8.x
Published:
Last Modified: 2015-08-21

Challenge

You find that there are more restore points for a backup job than you have specified.

Cause

This most often occurs with traditional Forward Incremental, and rarely occurs with Forward-Incremental-Forever and Reversed Incremental rarely have this issue. Traditional Forward Incremental occurs when the Synthetic or Active Full option is enabled within a job, or an active full is manually generated via the job’s context menu.
 
The most common causes are:


C1. Expected effect of how retention is enforced with traditional forward incremental. The following articles should be read to understand this in depth:

C2. Not enough free space for a new full backup to be created. This is often caused by a misunderstanding regarding the number of full restore points a job will be required to maintain. For a job that is configured to have a weekly full restore point, you will need 1 full point for every 7 restore points set in retention, plus 1. A job that is set for 14 restore points will have a maximum of 3 full restore points, assuming the job runs daily.

C3. The Transform/Merge fails to process or the Synthetic full fails to be created. This often occurs due to:
  • Due to poor storage I/O performance. The common resolution is to switch to using the periodic active full option.
  • Not enough overhead free space to perform these type tasks.
Note: If the synthetic full backup fails and the retry begins on a day that the synthetic full is not scheduled, the job session will start, determine that there are no incremental VM tasks to retry and that a synthetic full is not scheduled, and then stop. This empty job session will be marked as a success because no errors occurred.

C4. The job did not perform the full or transform operation as scheduled. This often occurs due to:
  • The job being disabled on that day.
  • An incremental job session ran for more than 24 hours causing the job not to start on the scheduled day. For example, the full is scheduled for Saturday, but the incremental session that began Friday ran for more than 24 hours, so the next job session did not start until Sunday.
  • The Veeam Backup & Replication software was installed within an OS that was configured to sleep after a period of time causing the OS to be asleep at the time the job was to run.
  • The jobs are set to run in sequence, and the previous job ran past midnight causing this job to not run on the scheduled day for fulls. For example, the full is scheduled for Saturday, but the job is scheduled to run after a previous job completes, and so did not start until Sunday.
C5. Retention could not be enforced because the storage refused to allow the delete operation.

C6. Anti-Virus prevents Veeam deleting or modifying existing backup files.
 

Solution

The following tasks can be performed to resolve an issue where a repository has become full.
 
Similar to when a circuit breaker trips at home, you must first resolve why it triggered before resetting it, else it may trigger again. If your repository has become full you must assess the root cause of the present situation, else any solution below may just put you back in to a situation where the same thing could occur again.
 
Note: Please understand that there are many variables to account for when considering how to resolve this situation. Due to this complexity this KB article may not cover all situations.
 
Choose which of the following cases applies to you based on the backup files in your storage. If you are not sure which case applies, read the Terminology section, below.
 
──────────────────────────────────────────────────────────
# of Backup Sets Present on Storage: 1
# of Full Restore Points in Backup Set: 1

Troubleshooting Steps (Do the first step and retry the job, moving to the next step only in case of failure):

S1.1. Disable Synthetic Full and Active Full option forcing the job to run in Forward Incremental Forever mode, then set retention to less than the number of restore points that are presently filling the storage.
S1.2. If space is available to hold on to all old restore points, manually move all restore points to another location. Then start a new backup set: http://www.veeam.com/kb1885
Note:You can always manually import the old restore points should you need to perform a restore. Keep in mind the files moved off to the new location will not be controlled by the jobs retention and will need to be managed manually.
S1.3. If you have no storage available elsewhere to store the old restore points, the existing backup chain must be deleted. Follow the steps to create a new backup set, but instead choose Remove from disk.
──────────────────────────────────────────────────────────
# of Backup Sets Present on Storage: 1
# of Full Restore Points in Backup Set: 2 or more
 
Troubleshooting Steps (Do the first step and retry the job, moving to the next step only in case of failure):
S2.1. Set retention to a value  that would cause the oldest backup chain to exceed retention and automatically be removed. 
  1. Navigate to the location where the backup files are stored for the job in question.
  2. Order the backup chain from oldest at top to newest at bottom
  3. Count backwards from the bottom to the most recent vbk
  4. Change the retention within the job to that number and run the job again.
  5. When the job succeeds, the old chain will be removed via retention.
Note: It is possible the disk is too full and the job may fail without enforcing the new retention.

S2.2. Manually delete the oldest backup chain.
Note: The software will continue to think the files that were manually removed exist until those points fall outside the configured retention scope.
 
──────────────────────────────────────────────────────────
# of Backup Sets Present on Storage: 2 or more
# of Full Restore Points in Largest Backup Set: 1
 
If there is not enough space for this backup set to maintain the number of needed fulls, it may be advisable to switch to Forward Incremental Forever or Reversed Incremental.
 
Troubleshooting Steps (Do the first step and retry the job, moving to the next step only in case of failure):
S3.1. Move some of the other backup sets off the storage temporarily. Switch the large backup set to Forward Incremental Forever, run it once with the other jobs disabled. It should merge the single full and a number increments to bring retention under control. Move the other backup sets back.
S3.2. Move backup sets to a new repository where more free space is available. http://www.veeam.com/kb1729
 
──────────────────────────────────────────────────────────
# of Backup Sets Present on Storage: 2 or more
# of Full Restore Points in Largest Backup Set: 2 or more
 
Troubleshooting Steps (Do the first step and retry the job, moving to the next step only in case of failure):
S4.1. Move some of the other backup sets off the storage temporarily. Set retention to value that would cause the oldest backup chain to exceed retention and automatically be removed. Run it once with the other jobs disabled. Move the other backup sets back.
S4.2. Manually delete oldest backup chain.
Note: The software will continue to think the files that were manually removed exist until those points fall outside the configured retention scope.

 

More Information

If there are .vbk, .vrb or .vib backup files in a job folder that are not listed in the backup properties, this KB does not apply. The most likely explanations are that some process was locking the file when the job tried to delete it, or that a new backup set was started without renaming the folder. These files can be moved to archival storage, or deleted.
 
──────────────────────────────────────────────────────────
Terminology
──────────────────────────────────────────────────────────
 
Backup Set = The entire set of backup files for a specific job.
Backup Chain = The chain of backup files within a set that depend on each other.

For example:

This set of 7 restore points is a backup set. A backup chain is the 4 restore points starting with the full on Sunday and ending with the increment on Wednesday.

User-added image


The Restore Point Simulator
http://rps.dewin.me/

 
How helpful is this article: 
4 out of 5 based on 29 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Request new content

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Orphus system