Notifications
Clear all

Time machine issue?

(@adalogue)
New Member Customer

Mac Mini Server - MacOS 10.13
iMac - MacOS 10.13.1

New Time Machine backups for Mac Mini not storing a as sparse bundle on SoftRAID volume (RAID1 using USB drives attached to Mac Mini Server).

However, spare bundle is made for iMac that uses Time Machine to back up to same SoftRAID volume attached to Mac Mini. Mac Mini TM bavkups are stored in “backups.backupdb”

Tried starting back up over (resetting link to backup volume), upgrading to 10.13.1, and still no luck.

Thoughts?

Quote
Topic starter Posted : 08/12/2017 12:10 am
(@softraid-support)
Member Admin

I am not sure from your description, what is going on.

We are aware of a High Sierra bug, where Time Machine Sharing in High Sierra doesn't work with any RAID volume, either with SoftRaid or Apple RAID.

You would have to give us step by step on your configuration that does not work, so it can be tried to be replicated.

Did it not work with 10.12.x? I would start with 10.12, if possible, as High Sierra introduces additional complexities (and bugs) and it may be more difficult to figure out the cause of this.

ReplyQuote
Posted : 08/12/2017 1:56 pm
(@gendev)
Active Member Customer

I think I have the same, or at least similar, problem.  I bought a Mercury Elite Pro Quad (USB) and put 2 2TB drives in it.  I created a RAID1 mirror volume of the full disks, formatted in APFS. When I point Time Machine to it for local backup, it tells me that it isn't formatted correctly and gives me the option to erase it to APFS again.  If I say yes, it just hangs indefinitely, or at least until my patience ran out.  If I don't invoke TM the volume is accessible, so I think it is directly TM related.

Here are the specs of my system:

MacOS 10.13.6

Mac Mini (Mid 2011) 2.5GHz i5 16GB

SoftRaid XT v6.2 Driver 6.2

Time Machine 1.3 (2020-11-14)

Is there a possible incompatibility between the APFS Time Machine expects from SoftRaid, and/or that delivered by High Sierra?  Although I suspect Both SR and TM are invoking the same utility under the covers. Or is this the RAID/TM bug alluded to in the earlier post?

Ultimately, I hope for this system to serve as a file server and remote TM target, on different drives and volumes.

ReplyQuote
Posted : 17/07/2022 4:25 pm
(@softraid-support)
Member Admin

@gendev 

Since this is 10.3.x, try using HFS and it should work. High Sierra did not have a full implementation of APFS, so there can be some weird issues, this may be one.

This post was modified 2 months ago by SoftRAID Support
ReplyQuote
Posted : 18/07/2022 9:21 am
(@gendev)
Active Member Customer
Posted by: @softraid-support

@gendev 

Since this is 10.3.x, try using HFS and it should work. High Sierra did not have a full implementation of APFS, so there can be some weird issues, this may be one.

Time Machine won't let me use anything but APFS. And I guess High Sierra didn't really have it.

This post was modified 2 months ago by SoftRAID Support
ReplyQuote
Posted : 18/07/2022 9:37 am
(@softraid-support)
Member Admin

@gendev 

Are you certain you cannot use an HFS volume in High Sierra? I have used SoftRAID HFS volumes with Time Machine. Time Machine is flaky, but it should function in your environment.

ReplyQuote
Posted : 18/07/2022 10:03 am
(@gendev)
Active Member Customer
Posted by: @softraid-support

@gendev 

Are you certain you cannot use an HFS volume in High Sierra? I have used SoftRAID HFS volumes with Time Machine. Time Machine is flaky, but it should function in your environment.

As soon as I point Time Machine at the mirror it asks me to erase the disk with APFS. Doesn't matter if it was HFS or APFS as invoked from SoftRAID.  Time Machine is currently working on an external USB drive, but doesn't give me the resiliency I'm hoping to have.

ReplyQuote
Posted : 18/07/2022 11:10 am
(@softraid-support)
Member Admin

@gendev 

I will test this myself. I never saw that. Let me get back later.

ReplyQuote
Posted : 18/07/2022 11:44 am
(@gendev)
Active Member Customer

I seem to have a workaround.  I compared the file system settings very carefully, and found "case sensitive" missing on the raid mirror when compared to the standalone TM drive. I used disc utility to erase the RAID mirror HFS+ volume and replaced it with HFS+ with "case sensitive; journaled" attributes. When I pointed TM at it, it did not ask me to erase and it is currently backing up.

Since it appears to be working, I will abandon APFS for now.

ReplyQuote
Posted : 19/07/2022 12:48 pm
Share:
close
open