Hi,
A question comes to my mind regarding the Behaviour of a backup session that ends in a failure because backup window is exceeded.
We seeded a First Full backup (vbk) on a low bandwidth (2-4Mb/s) site.
Job runs in Forever Inc. Mode.
We observed that during a few days the Job was running fine.
Someday a user put 100Gb of data on the Server, since then the backup fails exceeding backup window. During Week Ends backup can absorb approximately 70Gb of datas, during Week days approx 13Gb per night.
We also observed that every day, though the backup job is failing it still generate a VIB file.
In those conditions, Will veeam catch up the missing data if we keep like this or does it try to backup all the missing data from scratch as long as the job is not successful? If so, why some VIB files are generated though the backup is failed?
Trying to perform FLR, we obser the latest restore point available correspond to the latest successful backup.
Any explanation of the behaviour would be appreciated there.
Regards,
-
- Enthusiast
- Posts: 68
- Liked: 6 times
- Joined: Jul 24, 2013 7:21 pm
- Contact:
-
- Product Manager
- Posts: 14720
- Liked: 1705 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Question Regarding Low Bandwidth and Backup Windows
Hi rurouni.
What is the scope of the source items (entire computer/volume level or file level backup mode)?Job runs in Forever Inc. Mode.
The system is self-healing, so if you see the incomplete incremental restore point it should be removed by the next successful job run. Unfortunately it's not possible to use incomplete restore point as a source for data recovery. Cheers!In those conditions, Will veeam catch up the missing data if we keep like this or does it try to backup all the missing data from scratch as long as the job is not successful? If so, why some VIB files are generated though the backup is failed?
-
- Enthusiast
- Posts: 68
- Liked: 6 times
- Joined: Jul 24, 2013 7:21 pm
- Contact:
Re: Question Regarding Low Bandwidth and Backup Windows
We use bolume level backup.
What is the point then to keep unsuccessful restore points on Repository until nex successful backup if not used?
By the way how can we know how much data is missing to perform a successful backup. The stats talk about overall size, read size and transfered size but not the size of overall increment itself.
Thank you
What is the point then to keep unsuccessful restore points on Repository until nex successful backup if not used?
By the way how can we know how much data is missing to perform a successful backup. The stats talk about overall size, read size and transfered size but not the size of overall increment itself.
Thank you
-
- Product Manager
- Posts: 14720
- Liked: 1705 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Question Regarding Low Bandwidth and Backup Windows
rurouni,
Incomplete restore point means that this restore point is corrupted and data inside cannot be restored. You can get such restore point when connection was interrupted or when the backup job was shut down by reboot or shut down.
Next job run will create a new restore point with consistent and up to date data, while incomplete restore point will be erased.
Incomplete restore point means that this restore point is corrupted and data inside cannot be restored. You can get such restore point when connection was interrupted or when the backup job was shut down by reboot or shut down.
Next job run will create a new restore point with consistent and up to date data, while incomplete restore point will be erased.
Who is online
Users browsing this forum: No registered users and 30 guests