Time Machine detected that your backups on rCLDanielerCY cannot be reliably restored.
I've been away for a couple of weeks, and now:
Time Machine detected that your backups on rCLDanielerCY cannot be reliably >> restored.
It wants to erase my backup history and start a new backup.
My backup server is a Raspberry Pi running OpenMediaVault, but I have had this
before more than once after going away.
It seems that Time Machine is quite prone to this, and that possibly permissions are at the root of the issue (according to what I've read).
Why so sensitive, Time Machine?
Daniele
I've been away for a couple of weeks, and now:
Time Machine detected that your backups on "Daniele" cannot be reliably restored.
It wants to erase my backup history and start a new backup.
My backup server is a Raspberry Pi running OpenMediaVault, but I have had this
before more than once after going away.
It seems that Time Machine is quite prone to this, and that possibly permissions are at the root of the issue (according to what I've read).
Why so sensitive, Time Machine?
D.M. Procida <daniele-at-vurt-dot-org@invalid.com> wrote:
I've been away for a couple of weeks, and now:
Time Machine detected that your backups on "Daniele" cannot be reliably
restored.
It wants to erase my backup history and start a new backup.
My backup server is a Raspberry Pi running OpenMediaVault, but I have had this
before more than once after going away.
It seems that Time Machine is quite prone to this, and that possibly
permissions are at the root of the issue (according to what I've read).
Why so sensitive, Time Machine?
IIRC you could tell Time Machine to 'inherit' an older BU.
Has that been changed?
Jan
On 18/10/2025 20:08, D.M. Procida wrote:
I've been away for a couple of weeks, and now:
Time Machine detected that your backups on rCLDanielerCY cannot be reliably >>> restored.
It wants to erase my backup history and start a new backup.
My backup server is a Raspberry Pi running OpenMediaVault, but I have had this
before more than once after going away.
It seems that Time Machine is quite prone to this, and that possibly
permissions are at the root of the issue (according to what I've read).
Why so sensitive, Time Machine?
Daniele
No Idea but I've had that same message more than once now. I've simply done a new backup - obviously check for anything you might lose.
On 19 Oct 2025 at 09:27:19 BST, "David Kennedy"
<davidkennedygm@gmail.com> wrote:
On 18/10/2025 20:08, D.M. Procida wrote:
I've been away for a couple of weeks, and now:
Time Machine detected that your backups on rCLDanielerCY cannot be reliably
restored.
It wants to erase my backup history and start a new backup.
My backup server is a Raspberry Pi running OpenMediaVault, but I have had this
before more than once after going away.
It seems that Time Machine is quite prone to this, and that possibly
permissions are at the root of the issue (according to what I've read).
No Idea but I've had that same message more than once now. I've simply done a
new backup - obviously check for anything you might lose.
Yeah, I've had about three of those. Move the old sparsebundle aside
(needs to go into a folder else TM will find it despite renaming and
object or indeed delete it if you agree) and make a new one. Toss the
old bundle whenever.
It's like moving to a new set of tapes or something.
It has happened again, about two months after starting a new backup.
I am fairly sure that with an Apple Time Capsule it was not nearly so fragile.
It's not very confidence-inspiring.
On 7 Jan 2026 at 17:14:06 GMT, "D.M. Procida" <daniele-at-vurt-dot-org@invalid.com> wrote:
It has happened again, about two months after starting a new backup.
I am fairly sure that with an Apple Time Capsule it was not nearly so fragile.
It's not very confidence-inspiring.
I have been following the various Time Capsule replacements people have been using with different levels of success, and more and more I get the impression, that TM works best with a file system that the Mac supports natively, APFS or HFS+ before that. As far as I know, no NAS or any of the other solutions can use APFS.
Hence my plan is to dedicate a networked Mac mini with an external drive to take over the TC's task when the time comes. Storage can be upgraded easily by
plugging in a bigger drive.
That is exactly what I do successfully for two years. I bought a huge
HDD formatted it to APFS and then plugged into the mini. It is backing
up with TM every hour the machine is running.
I have separate 1 GB SSDs for our other Macs. One SSD for each Mac. I
have not intention to put all eggs in one basket.
On 09/01/2026 17:25, J||rg Lorenz wrote:
That is exactly what I do successfully for two years. I bought a huge
HDD formatted it to APFS and then plugged into the mini. It is backing
up with TM every hour the machine is running.
I have separate 1 GB SSDs for our other Macs. One SSD for each Mac. I
have not intention to put all eggs in one basket.
But you already have: if the Mini fails then it might corrupt all the attached drives. :-(
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 54 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 14:02:30 |
| Calls: | 742 |
| Files: | 1,218 |
| D/L today: |
3 files (2,681K bytes) |
| Messages: | 183,722 |
| Posted today: | 1 |