-
- Enthusiast
- Posts: 26
- Liked: 1 time
- Joined: Dec 28, 2014 11:29 am
- Contact:
Disadvantages of new version 2.0.0.700
HI. I have some replies about noticed unexpected behaviour.
1) I have backup starting at 3am. It takes 3 hours. I have checked option "when backup target is connected" and there is set default period "2 hours". Backup finished at 6:03am and I 45 minutes later I made restart. Suddanly - at 6:50 - it started again to make backup !!! Why, if only 50 minutes left from ending last backup ???
So please change it this period should be counted from the ending, not beginning of backup.
2) Still when clicked STOP making backup - wee need to wait so, so, so long to really stop... As usual long
1) I have backup starting at 3am. It takes 3 hours. I have checked option "when backup target is connected" and there is set default period "2 hours". Backup finished at 6:03am and I 45 minutes later I made restart. Suddanly - at 6:50 - it started again to make backup !!! Why, if only 50 minutes left from ending last backup ???
So please change it this period should be counted from the ending, not beginning of backup.
2) Still when clicked STOP making backup - wee need to wait so, so, so long to really stop... As usual long
-
- Veteran
- Posts: 471
- Liked: 59 times
- Joined: Dec 14, 2015 9:42 pm
- Contact:
Re: Disadvantages of new version 2.0.0.700
I have seen this as well. At the time when the backup finishes it then says "last backup x minutes / hours ago", taking the start time not the end time.CharlieKPoland wrote:1) I have backup starting at 3am. It takes 3 hours. I have checked option "when backup target is connected" and there is set default period "2 hours". Backup finished at 6:03am and I 45 minutes later I made restart. Suddanly - at 6:50 - it started again to make backup !!! Why, if only 50 minutes left from ending last backup ???
So please change it this period should be counted from the ending, not beginning of backup.
I can see why it is done, because for long backups doing several hundred gigabytes this becomes somewhat helpful as the data at the beginning of the backup literally hasn't been backed up since the start time.
I would change the default period. I myself will often change it to 18 hours.
-
- Product Manager
- Posts: 5796
- Liked: 1215 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Disadvantages of new version 2.0.0.700
In regards to 2, if you click stop we have to make sure everything is back to a normal state so we can't just force stop it. If you think it can be faster on the specific machine please contact support for assistance.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Influencer
- Posts: 17
- Liked: 4 times
- Joined: Mar 01, 2016 1:49 pm
- Contact:
Re: Disadvantages of new version 2.0.0.700
I would think that taking the start time is corect cause VSS will frezze the system pretty close to the start time and all changes being made after this freeze are not in the backup and therefor it should be correct or logical for me.
-
- Product Manager
- Posts: 14715
- Liked: 1702 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Disadvantages of new version 2.0.0.700
The 'Back up no more often than' option applies to backup events only and does not track the scheduled backup time.Veeam Help Center wrote:The Back up no more often than every <N> <time units> option is applied only to job sessions started at specific events. Daily backups are performed according to defined schedule regardless of the time interval specified for this setting.
Correct.SS will frezze the system pretty close to the start time and all changes being made after this freeze are not in the backup
Who is online
Users browsing this forum: No registered users and 45 guests