Disk Image
Apr 6, 2024 13:14:33 #
bobbyjohn wrote:
Jerry, if you are also using McAfee as your anti-v... (show quote)
Thanks. Since EaseUS worked, I'm sticking with that.
Apr 7, 2024 08:21:04 #
popheizz
Loc: berks co., pennsylvania
jerryc41 wrote:
I don' t know. I wanted an image. I'm going to stop and cancel. It's up to 14 hours now.
The way I read the scr grab it’s copying over 1800 GB not 170.
Apr 8, 2024 00:41:13 #
jerryc41 wrote:
I don't understand. I'm using Macrium Reflect to make a disk image of C. It's going to take ten more hours. The C drive contains about 170GB of data. If I copied all the files from C to Q, it wouldn't take that long (I don't think). What's going on?
A track for track image does take a LONG time, especially if one disk is an external connected via a slow USB port. Acronis is no better (tried them both), maybe even slower form my experience.
Apr 8, 2024 05:33:34 #
chrissybabe
Loc: New Zealand
Not enough information. The backup looks to be 1.8TB which is a ton of data. This would probably result in a bit less real space. First up is the drive being backed up to an SSD or HDD ? And is this the first time the backup has been created ? Or is this another attempt ? And is the drive being backed up to an SMR type drive ? Because what you are seeing is an example of what will happen if you try and overwrite a previous created image with ANY backup program. And is a direct result of SMR type writing. I have seen this multiple times until I replaced my HDDs with none SMR type recording. A backup that should have taken maybe a few hours max was taking days. To partially quote from an answer provided elsewhere (sorry about that) -
" The penalty for SMR is when writing, and only when you write enough data. If you only write a few gigabytes occasionally you will probably not even notice, but if you write 100s of gigabytes at a time, your write speed will absolutely tank. SMR doesn't affect read speeds or seek times. So as long as you use it in a more or less "write once, read many times" fashion it's perfectly fine." An image backup writes 100's of gigabytes and you are doing this. Problem is even worse if you are overwriting a previous file.
" The penalty for SMR is when writing, and only when you write enough data. If you only write a few gigabytes occasionally you will probably not even notice, but if you write 100s of gigabytes at a time, your write speed will absolutely tank. SMR doesn't affect read speeds or seek times. So as long as you use it in a more or less "write once, read many times" fashion it's perfectly fine." An image backup writes 100's of gigabytes and you are doing this. Problem is even worse if you are overwriting a previous file.
If you want to reply, then register here. Registration is free and your account is created instantly, so you can post right away.