Free Windows file sync programs? FreeFileSync, etc.

[LynniePad]

If there are several computers available, each with an installed suit of programs,

I prefer a backup program to that option. We're talking about backup vs. sync in this thread.

It seems to me that they are equivalent, certainly for the overall intended purpose.

Is it now forbidden for threads to meander wide and deep?

 

[Chris Noble]

If there are several computers available, each with an installed suit of programs,

I prefer a backup program to that option. We're talking about backup vs. sync in this thread.

It seems to me that they are equivalent, certainly for the overall intended purpose.

Only if they are kept in sync, if the purpose is for backup.

Is it now forbidden for threads to meander wide and deep?

Not at all. Having many computers is a different situation than having one, and is a worthy discussion topic. But it's not a solution to the "backup vs. sync" debate, if there is no other reason to have a second computer that is on-line and connected. Do you agree?

We have three computers in the house, and a NAS, and use Cloud storage, and they all work together for backup purposes; so an interesting topic for me; but different from the backup-vs-sync topic.

 

[Eric Carlson]

Right. I only do a 1 way sync, to my backup drives. It doesn't affect the source files.

 

[foot]

Robocopy has been around for a while, Win7 at least.

Since Windows NT 4.0 resource kit. A really long time ago. It's great for IT work, and for people who grew up using the command line, though not necessarily ideal for people not used to using a command prompt.

Yes, but some early versions were rather limited. I mentioned Win7 because it was likely the first version that many users employed. Wikipedia discusses the history.

I’d suggest that the computer skills required for command line operation are rather less than those required for wrangling LR and PS, and for the many other complex activities often recommended by our correspondents. Craig, for example, makes my head hurt. :-D

I’ve been using Robocopy for backup since 2019 with good results. There does seem to be some reluctance to use the program, but it’s ideal for my requirements.

Does Robocopy support versioning?

No, but when necessary, I keep multiple versions of a developing project in the working folder: (thesis001.docx, thesis002.docx, thesis003.docx etc.).

I use FreeFileSync which has versioning. On two critical folder hierarchies that are in constant change I set up FFS script to back them up with versioning every hour. Runs in the background and is very fast.

In addition to the quick Robocopy backup, I regularly back up the whole working folder system, without overwriting, so there’s about 2 years of versioning. Note that the working folder is only 30Gb, and there’s a separate backup system for my photo archive (which is also supplemented by a Robocopy routine).

What some correspondents don’t seem to understand is that, after the initial backup, subsequent runs only copy new or changed files by default. That, plus the implementation of multi-tasking makes for very quick backup. The first time that I used MT with SSD source and destination drives, I thought that the procedure had failed because it was done in an instant.

On two critical folder hierarchies that are in constant change

any issues when the files are changed while being sync'ed?

 

[LynniePad]

Robocopy has been around for a while, Win7 at least.

Since Windows NT 4.0 resource kit. A really long time ago. It's great for IT work, and for people who grew up using the command line, though not necessarily ideal for people not used to using a command prompt.

Yes, but some early versions were rather limited. I mentioned Win7 because it was likely the first version that many users employed. Wikipedia discusses the history.

I’d suggest that the computer skills required for command line operation are rather less than those required for wrangling LR and PS, and for the many other complex activities often recommended by our correspondents. Craig, for example, makes my head hurt. :-D

I’ve been using Robocopy for backup since 2019 with good results. There does seem to be some reluctance to use the program, but it’s ideal for my requirements.

Does Robocopy support versioning?

No, but when necessary, I keep multiple versions of a developing project in the working folder: (thesis001.docx, thesis002.docx, thesis003.docx etc.).

I use FreeFileSync which has versioning. On two critical folder hierarchies that are in constant change I set up FFS script to back them up with versioning every hour. Runs in the background and is very fast.

In addition to the quick Robocopy backup, I regularly back up the whole working folder system, without overwriting, so there’s about 2 years of versioning. Note that the working folder is only 30Gb, and there’s a separate backup system for my photo archive (which is also supplemented by a Robocopy routine).

