Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

"The operation could not be completed" when ChronoSync runs backup on APFS HDD

New Here ,
Feb 22, 2019 Feb 22, 2019

I have discovered a conflict between Adobe Bridge and ChronoSync when using backups with the "Freeze file system" APFS feature enabled. This occurs with Mac OS Mojave and ChronoSync updated to work with Mojave.

What's happening:

• Whenever the sync starts, Adobe Bridge pops up an error saying "The operation could not be completed."

Steps to repeat:

• Run any ChronoSync task with "Freeze file system enabled" while Bridge is running

• If it is disabled, then no error is generated

Thank you very much

2.0K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 22, 2019 Feb 22, 2019

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Feb 22, 2019 Feb 22, 2019

You need to either quit Bridge or not freeze the file system during backups. Most apps do not expect the hard drive to become read-only.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 22, 2019 Feb 22, 2019
LATEST

The hard drive does not become read-only with the APFS hard drive format on Mac OS.

The documentation of the feature on ChronoSync's website is as follows:

https://www.econtechnologies.com/chronosync/current.html

If using APFS as a source, the "Freeze File System" feature will take a snapshot of the file system before backing it up. The snapshot freezes all the files at the moment the sync/backup runs so there is no possibility of any files being modified, added, or removed during the course of the sync/backup. This guarantees the destination will mirror the source at the exact moment the sync/backup begins. This is even true if the computer is being used at the time the sync/backup is running.

Freezing the file system is important because macOS is constantly modifying files, even when you are not actively using them. For example, the Photos app will continuously update and modify your photo library even when you have not used the app. Without freezing, the photo library could get modified before it has been fully copied, potentially leading to a corrupt library on the destination!

It seems to me that Bridge is not interacting well or being fully respectful of the way the APFS format works within the operating system during this feature. I have taken care to disable the freeze file system option until this problem can be resolved.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines