Due to an issue with Family Tree Make 2024 my Ancestry tree (whose master is in RM 11) got horribly corrupted with hundreds if not thousands of ~FTM facts and in some cases replaces ~FTM names made primary. This isn’t an RM issue except for the fact RM is the my master and I need to completely refresh my Ancestry tree from RM.
I haven’t had to do this for a few years and versions of RM ago so I’d like to verify what I think is the process as it’s going to take some time as I have 50,000 people.
Disconnect my MacOS database from Ancestry (unlink)
Rename Ancestry database to {databasename} Archive
Run full set of database tools on MacOS
Transfer database and media to Windows 11
Run full set of database tools
Upload database to New Ancestry Tree
Transfer database back to MacOS (no media)
Run full set of database tools
Does that sounds like the correct process? It’s been a few years.
Looks good. Maybe just add a backup as step 1. I assume the gyrations of going to windows are because you had problems uploading directly from macOS. My process is slightly different… here’s 2 changes for you to consider:
Don’t do steps 1& 2 until the very end… use a copy of your current RM master to create the new ancestry tree. It might take multiple attempts to get a good upload and with this approoch, you can keep you current RM master and Ancestry tree intact until you are 100% comfortable with the new tree.
My tree is much smaller so I don’t need the Windows upload. If you have not already done so already, you might try the upload directly from macos before using windows. It very possibly will still fail, but it’s worth testing on the new ancestry api
Maybe something like. this
Backup RM db
Make a copy of your MacOS RM database, rename it
Run full set of database tools on new MacOS RM copy db
Disconnect new MacOS RM copy db from Ancestry (unlink)
Upload database from new MacOS RM copy to New Ancestry Tree
Verify that all people and media xfer, spot check citations, etc
If success go to 14, otherwise go to step 8
Transfer database and media to Windows 11
Run full set of database tools
Upload database to New Ancestry Tree
Verify that all people and media xfer, spot check citations, etc
Transfer database back to MacOS (no media)
Run full set of database tools
Rename old MacOS database to {databasename} Archive
Rename Ancestry tree to {tree name} Archive
Confirm that new MacOS RM file and Ancestry tree names are named in the way you desire
I’m a Windows user who has zero experience with RM on a Mac. May I assume that you are having problems with TreeShare on a Mac, or else maybe you are worried about TreeShare on a Mac? Absent that kind of issue, it would seem that you could just do all your work for this project on your Mac.
@thejerrybryan Mac is my primary machine, but the last time I had to refresh my Ancestry tree (after the citation merge debacle) there was an issue with the building of the AMT_ Ancestry tracking database on the Mac when doing a large upload. My assumption is that the SQLite driver they use is not set up correctly or outdated on the Mac. Works fine for normal activity. So that I’ve done in the past is refresh on WIndows, then copy the AMT_ tracking database back to the Mac (and the regular .rmtree too of course).
Since I’ve not tried this on RM11 with the new API I’ve decided to try it first on the Mac, then revert to Windows if this doesn’t work.
@rzamor1 for support’s information I did an experiment. The original upload on MacOS had upload media enabled, and stalled at the point shown. So I retried without media upload, and it started uploading people but rather slowly. For kicks and grins I started the upload on Windows 11 to a different tree from a copy of the database (and media) as I’d originally planned.
So the next morning the MacOS upload has stalled ..
So for analysis sake two machines of roughly the same capabilities, on the same network, using the same database, going to the same Ancestry account, RM 11.4 on Windows worked, MacOS stalled. Support should be able to reproduce this themselves easily and find the performance issue.
@rzamor1 I should note that neither the Mac or Windows tree uploads provided any relationships, so not I have 48,000 unlinked people in an Ancestry tree, which is basically worthless. I’ll open a ticket shortly.
As an FYI for anyone following this thread I’ll note I finally got an upload to from MacOS on a Mac Studio M2 Max running Tahoe. No idea why the Windows upload didn’t work with relationships, but at least I’m back in business.
That’s really good news! I have seen others report this same problem where large RM db files could not be uploaded via MacOS. It’s good to know that, at least for you, the problem has been solved with some combination of RM 11.4.0 update and the new ancestry API.