What some correspondents don’t seem to understand is that, after the initial backup, subsequent runs only copy new or changed files by default. That, plus the implementation of multi-tasking makes for very quick backup. The first time that I used MT with SSD source and destination drives, I thought that the procedure had failed because it was done in an instant.

On two critical folder hierarchies that are in constant change

any issues when the files are changed while being sync'ed?

Maybe that’s an argument for manually initiated backup?

Some of the backup/sync options promoted in this thread are rather bizarre. I just use Robocopy, which is free.

 

[foot]

Robocopy has been around for a while, Win7 at least.

Since Windows NT 4.0 resource kit. A really long time ago. It's great for IT work, and for people who grew up using the command line, though not necessarily ideal for people not used to using a command prompt.

Yes, but some early versions were rather limited. I mentioned Win7 because it was likely the first version that many users employed. Wikipedia discusses the history.

I’d suggest that the computer skills required for command line operation are rather less than those required for wrangling LR and PS, and for the many other complex activities often recommended by our correspondents. Craig, for example, makes my head hurt. :-D

I’ve been using Robocopy for backup since 2019 with good results. There does seem to be some reluctance to use the program, but it’s ideal for my requirements.

Does Robocopy support versioning?

No, but when necessary, I keep multiple versions of a developing project in the working folder: (thesis001.docx, thesis002.docx, thesis003.docx etc.).

I use FreeFileSync which has versioning. On two critical folder hierarchies that are in constant change I set up FFS script to back them up with versioning every hour. Runs in the background and is very fast.

In addition to the quick Robocopy backup, I regularly back up the whole working folder system, without overwriting, so there’s about 2 years of versioning. Note that the working folder is only 30Gb, and there’s a separate backup system for my photo archive (which is also supplemented by a Robocopy routine).

What some correspondents don’t seem to understand is that, after the initial backup, subsequent runs only copy new or changed files by default. That, plus the implementation of multi-tasking makes for very quick backup. The first time that I used MT with SSD source and destination drives, I thought that the procedure had failed because it was done in an instant.

On two critical folder hierarchies that are in constant change

any issues when the files are changed while being sync'ed?

Maybe that’s an argument for manually initiated backup?

Some of the backup/sync options promoted in this thread are rather bizarre. I just use Robocopy, which is free.

For systems doing critical work, say a server handling online orders, it's more complicated, since losing orders/payments hurts the user confidence and cash flow

also many files with many changes have to stay in sync. You wouldn't want to miss the order yet get the payment, or get the order and miss the payment. Customer confidence would suffer

Or other cases such as a clinic handling appoitments

Surprisingly RAID isn't necessarily a good solution either. I came across an interesting video on RAID which I'll post in a seperate thread

I'm not doing anything like that, so I manually do the backup/archive, which I do several times a day, and always after I make important code changes

I'm using Robocopy for the master backup, and zpaq for the versioning/journaling archive

 

[LynniePad]

Robocopy has been around for a while, Win7 at least.

Since Windows NT 4.0 resource kit. A really long time ago. It's great for IT work, and for people who grew up using the command line, though not necessarily ideal for people not used to using a command prompt.

Yes, but some early versions were rather limited. I mentioned Win7 because it was likely the first version that many users employed. Wikipedia discusses the history.

I’d suggest that the computer skills required for command line operation are rather less than those required for wrangling LR and PS, and for the many other complex activities often recommended by our correspondents. Craig, for example, makes my head hurt. :-D

I’ve been using Robocopy for backup since 2019 with good results. There does seem to be some reluctance to use the program, but it’s ideal for my requirements.

Does Robocopy support versioning?

No, but when necessary, I keep multiple versions of a developing project in the working folder: (thesis001.docx, thesis002.docx, thesis003.docx etc.).

I use FreeFileSync which has versioning. On two critical folder hierarchies that are in constant change I set up FFS script to back them up with versioning every hour. Runs in the background and is very fast.

In addition to the quick Robocopy backup, I regularly back up the whole working folder system, without overwriting, so there’s about 2 years of versioning. Note that the working folder is only 30Gb, and there’s a separate backup system for my photo archive (which is also supplemented by a Robocopy routine).

