Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
How long should a full backup take? Incremental? Big time difference in recreated tsk
#1
I had a backup job running for over a year that consistently took 3 hours for the full, and 3 hours for the incremental.

I had to delete and recreate the job (I took screenshots of all settings) and made the job the same. 

Now the full took 1 hour, and incremental takes 5 min. 

Why would there be such a major difference all of a sudden??
Reply
#2
No idea why your 3H Full and 3H incremental was taking 3H for the incremental. That makes no sense and it looks like another Full was getting executed.
Your 1H Full and 5 min incremental makes more sense if the incremental was done before any major changes were made.

The 3H vs 1H for the Full is strange - are you using the exact, and I do mean exact, hardware setup including USB/Ports/cables, etc?

I think Hasleo's logs are pretty primitive and not much help but have a look to compare the old vs new setup.
Reply
#3
(4 hours ago)CDC9762 Wrote: No idea why your 3H Full and 3H incremental was taking 3H for the incremental. That makes no sense and it looks like another Full was getting executed.
Your 1H Full and 5 min incremental makes more sense if the incremental was done before any major changes were made.

The 3H vs 1H for the Full is strange - are you using the exact, and I do mean exact, hardware setup including USB/Ports/cables, etc?

I think Hasleo's logs are pretty primitive and not much help but have a look to compare the old vs new setup.

Yes, everything is exact. Same drive, cables, and settings. I'm just worried that if I ever go to do a restore it will fail.
Reply
#4
Hi,

also, in older HBS versions the compression level was set to medium, now the default is low. Maybe that could've made a difference in the performance as medium uses up more CPU. But you said you made screenshots of all settings which doesn't add up to that theory then.

So maybe there was some kind of error in an older HBS version that caused this issue in the job, maybe a timeout of some kind that made the job freeze for a long time. And this problem was then carried over to the more recent versions as the job was reused for that long.

Maybe @admin has an idea what could've gone wrong with the old job. Log files might still be helpful for this analysis, please keep them for now.
Reply
#5
There are so many factors involved that are essential to making an evaluation.

1. What is the spec of the PC being used
2. What is being backed up, what is the size, and what type of drive
3. What is the target for the backup, SSD, HDD, etc
4, How it the PC connected to the target, internal drive, ethernet, wifi, and what speeds
5. What is the size of the full backup, and the incremental backup
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)