Two Time Machine backups at the same causing errors
Posted: Sat Nov 04, 2017 10:13 am
Hi,
I'm not sure at all if this is ZFS related or not but it's kind of my best guess right now. I hope someone else out there is using a similar setup and can tell me if this is just me or a general issue.
The issue:
One backup will fail as soon as two machines will run a Time Machine backup to my O3X storage server at the same time. Looks like the machine that comes first is able to do the backup. The second one will fail and the error depends on which machine fails.
One machine will get:
The other one tends to get that one:
Failed to mount because the image could not be attached, error: Error Domain=com.apple.backupd.ErrorDomain Code=21
[/code]
The backup of the other machine tends to get corrupted when the other machine tries to do a backup as well.
I tried adding quotas via the Server.app as well as on the file systems. There is more than enough free space available.
My current "solution" is to do frequent snapshots and revert back to a known good state in case a backup gets corrupted. (This kind of works since there is usually just one machine around and not
My setup:
macOS 10.12 / 10.13
O3X 1.6.1 / 1.7.0
The pool layout is a stripe of two mirrors with two disks each
file systems:
zfspool/tmbackups
zfspool/tmbackups/tm_<name1>
zfspool/tmbackups/tm_<name2>
Any help / hint is appreciated! Thanks!
I'm not sure at all if this is ZFS related or not but it's kind of my best guess right now. I hope someone else out there is using a similar setup and can tell me if this is just me or a general issue.
The issue:
One backup will fail as soon as two machines will run a Time Machine backup to my O3X storage server at the same time. Looks like the machine that comes first is able to do the backup. The second one will fail and the error depends on which machine fails.
One machine will get:
- Code: Select all
Failed to attach to image '/Volumes/TM-<Name1>/<Name1>.sparsebundle', DIHLDiskImageAttach returned: 110 (image not recognized)
The other one tends to get that one:
Failed to mount because the image could not be attached, error: Error Domain=com.apple.backupd.ErrorDomain Code=21
[/code]
The backup of the other machine tends to get corrupted when the other machine tries to do a backup as well.
I tried adding quotas via the Server.app as well as on the file systems. There is more than enough free space available.
My current "solution" is to do frequent snapshots and revert back to a known good state in case a backup gets corrupted. (This kind of works since there is usually just one machine around and not
My setup:
macOS 10.12 / 10.13
O3X 1.6.1 / 1.7.0
The pool layout is a stripe of two mirrors with two disks each
file systems:
zfspool/tmbackups
zfspool/tmbackups/tm_<name1>
zfspool/tmbackups/tm_<name2>
Any help / hint is appreciated! Thanks!