What some correspondents don’t seem to understand is that, after the initial backup, subsequent runs only copy new or changed files by default. That, plus the implementation of multi-tasking makes for very quick backup. The first time that I used MT with SSD source and destination drives, I thought that the procedure had failed because it was done in an instant.

On two critical folder hierarchies that are in constant change

any issues when the files are changed while being sync'ed?

Maybe that’s an argument for manually initiated backup?

Some of the backup/sync options promoted in this thread are rather bizarre. I just use Robocopy, which is free.

For systems doing critical work, say a server handling online orders, it's more complicated, since losing orders/payments hurts the user confidence and cash flow

also many files with many changes have to stay in sync. You wouldn't want to miss the order yet get the payment, or get the order and miss the payment. Customer confidence would suffer.

No online server in our office, just some rather critical word processing needs, where Robocopy is absolutely ideal for quick and secure backup. We regularly produce (or edit) 400 page technical monographs with many supporting sections. Losing any of this stuff is not an option.

Typically, a full day’s work can be saved (added to the backup copy) in less than a second, and this is supported by periodic full backups to external HDDs.

 

[PHXAZCRAIG]

It's super simple to set up and use versioning. If you can use backup and restore, you can use versioning without much thought or effort at all.

OK; let's say I want to roll back my entire system to the state it was in on Sept 1, except for my data files that I want to roll back to the state they were in on Sept 25th, without affecting the newly created data files since Sept 25th. What is the super simple sequence of mouse clicks to do that with FreeFileSync?

This would be the situation if there is some corruption in the OS that exhibited itself between Sept 1 and Sept 25th, but has not affected the data files.

Sync is not for the OS, just for data. Use file backup and/or image backup for the OS and apps. Obviously. Or just reinstall.

Super simple to use backup for both OS and data. Then no additional need for sync.

Sure, simple. But. How much space is needed for the backups?

No big deal if I lose my OS or apps. I'll just switch to another computer. And I have my sync'd data, so it's all good.

Super simple to avoid having to get another computer and reinstall and reconfigure all your apps -- by just having a backup. Sounds even more super than your super, doesn't it?

If you are talking about a complete backup, the restore is simple. But if you are not simply duplicating an entire PC multiple times, then you have to factor in a differential backup or your backup space requirements are to the moon.

It gets less simple when you don't have 25 times the amount of disk space of your pc in your backup.

I do like versioning, in general, but I associate it with more sophisticated and expensive backup software.

 

[Chris Noble]

It's super simple to set up and use versioning. If you can use backup and restore, you can use versioning without much thought or effort at all.

OK; let's say I want to roll back my entire system to the state it was in on Sept 1, except for my data files that I want to roll back to the state they were in on Sept 25th, without affecting the newly created data files since Sept 25th. What is the super simple sequence of mouse clicks to do that with FreeFileSync?

This would be the situation if there is some corruption in the OS that exhibited itself between Sept 1 and Sept 25th, but has not affected the data files.

Sync is not for the OS, just for data. Use file backup and/or image backup for the OS and apps. Obviously. Or just reinstall.

Super simple to use backup for both OS and data. Then no additional need for sync.

Sure, simple. But. How much space is needed for the backups?

No big deal if I lose my OS or apps. I'll just switch to another computer. And I have my sync'd data, so it's all good.

Super simple to avoid having to get another computer and reinstall and reconfigure all your apps -- by just having a backup. Sounds even more super than your super, doesn't it?

If you are talking about a complete backup, the restore is simple. But if you are not simply duplicating an entire PC multiple times, then you have to factor in a differential backup or your backup space requirements are to the moon.

It gets less simple when you don't have 25 times the amount of disk space of your pc in your backup.

I do like versioning, in general, but I associate it with more sophisticated and expensive backup software.

I do a Full backup monthly, Differential weekly, Incremental nightly. I keep the last 3 of each. All automated of course (Macrium). Super simple and cheap.

 

[foot]

Robocopy has been around for a while, Win7 at least.

Since Windows NT 4.0 resource kit. A really long time ago. It's great for IT work, and for people who grew up using the command line, though not necessarily ideal for people not used to using a command prompt.

