An offsite copy job failed with "Error: cannot proceed with the job: existing backup meta file '...' on repository 'Wasabi S3' is not synchronized with the DB. To resolve this, run repository rescan"
Why doesn't VBR do the rescan automatically? Why do I have to do it?
-
- Service Provider
- Posts: 27
- Liked: 8 times
- Joined: Nov 26, 2015 12:06 am
- Contact:
-
- Veeam Software
- Posts: 2838
- Liked: 650 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: "To resolve this, run repository rescan"
Hi FireExit,
The Rescan process while safe to perform will cause some temporary locks on the data in the repository while the rescan is being performed. If a job is already running, as per the note in the previous link, the rescan will "skip" such backups during that time, and vice versa with the Rescan job potentially interrupting others.
In brief, the rescan can temporarily disrupt other activities, so it's best that it be an intentional action.
The Rescan process while safe to perform will cause some temporary locks on the data in the repository while the rescan is being performed. If a job is already running, as per the note in the previous link, the rescan will "skip" such backups during that time, and vice versa with the Rescan job potentially interrupting others.
In brief, the rescan can temporarily disrupt other activities, so it's best that it be an intentional action.
David Domask | Product Management: Principal Analyst
-
- Service Provider
- Posts: 27
- Liked: 8 times
- Joined: Nov 26, 2015 12:06 am
- Contact:
Re: "To resolve this, run repository rescan"
That explains it, thank you David 

Who is online
Users browsing this forum: Bing [Bot], Google [Bot], Semrush [Bot] and 21 guests