Karen's Replicator, 'failed Copies' ?

.
Backing up (most) files with Karen's Replicator (I know its old, but imho it is still very helpful) and for some 'Jobs' get a few thousand 'Failed Copies:' explained by the following note with each of those files all in the log list...

Files are not 'in use'.
Any way to unlock ?
Other ?
Thoughts ?

 

Try using a sync program instead - I use SyncBackFree.

 

I still use Karen's Replicator and still rely on it as my primary file backup program. I began
using SyncBackFree also about 7 months ago, because it has a Restore feature which Replicator does
not. It did take some time to learn how to use the software.

You should check the destination for some of those failed copies for anything unusual.
Try moving one of the destination folders to another location for safe keeping and then delete the destination folder.
Replicator should create a new folder the next time you run that job.
If the job then runs properly, you can repeat the process on the other troublesome destination folders.

If the destination is a Hard drive, I suggest also that you first run a disk error check from
Windows Explorer > right click on drive > drive properties > Tools > Error checking.
Make sure Automatically fix file system errors is checked.

 

The problem may be the Source for the job.
If the source location no longer exists, that will generate errors. Same applies to file Filters.
Do a job edit. Use the Browse button next to the source and navigate to the source location to be sure that it is correct.
If you use a file filter, make sure that such files do exist at the source.

 

Thank you for the reply and suggestion.
Tried 'chkdsk' on the external 'backup' hd, it ran for almost 24hrs, and did not help.
Actually it appears the source file names may be 'too long' for KR.
Does that make sense ?
Does SBF have the same problem with file names, and is the backup 'compressed', or can it just duplicate ?

 

SyncBackFree always keeps all files in their native format, there is no compression or conversion, and it has no issues with long filenames. There are though a surprising number of options that have to be given some thought when creating a backup profile, such as what to do when synchronising if a file is in the backup folder but not in the folder being backed up. I suspect it was considerations like this that caused the comment about it not being easy to learn.

 

chkdsk running for 24 hours is extremely unusual. I would suspect something is wrong with the drive or file system. If there is something wrong with the drive, then using a different backup program will not help.

Karen's Replicator is a very well designed and reliable program. I do not think the problem is with the backup program itself.

Did you try moving the destination files of one problem job, then deleting that destination folder and running that problem job?

Why do you think the filenames are too long? If those jobs had been running properly at some time previously, then long paths and or filenames would not suddenly become a problem. That doesn't sound right to me.

SyncBack Free has the option to compress files using the industry standard ZIP format. By default, each file is compressed into it's own separate zip file. There is an option to compress all files together into one zip file.

To create a job in SyncBack Free, you have to choose either Backup, Mirror or Synchronize as a job type. All of the terms are described in the program HELP. SyncBack Free has only Basic synchronization. More advanced types are only in the paid versions. As Earthling mentioned, there are a lot of options that should be examined to make sure the job will do what you want and what you Expect it to do. Everything is explained in the HELP, but does take some study.

I like having both backups. I always run Karen's but maybe not SyncBack so I'll have some older copies.

 

Just realized that you are copying to an external, supposedly USB, hard drive.

Try this:
Open Windows Explorer
Right click on the external drive and choose Eject. When the prompt says it's OK to disconnect, disconnect the drive from the USB port.

Close down your programs and Restart Windows. When the reboot has finished, reconnect the drive, check Windows Explorer to see that the drive is accessible, then try Karen's Replicator again.

If you still get the same errors, I think that either some other process is using/locking the files or there is something wrong with the drive or file system.

Hope this helps.

 

Thanks for the followup/info !
Do you not think the length of the filename could be the problem with KR ?

Btw, lot of SyncBackFree reviews at http://download.cnet.com/SyncBackFree/3000-2242_4-10413802.html#review, and most are good.
One mentioned...
"After an initial backup: If you change a notepad file in the SOURCE, it will not allow a back-up to the DESTINATION. It will flag it as a 'COLLISION' and leave out the updated text file. I can not see a way around this glitch."
Any idea if SB could backup to same backup folders/files started with KR, and/or if they could both be use on the same folders/files on an external backup HD ?
Seems like it could be possible if files are not compressed etc ?

 

The review excerpt that you mentioned is most likely the result of a misunderstanding on the part of the user. I think you can disregard it. The term 'collision' does not mean failure in Syncback. Syncback is a solid program. It is very flexible and powerful, but more complex than Replicator.

We can't do two things at once. Stick to finding the problem with Replicator. I think ultimately the problem can be resolved, if not by me, than by someone else.
I do not think the problem is the Replicator program.
I do not think the filename length is a problem.

Maximum filename length in NTFS (Windows XP and Windows Vista)?

Post an example filename with the full path included so we have something to judge by.

Is the backup drive a USB drive? How did the Eject, disconnect, reboot, reconnect work out?

 

Thanks for the followup !
Per your questions:

1. Example of filename...
Copy Failure: Could not Open Destination File (File Possibly In Use/Locked): I:\H.PTReplicator\D5721-XParchiveKReplicatorHD#1-150714\xxx\Desktop\BASICS\A-Z\V\Vistro200\Vistro200-Desktop-130806\HOLD\xxx-OhToSea-130301\Hotwire- Airline Tickets, Hotel Reservations, Car Rentals - Discount Travel Deals, Last-Minute Travel Too!-CancelCarRental-130505.TIF

2. 'Eject, disconnect, reboot, reconnect' did not help.

3. Previous question, just in case need to switch...
Any idea if SB could backup to same backup folders/files started with KR ?
Seems like it could be possible if files are not compressed etc ?

 

I used http://www.charactercountonline.com/ and the filename you posted is 273 characters long which is too long for NTFS so the problem has nothing to do with Karen's.
You need to shorten the path to fix it!

 

Wow! I have never seen a path like that. That's way beyond what I expected.

The maximum path/filename combination in Windows is 259 characters or less.
That can not be changed.
Naming Windows Files - Restrictions and Limitations

Since the utility posted by davismccarn shows a length of 273 characters, it is too long and will generate an error.
Using a different backup program will not help. You need a shorter path.

 

.
Thank you all much for the replies/info !!!
Not sure how such long file names got into the system, but good to know KR is not the problem.

Side question, in case need to switch...
Any idea if SyncBackFree could backup to same backup folders/files started with KR (not compressed etc) ?

 

Whoever came up with your folder naming scheme didn't anticipate an issue with long filenames!
"I:\H.PTReplicator\D5721-XParchiveKReplicatorHD#1-150714\xxx\Desktop\BASICS\A-Z\V\Vistro200\Vistro200-Desktop-130806" is the path to the backup folder(s) which is a big part of the problem!

Sure, there are utilities (maybe SyncBack) that would plow right on; but, you wouldn't be able to restore them (been there, done that). How about I:\Backups\Vostro200-130806\ instead?

 

Yes it could, but I can't guarantee it will recognise the files created by KR as I can't test it myself.

 

With an hour to spare I installed Karen's Replicator in my XPVM and ran a backup of a selected shared folder on the host Win 10 system. I then installed SyncBack Free in the XPVM and ran an identical backup. It reported no changes so it was recognising the files created by Karen's. I also tested adding files to the source folder and running Karen's again and the new files were added to the backup in the XPVM. I then deleted those files from the source folder and restored them from the Karen's backup. Everything worked perfectly so you can safely switch to SyncBack Free if you want.