|
|
Any backup software that creates a large file that can only be opened by said software is a non-starter in my book.
|
|
|
|
|
"There can only be one!" 
I'm afraid that's the way most backup programs work ...
|
|
|
|
|
...and that's why I don't use any of 'em.
|
|
|
|
|
1. perhaps there is an error. Default in Robocopy:
/R:n :: number of Retries on failed copies: default 1 million.
/W:n :: Wait time between retries: default is 30 seconds.
Try /R:zero (use 0, it gave me a happy face)
maybe you tried this already?
2. File or directory size greater than 4GB?
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
My script invokes Robocopy with
/MIR /R:0
My backup set includes files that are tens of GBs in size, and I haven't seen any problem with those. I suppose I shouldn't have said that it only happens with large files, but rather, that I haven't seen it happen with small files.
|
|
|
|
|
The solution kinda makes me wonder if it's a memory fault, rather than a disk / usb problem.
What happens if you try copying a large file repeatedly onto the same disk? A quick Powershell - logging each time it completed each copy so you can see any slowdown - and leave it running overnight?
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: The solution kinda makes me wonder if it's a memory fault, rather than a disk / usb problem.
Even if--for a given file--it either doesn't happen at all, or always happens at the same place, even after many reboots? :-/
OriginalGriff wrote: What happens if you try copying a large file repeatedly onto the same disk? A quick Powershell - logging each time it completed each copy so you can see any slowdown - and leave it running overnight?
I'm tempted to run sdelete from SysInternals and have it fill all free space to see what happens. But that's a good idea as well. I'll follow up if I go ahead with it.
|
|
|
|
|
Have you looked in the Event Log for any hardware errors. Does sound to me like it's the USB in your computer.
|
|
|
|
|
Rather thoroughly, yeah. I can see the events complaining about the unexpected reboots (of my own creation), but nothing about hardware faults, unfortunately.
|
|
|
|
|
I use EaseUs Todo Backup. It puts the files in a ".pdb" blob that can be opened by Windows Explorer. You don't need the backup s/w to open it and extract files.
|
|
|
|
|
matblue25 wrote: I use EaseUs Todo Backup. It puts the files in a ".pdb" blob that can be opened by Windows Explorer.
Really? Windows Explorer natively understands these BLOBs created by a third-party program, so a machine that's never had it installed on it before will understand these file types? I find that dubious, because I just created an empty .pdb file, and Explorer showed a generic icon and set the type to "PDB file", which tells me it's an unregistered file type and Windows wouldn't know what to do with it.
|
|
|
|
|
You're right. If I double click on a pdb file (created by EaseUs) on a computer that has EaseUs installed on it, it opens in Windows Explorer. But if I try it on another computer that doesn't have EaseUs installed, it won't open it. It really is Explorer opening the file, not the EaseUs app. I looked in the registry for what kind of magic it could be doing to make that happen but didn't see how it's done. Whatever it is, it's not the standard HKEY_CLASSES_ROOT\.pdf registry key. Must be some kind of extension added to Explorer. Sorry if I got your hopes up.
|
|
|
|
|
matblue25 wrote: Must be some kind of extension added to Explorer. Sorry if I got your hopes up.
Of course it's an extension. And no, I didn't have one iota of "hope" this would even be possible without said third-party software.
I still prefer having a plain copy of the individual files--nothing will change that. That way, anything that can read NTFS will be able to read my backup. One less thing that can go wrong, really. Just how resilient is EaseUs to corruption in its own files?
|
|
|
|
|
I haven’t had any problems with it yet. My wife is constantly losing files and I’ve been able to recover them all so far. Just had to reload my C: drive from backup because it wouldn’t boot (after several attempts to fix it). It restored and booted right away. Just one issue minor issue with Windows that I had to fix after the restore, which I can’t blame on EaseUs.
|
|
|
|
|
I would get a new sourcedrive immediately. It has bad sectors.
Unless it's an SSD of course.
|
|
|
|
|
What do you make of the part where, if I copy from that same source drive across my LAN instead of locally, there's no error or even any sort of slowdown whatsoever?
If the source drive had bad sectors, then I don't see how copying across the LAN would change anything.
|
|
|
|
|
I missed the part where it works over the LAN. You can disregard my post completely.
But have you checked how deep your directory structure is?
The length of the path might be up to 32k characters long in NTFS, but the Explorer doesn't support more than 260, and if you do it over the LAN the path is often shorter
|
|
|
|
|
|
Large file, takes a long time, but copying doesn't really count as "activity" so...
Is your computer shutting down USB ports when it deems them inactive?
|
|
|
|
|
I can copy much larger files without any issue.
Besides...any data that's still passing through the bus ought to count as activity.
|
|
|
|
|
You expect the computer to make sense? You funny. 
|
|
|
|
|
where's python discussion / forum in this web?
|
|
|
|
|
There is no specific Python forum at the moment. You can use Quick Answers[^] instead.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
