Skip to content

Document reusing existing Time Machine backups#214

Open
houmark wants to merge 1 commit into
jamesyc:mainfrom
houmark:codex/faq-existing-time-machine-backups
Open

Document reusing existing Time Machine backups#214
houmark wants to merge 1 commit into
jamesyc:mainfrom
houmark:codex/faq-existing-time-machine-backups

Conversation

@houmark

@houmark houmark commented Jun 20, 2026

Copy link
Copy Markdown

Summary

  • add FAQ guidance that install/deploy does not overwrite existing Time Machine sparsebundle backups
  • describe how to reuse an existing sparsebundle by moving it to the SMB share root, including the default ShareRoot behavior
  • document the old per-user folder case and the privacy limits of the single device-password SMB share

Context

This follows the discussion in #29 where an existing AFP Time Capsule backup was successfully reused after moving the sparsebundle into the root of the SMB share and rebooting the Time Capsule and Mac.

Testing

  • git diff --cached --check

No code tests were run; this is a documentation-only change.

Add FAQ guidance for preserving existing sparsebundle backups when moving from the original Time Capsule AFP setup to TimeCapsuleSMB.

The notes clarify the default ShareRoot path, user-folder migrations, reboot recovery for stale Time Machine state, and the limits of the single device-password SMB share.
@houmark
houmark marked this pull request as ready for review June 20, 2026 05:33

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the FAQ.md file to address common questions regarding existing backups, user folders, and multi-user privacy. The reviewer suggests updating references to .sparsebundle to also include .backupbundle across the document, as modern macOS versions (Big Sur and later) use the .backupbundle extension for SMB-based Time Machine backups.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread FAQ.md
Comment thread FAQ.md

#### Can I keep using an existing Time Machine backup?

Yes. Install with the standard settings first and confirm the SMB connection works. Then move the existing `.sparsebundle` into the root of the SMB share Time Machine sees. With standard internal-disk settings, that is the `ShareRoot` folder. If you intentionally enabled "Internal Share Uses Disk Root", that is the disk root.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Since modern macOS versions use the .backupbundle extension for SMB-based Time Machine backups, we should mention both .sparsebundle and .backupbundle here as well to ensure users can locate their existing backups correctly.

Suggested Change:

Yes. Install with the standard settings first and confirm the SMB connection works. Then move the existing `.sparsebundle` or `.backupbundle` into the root of the SMB share Time Machine sees. With standard internal-disk settings, that is the `ShareRoot` folder. If you intentionally enabled "Internal Share Uses Disk Root", that is the disk root.

Comment thread FAQ.md

#### What if my old backup was inside a user folder?

Old Time Capsule setups could store backups under separate user folders. TimeCapsuleSMB uses one device-password SMB share, so move any `.sparsebundle` backups you want to keep out of those user folders and into the root of the SMB share.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Update this reference to include .backupbundle as well, ensuring consistency across the FAQ for users on newer macOS versions.

Suggested Change:

Old Time Capsule setups could store backups under separate user folders. TimeCapsuleSMB uses one device-password SMB share, so move any `.sparsebundle` or `.backupbundle` backups you want to keep out of those user folders and into the root of the SMB share.

Comment thread FAQ.md

Not in the same way as the original Time Capsule user-folder mode. TimeCapsuleSMB currently uses the Time Capsule device password for SMB access, and anyone who can connect to the share can see and delete the backup bundles.

For privacy, turn on Time Machine encryption for each Mac. Other household members may still see or delete the `.sparsebundle` file if they have SMB access, but they should not be able to open the backup contents without the encryption password.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Update this reference to include .backupbundle as well, ensuring consistency across the FAQ for users on newer macOS versions.

Suggested Change:

For privacy, turn on Time Machine encryption for each Mac. Other household members may still see or delete the `.sparsebundle` or `.backupbundle` file if they have SMB access, but they should not be able to open the backup contents without the encryption password.

@DMBlakeley

Copy link
Copy Markdown

I believe that there is a much easier approach.

After installation and confirmation of SMB connections, go to Settings/Genera/Time Machine, delete the old Time Machine by highlighting and then selecting "-", which will delete this instance. Then select "+" which will find the new SMB version, select, and answer Yes to reuse backups that already exist. At that point, you are all set.

@houmark

houmark commented Jun 21, 2026

Copy link
Copy Markdown
Author

I believe that there is a much easier approach.

After installation and confirmation of SMB connections, go to Settings/Genera/Time Machine, delete the old Time Machine by highlighting and then selecting "-", which will delete this instance. Then select "+" which will find the new SMB version, select, and answer Yes to reuse backups that already exist. At that point, you are all set.

That depends on the setup you had on your Time Capsule prior to installing this tool.

I had multi‑user configured, meaning it creates a user’s folder with my user inside, and that’s where it places the backup so only I, with my actual username and password, can access it. Other people in my household can have their own user folder, and they can both store backups and files in that folder to use it as a mini NAS (this feature is what I will miss the most about the original setup, being able to provide a network volume/folder for other members of my household where they can save stuff they don't want on their main Mac without anyone else having access to those files). This tool currently does not support that, so all backups must be in the same folder. If I follow your suggestion, it won’t find my existing backup because it was placed in a different folder, so I had to move the backup into the root of the volume.

@houmark

houmark commented Jun 21, 2026

Copy link
Copy Markdown
Author

And just to add to this, my testing did show that once I tried to set up the actual Time Machine configuration exactly following your steps, it would only set up a brand-new Time Machine backup until I actually manually went in and moved the existing sparse bundle file from my user folder to the root using the mv command line function which btw took less than a second to complete because it was just doing a metadata rename.

@DMBlakeley

Copy link
Copy Markdown

I believe you, but I only deleted the old and added the new accepting the pop-up that backups already existed for my system.

@houmark

houmark commented Jun 21, 2026

Copy link
Copy Markdown
Author

Maybe you didn't use users?

I don't know how your system works, but I'm assuming that other people might have the same problem as I've encountered. And for that reason, I think that a FAQ item that explains it in the case that it doesn't work for them is helpful. Maybe there is a point that this could work automatically, but since I am not able to replicate that or even attempt to do that, I cannot obviously say if this will work in most cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants