Family File in the cloud syncing issue?

[Miss Myrtle]

I currently have my Reunion folder in my documents, which syncs to iCloud, but I also have it set so all my files are stored locally. My question is, every time I add information, it appears to sync the entire database, not just update the one item. That isn't a big deal right now as my folder is only about 100 megabytes. But when it reaches into the gigabytes, that's going to be ridiculous.

I'm considering moving it offline and into my user folder on my Mac. I'm not overly concerned about syncing to the app. Thoughts?

[DrJJWMac]

I've taken an approach to limit iCloud storage solely to those cases that require that I sync the content between my desktop system and my iPhone/iPad. I also do not view iCloud as a backup resource. Specifically, in System Settings, I have set iCloud Drive to Sync this Mac but I do not sync Desktop & Documents Folders and do not Optimize Mac Storage.

If you want your Reunion folder to be a local-only copy but you want to have the Desktop & Documents Folder and Optimize Mac Storage turned on, you may want to consider a focused approach to set where you store your databases and resources. Create a new volume on your local drive (for example call it Genealogy). Give the volume the space that you think you might need for all of your files.

By example, I have four volumes on my Mac -- the main one, one called Databases, one called Repositories, and one called Archives. I store various database-related content (from Devonthink, bibliography, and other "database-type" apps) in Databases, I store reference content in Repositories, and I store content that is to be moved to external archives on Archives.

Besides keeping the content out of iCloud, an approach with separate storage volumes allows me to have finer controls on Time Machine backups. By example, the Archives volume is naturally never included in Time Machine backups.

[Gregg]

As you pointed out: If your family file is in an iCloud Drive or Dropbox folder, changes are uploaded to the cloud as files are modified.

If you have an iCloud Drive folder containing 100MB and your family file contains only 2000 people, then most of that 100MB will not be getting synced to the cloud each time you make a change. Only about a 2 - 3 MB part of your family file will be getting synced as you make changes. The other 100MB that you have in that folder will not be getting synced unless it has been modified.

[Miss Myrtle]

By example, I have four volumes on my Mac -- the main one, one called Databases, one called Repositories, and one called Archives. I store various database-related content (from Devonthink, bibliography, and other "database-type" apps) in Databases, I store reference content in Repositories, and I store content that is to be moved to external archives on Archives.

Yes, I have a database fold in my user folder as well for DevonThink. I'm considering moving Reunion there as well.

[Miss Myrtle]

As you pointed out: If your family file is in an iCloud Drive or Dropbox folder, changes are uploaded to the cloud as files are modified.

If you have an iCloud Drive folder containing 100MB and your family file contains only 2000 people, then most of that 100MB will not be getting synced to the cloud each time you make a change. Only about a 2 - 3 MB part of your family file will be getting synced as you make changes. The other 100MB that you have in that folder will not be getting synced unless it has been modified.

I don't think that's what is happening? Hence my post. Here's my file so far. Each time I make a single change, it syncs the entire 93.1 megabytes or whatever it is at that sync. It isn't only syncing two to three megabytes.


People 64
Families 45
Places 64
Place Usage Unique places: 64 - Total instances: 259 - Maximum: 35 (Chicago, Cook, Illinois)
Sources 175
Fields 188
Clipboard Empty
Data Entry Font LucidaGrande, 11
Thumbnails Large People/Families - 318, 54.4 MB; Sources - 175, 31.9 MB
Thumbnails Small People/Families - 318, 3.4 MB; Sources - 175, 1.9 MB
File Size 93.1 MB
File Location /Users/deleted for privacy
Last Modified 51 minutes ago
Reunion Version 14.0 (build:260412) Apple cpu
Reunion Location /Applications/Reunion 14.app
Mac OS 26.5.0

[Gregg]

Oh, I see that you're correct. iCloud Drive treats the family file package as a single item so "yes" the entire 100MB is being uploaded with each change you make to the family file. It does seem like a waste, especially in cases where you're making changes faster than the family file can be uploaded to the cloud.

Dropbox is smart enough to not do that and treat the family file as individual pieces.

If keeping backups is a concern, you might want to consider getting an external hard drive and using Apple's Time Machine as mentioned earlier.

Retrieving backups from Dropbox and iCloud drive can be difficult and after a certain amount of time impossible.

Another option would be to ask Reunion to make a backup of your family file from time-to-time. After you've made some significant changes to your family file, choose File > Save a Backup Copy from Reunion's main menubar. You can keep the backup file small by unchecking the "Include Thumbnails" option. This will create a backup copy of your family file with a date stamp in the file name.

[Miss Myrtle]

If keeping backups is a concern, you might want to consider getting an external hard drive and using Apple's Time Machine as mentioned earlier.

Thanks Gregg. I went ahead and moved my Reunion folder to my user folder on my hard drive, and relinked the files. How awesomely easy that was!
I already have a large external hard drive that syncs daily with Time Machine. I'll make a backup file and upload it to my documents weekly as well. I have no desire to set up Dropbox syncing as I already pay for iCloud storage.

PS.. this can be fixed. My MFT software syncs incrementally with iCloud like Reunion does with dropbox. Perhaps something the team could look at in the future.

[DrJJWMac]

Yes, I have a database fold in my user folder as well for DevonThink. I'm considering moving Reunion there as well.

Not folder. Volume. Use Disk Utility to create one or more additional drive VOLUMEs on your internal HDD/SSD. The process is exceptionally easy to do and trouble free, especially for internal SSD drives.

The benefits of setting up separate drive volumes are that iCloud will not sync the other volumes when you use it to sync Documents & Desktop and that managing where you store Time Machine or other (e.g. Dropbox/Backblaze) backups on a volume-by-volume basis can be a more intuitive process than doing so on a folder-by-folder basis.

[Miss Myrtle]

The benefits of setting up separate drive volumes are that iCloud will not sync the other volumes when you use it to sync Documents & Desktop and that managing where you store Time Machine or other (e.g. Dropbox/Backblaze) backups on a volume-by-volume basis can be a more intuitive process than doing so on a folder-by-folder basis.

Thanks! I'lll look into this, good idea!

[Gregg]

Some thoughts about the Time Machine volume...

I always use an external hard drive (SSD now days) rather than partitioning the internal hard drive with a secondary volume. A few reasons for this...

• If the internal drive fails, then most likely the Time Machine volume will fail too and all will be lost.
• If your Mac dies, the Time Machine backups will be stuck in the Mac. (this is kinda the same as the first reason)
• You can have multiple Time Machine drives, so you can swap them once in a while, keeping the other one in a safe place.

On a laptop, when you're on the road you don't need to take the TM drive with you. When you get back home, you can connect it again and TM will do a backup right away.

[DrJJWMac]

I partition my internal drive in separate volumes primarily because I find it presents me with an easier (more intuitive) workflow. By example, I store folders for content related to Devonthink, Bookends, Obsidian, TapForms, and Zotero is in specific folders for each application on a dedicated internal volume called Databases. I find this approach is more intuitive than creating a Database folder located in the Documents folder on my main volume.

To be clear, I do not use any of my internal volumes for Time Machine (TM) backups. And I have one internal volume (Archives) that I exclude from any TM backups. I copy the content on Archives manually to a separate external drive and then delete the content from the internal Archives volume.

Finally, I second the recommendation to use an SSD for TM backups. An SSD is orders of magnitude faster than an HDD.