Yes, but some early versions were rather limited. I mentioned Win7 because it was likely the first version that many users employed. Wikipedia discusses the history.

I’d suggest that the computer skills required for command line operation are rather less than those required for wrangling LR and PS, and for the many other complex activities often recommended by our correspondents. Craig, for example, makes my head hurt. :-D

I’ve been using Robocopy for backup since 2019 with good results. There does seem to be some reluctance to use the program, but it’s ideal for my requirements.

Does Robocopy support versioning?

No, but when necessary, I keep multiple versions of a developing project in the working folder: (thesis001.docx, thesis002.docx, thesis003.docx etc.).

I use FreeFileSync which has versioning. On two critical folder hierarchies that are in constant change I set up FFS script to back them up with versioning every hour. Runs in the background and is very fast.

In addition to the quick Robocopy backup, I regularly back up the whole working folder system, without overwriting, so there’s about 2 years of versioning. Note that the working folder is only 30Gb, and there’s a separate backup system for my photo archive (which is also supplemented by a Robocopy routine).

What some correspondents don’t seem to understand is that, after the initial backup, subsequent runs only copy new or changed files by default. That, plus the implementation of multi-tasking makes for very quick backup. The first time that I used MT with SSD source and destination drives, I thought that the procedure had failed because it was done in an instant.

On two critical folder hierarchies that are in constant change

any issues when the files are changed while being sync'ed?

Maybe that’s an argument for manually initiated backup?

Some of the backup/sync options promoted in this thread are rather bizarre. I just use Robocopy, which is free.

For systems doing critical work, say a server handling online orders, it's more complicated, since losing orders/payments hurts the user confidence and cash flow

also many files with many changes have to stay in sync. You wouldn't want to miss the order yet get the payment, or get the order and miss the payment. Customer confidence would suffer.

No online server in our office, just some rather critical word processing needs, where Robocopy is absolutely ideal for quick and secure backup. We regularly produce (or edit) 400 page technical monographs with many supporting sections. Losing any of this stuff is not an option.

Typically, a full day’s work can be saved (added to the backup copy) in less than a second, and this is supported by periodic full backups to external HDDs.

sure, for backups. But backups don't cover all situations

if the data file somehow gets corrupted, or loses it's data, then the process is only backing up bad data.

I've had this happen to me, more than once. It could be due to some strange bug in the program (I'm looking at you, notepad++) or operator error (and now I'm looking at me...*sigh*)

versioning is the way to go

 

[LISABenjamin]

Try Duplicati

 

[LISABenjamin]

Several software options are suitable for performing a mass copy of 1.81 TB from a 2 TB external SSD to a 4 TB external SSD with emphasis on both performance and data integrity. Here are some popular choices:

-FreeFileSync

-Gs Richcopy360

-Goodsync

-Teracopy

-EaseUS Todo Backup

Additional considerations:

• Drive connection: Use a high-speed connection like USB 3.0 or Thunderbolt for optimal performance.
• File system: Ensure both drives use the same file system (e.g., NTFS for Windows, HFS+ for Mac) to avoid compatibility issues.
• Partition alignment: Align partitions on both drives for improved performance on some hardware configurations.
• Error handling: Choose software with error handling and retry mechanisms to handle potential transfer issues.

hope this helps

 

[Jon555]

I'm interested in a free, simple and reliable Windows program to back up files on a local hard drive to an external drive. Ideally, I would enter a source (local) and target (external) directory, click Go and the program would determine which files were different and copy the source files to the external drive.

A recent thread mentioned the FreeFileSync program:

https://www.dpreview.com/forums/thread/4672217

I did some web searching and found few mentions of it or recent reviews. Many articles on the best sync software don't mention it and many of the reviews I found were very old.

I'm interested in hearing any feedback on FreeFileSync and other free alternatives.

On the one hand I'd recommend Syncback Free:

Download SyncBackFree - Free Backup Software for Windows

Official download page for SyncBackFree. Get the latest version of our powerful, 100% free backup software for Windows 11, 10, 8, 7, and Vista. Download now!

www.2brightsparks.com

But on the other hand I'd just say pay a few quid for the SE version...