Hi guys,
Our main backup drive started to get bit errors and VeeamB&R kept saying the VIB files were corrupt so we have replaced the drive, renamed the new drive to the old drive letter and name, but VeeamB&R wants the previous files, which no longer exists.
Unfortunately our Hyper-V host doesn't do backups well during the day due to the load, it results in the servers getting too slow and the staff can't do their work, so we can only run backups after hours in a narrow window due to branches in different time zones, when none of the IT staff are around.
How can I tell VeeamB&R to run a Full Backup and ignore the previous versions of Backups that were there? I keep getting the below error for all of the VMs in the backup job:
19/10/2020 7:47:04 p.m. :: Processing SERVER Error: File does not exist. File: [Backup SERVER to FD2020-10-15T190040_C7E7.vib].
Failed to open storage for read access. Storage: [Backup SERVER to FD2020-10-15T190040_C7E7.vib].
Basically I want to run an "Active Full", but on the usual backup schedule. I figure I need to clean the database of that backup job's previous run history?
-
- Veteran
- Posts: 472
- Liked: 59 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Drive died, how to run Full Backup when on a schedule?
If you have a scale-out backup repository, there's an option to create new full backup when the previous backups are not available.
If you have a regular repository, then enabling the rotated drives option temporarily should do the trick. This makes the job not to worry about missing backup files, as this is perfectly normal for a repository backed by rotated drives, and just create a new active full.
And worst case, remember you could always use a Windows Task Scheduler to schedule an Active Full backup to start at any time you like!
If you have a regular repository, then enabling the rotated drives option temporarily should do the trick. This makes the job not to worry about missing backup files, as this is perfectly normal for a repository backed by rotated drives, and just create a new active full.
And worst case, remember you could always use a Windows Task Scheduler to schedule an Active Full backup to start at any time you like!
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Drive died, how to run Full Backup when on a schedule?
Just a couple of ideas: this option might be a way to go or you can also remove records about the whole backup from database but in this case previous restore points will not be available unless you import the backup.AlexLeadingEdge wrote:I figure I need to clean the database of that backup job's previous run history?
Thanks!
-
- Veteran
- Posts: 472
- Liked: 59 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: Drive died, how to run Full Backup when on a schedule?
Oh dear, I forgot to hit Submit on my last message...
I logged into the backup server at some ungodly hour of the night and started an Active Full backup.
We have had a look at a scale-out backup repository and it could be of interest. We're wondering what happens when a drive dies, is the Full Backup on multiple drives?
I logged into the backup server at some ungodly hour of the night and started an Active Full backup.
We have had a look at a scale-out backup repository and it could be of interest. We're wondering what happens when a drive dies, is the Full Backup on multiple drives?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Drive died, how to run Full Backup when on a schedule?
No, each file is stored on a single extent.
Who is online
Users browsing this forum: Semrush [Bot] and 47 guests