Version 7 Very Long Incremental Image Processing


Author
Message
lagunasrfr
lagunasrfr
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 28, Visits: 102
Am on latest Home Edition 7.0.2079 running on Windows 10 64 with all updates current. Incremental update in V6 used to be about 20 minutes or less. Well over an hour in version 7. Am creating image on 5 TB Seagate Expansion from Toshiba L75D-A with 750 GB local drive with about 250 GB of data.
Edited 16 March 2017 5:31 PM by lagunasrfr
Nick
Nick
Macrium Representative
Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)
Group: Administrators
Posts: 2.1K, Visits: 13K
Hi 

Thanks for posting. Sorry you are having problems. 

The updates in v7.0.2079 ensures that exactly the same code execution is used as v6 so we need to check that things are OK in the write path to your backup drive.  Please try temporarily disabling AV or adding the backup folder and/or the Reflect application to your AV exclusions. This will isolate AV as the problem.  Also try toggling the 'Direct disk IO' option in the defaults as described here: http://knowledgebase.macrium.com/display/KNOW7/Macrum+Reflect+v7.0+Update+16th+Mar+2017


Kind Regards

Nick - Macrium Support

Next Webinar


lagunasrfr
lagunasrfr
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 28, Visits: 102
Direct disk I/O toggle seems to have done the trick. Ran incremental and full after toggling and times returned to those under V6. One other thing about V7: Your update changes to V7 take a very long time and have required reboot due to driver change.  Do you intend to always perform updates with complete update or will you revert back to just changing certain modules as you did in V6?

Thank you Nick.
Nick
Nick
Macrium Representative
Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)
Group: Administrators
Posts: 2.1K, Visits: 13K
Great, glad it's sorted.  Can you confirm that you 'un-checked' the 'Disable Direct I/O..' option?

Do you intend to always perform updates with complete update or will you revert back to just changing certain modules as you did in V6?


We will be delivering new v7 updates using the more efficient binary patching method shortly. 

Kind Regards

Nick - Macrium Support

Next Webinar


lagunasrfr
lagunasrfr
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 28, Visits: 102
Did uncheck Disable Direct I/O box.
lagunasrfr
lagunasrfr
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 28, Visits: 102
What did you mean by AV Nick?
Drac144
Drac144
Expert
Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)
Group: Forum Members
Posts: 587, Visits: 2.3K
AV=Antivirus software.

lagunasrfr
lagunasrfr
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 28, Visits: 102
duh. Was thinking audio visual.
lagunasrfr
lagunasrfr
New Member
New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)New Member (38 reputation)
Group: Forum Members
Posts: 28, Visits: 102
Now on v7.0.2134 (UEFI) and am getting very slow incremental processing. Transfer rates vary from 12 to 800 Mb. Transfer rate will start out slow , maybe 200Mb, then climb to maybe 650Mb. Then they will fall to less than 100 and even to low double digits. Then rate will climb again and then fall again, etc.  Have had incrementals run as long as 3 hours where they would usually run in 5 to 15 minutes. Full backups run about the same length as prior version (about 1 hr 15 minutes for an image of 220 gig active bytes on a 750 g C:drive on my laptop.
Tried all of your earlier suggestions and thought everything was ok, but now am finding inconsistent run times for incremental. Advanced incremental options are both unchecked. My Win 10 Disk policies are is enable write caching on the target external drive.
Have included log files for latest incremental backup where filesize added to backup set was 6 gig and took 39 minutes. .

Thanks for your help Nick.

Attachments
Macrium Reflect Log.pdf (4 views, 74.00 KB)
Edited 16 April 2017 11:50 PM by lagunasrfr
Nick
Nick
Macrium Representative
Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)Macrium Representative (3.6K reputation)
Group: Administrators
Posts: 2.1K, Visits: 13K
Hi 

Thanks for getting back. 

Incremental images will often have an inconsistent transfer rate. This is caused by two factors:

1. The data included in the Incremental may well be scattered across the File System. Unlike a Full image, which reads sequentially across the File system, an Incremental may cause the source disk to Seek  during the Incremental. If you are imaging a drive that is in use by Windows (such as C) then these Seeks will slow down the image process. 

2. Large files that have at least 1 cluster changed will cause the entire file to be read to determine which clusters have actually changed in the Incremental.  So, for example, a multi-GB VHD file with only a small change will incur the penalty of reading the whole file to determine which clusters to actually backup up. This time penalty is mitigated when using Changed Block tracking. http://knowledgebase.macrium.com/display/KNOW7/Macrium+Changed+Block+Tracker

Kind Regards

Nick - Macrium Support

Next Webinar


GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search