iMac M1 Monterey running slowly.

[pm-r]

This thread seems to be getting mixed up with discussions over different cloning apps? and I am finding it even more difficult to keep my head on straight?

...

I'm dropping out of the clone wars discussion, so that should die out. Let's focus on your backup.

Maybe one of the mods could move this new TM type discussion to a new separate thread...???


- Patrick
=======

 

[Jonzjob]

This is both the Disk Utility and the T M backup that is running at the moment. I do have a 2tb external HDD that has photos and video on it at the moment and that can be used for the T M, but according to the text on the T M window it should over write the last backups when the disk gets to be below the space needed for the backup.

I can't understand why there is no option to change the time span for the backup? And I have just realised that it had started a backup even although I have cleared the tick box for 'Back Up Automatically'.




I will have to come back to this in the morning. Thank you for your help and patience.

 

[chscag]

Maybe one of the mods could move this new TM type discussion to a new separate thread...???

Too complex to move things around Patrick. I will start a new thread instead when I get answers from Mike Bombich.

 

[MacInWin]

This is both the Disk Utility and the T M backup that is running at the moment. I do have a 2tb external HDD that has photos and video on it at the moment and that can be used for the T M, but according to the text on the T M window it should over write the last backups when the disk gets to be below the space needed for the backup.

I can't understand why there is no option to change the time span for the backup? And I have just realised that it had started a backup even although I have cleared the tick box for 'Back Up Automatically'.

View attachment 35272


I will have to come back to this in the morning. Thank you for your help and patience.

I think the reason it started was that it had tried and failed, so a backup was queued to go. Let it go for now, then reboot tomorrow and the queue should reset.

Can I recommend you take some things off the internal? 750GB on a TB drive is getting close to too much. And if you want to start using Photos (you mentioned it in another post) then you will need some elbow room on that internal drive. I start to get nervous if I get less than 300Gb left on my 1TB drive. Not that I will run out of space, but that not having lots of free space for the system to use might bog down performance.

 

[pm-r]

Too complex to move things around Patrick. I will start a new thread instead when I get answers from Mike Bombich.

Not to worry Charlie, at least not on my behalf, and I suspect that this Time Machine and it's backup time utility topic will just be a short burp in the process of things getting done and working properly on a new Mac.

At least I hope so.

PS: nice to see some gentle snowflakes falling here as long as they don't land and need shoveling!!! And we do have some real dark grey (snow capable holding) threatening clouds in the west and about 1 °C temps outside.


- Patrick
=======

 

[Randy B. Singer]

And that is my entire point. Integrated storage (to NOT call it a "drive" and confuse folks) means that when/if the storage fails, the clone is of no use getting that machine going again.

Well, two things...

First, you're going to have to get over it. Because that ship has sailed and it's not coming back. While it was a nice feature when we had it, it can't be restored and there is nothing else that does the same thing. Clone making software hasn't gotten worse, Apple has made the Macintosh different. Switching to Time Machine still isn't going to get you what a clone gives you. Having a clone is still a uniquely valuable and important thing.

Second, for all of the hand wringing and gnashing of teeth over this, it's probably all but a non-issue. Separate SSD's were becoming less and less long-lived, and slower, in order to make them less expensive. Apple remedied this by integrating high quality long term storage into the M1x chip package. I wouldn't be surprised if the only people who *ever* have an SSD problem with their M1x-based Mac are those who chose too small an SSD at the outset, and fill it up. Otherwise I expect the SSD's in M1x-based Macs to outlive the life of the rest of the computer. I strongly suspect that hearing about bricked M1x-based Macs due to having a dead SSD will be an incredibly rare event.

Going around bashing the making of clones is just spreading FUD. You already have people giving up on making clones needlessly. That's a crime, in my view.

 

[IWT]

I can't understand why there is no option to change the time span for the backup?

I think the reason it started was that it had tried and failed, so a backup was queued to go. Let it go for now, then reboot tomorrow and the queue should reset.

I believe that the extra-long time for the TM backup is that John chose case-sensitive Encrypted for his backup. I mentioned in an earlier post that it was my belief that APFS alone was standard practice for the great majority of users and that neither case-sensitive, nor encrypted backups were necessary.

Ian

 

[Jonzjob]

I will be redoing the T M backup from scratch again Ian, without the encryption! Honest

As far as the internal SSD state is concerned I am trying to get my photos off of it as much as I can and a question I was going to ask on the thread I have on Photos was going to be can it be put on an external SSD as I have a Crucial X8 1tb arriving today. If so then I can move about 4 or 500 gig off of the internal jobbie.

 

[IWT]

without the encryption!

Good man, John. Just APFS - no case sensitive or anything else. You're a star, keep at it!!

Ian

 

[Jonzjob]

I try to be good
Like I know that I should
It's my prayer for the end of the day

(thinks ? I could write a song about that )

 

[Jonzjob]

OK, the 2tb HDD is now the T M disk and I have configured it as APFS and the back up is under way. It's about 1/2 way through and has come up with a message telling me that I am doing a back up an encrypted SSD to an unencrypted HDD.

Is this a problem?

 

[pm-r]

It's about 1/2 way through and has come up with a message telling me that I am doing a back up an encrypted SSD to an unencrypted HDD.

Is this a problem?

I guess it depends on what you want regarding encryption of your internal boot drive data. It sounds like your internal drive was already encryptid, maybe by default, it seems that some of the new M1 iMacs do that, maybe check it out and see what you have:

are iMac M1 encrypted by default

Google Search

www.google.com

- Patrick
=======

 

[Jonzjob]

Well, it doesn't look like it?

 

[pm-r]

i don't believe the info is shown in that Get Info window.

You can check yourself using this method below which will tell you for sure whether it is or isn't:

To confirm the encryption status of your Mac, navigate to System Preferences > Security & Privacy > FileVault [tab]. If your hard drive is encrypted, the FileVault displays a message saying that FileVault is turned on. May 15, 2018

More info if needed here:

Google Search

www.google.com

I think a lot of members will tell you that encryption for normal User use is NOT required. So you may have a bit more work to do to reverse it. Aren't new Macs fun...


- Patrick
=======

 

[MacInWin]

TM in Monterey seems to change the target drive to Case-Sensitive. Not encrypted, but Case-Sensitive. I think the message about encryption comes because some system files, that the OS encrypts, are included in the backup. Not all of them, TM doesn't back up the entire system in Monterey (not needed on Mx systems), but some configuration files are in the encrypted system storage.

 

[IWT]

Thank you Jake and probably apologies to John. As I've said previously, APFS was the standard for Time Machine. Now, I gather that Monterey insists on case-sensitive - why I ask myself?; but if that's the new "norm", then so be it.

Ian

 

[pm-r]

I think the message about encryption comes because some system files, that the OS encrypts, are included in the backup. Not all of them, TM doesn't back up the entire system in Monterey (not needed on Mx systems), but some configuration files are in the encrypted system storage.

I think if Apple was a little bit more methodical and precise in their use of English, it would save a lot of guessing or misunderstanding. Actually, I think I could easily suggest they use much more methodical care and attention to the English they use.

This sounds rather familiar to some previous articles that have touched on the same topic and the same complaint, but it hasn't changed much.

Apple's great taste doesn't extend to grammar

The Verge is about technology and how it makes us feel. Founded in 2011, we offer our audience everything from breaking news to reviews to award-winning features and investigations, on our site, in video, and in podcasts.

www.theverge.com

- Patrick
=======

 

[chscag]

Good man, John. Just APFS - no case sensitive or anything else.

@ian:

I don't believe Disk Utility will allow an APFS format without adding case sensitive. At least that has been my experience. John got into a bit of trouble not because of the case sensitive part of the format but rather because he chose encryption.

Charlie

 

[MacInWin]

I don't believe Disk Utility will allow an APFS format without adding case sensitive.

I have multiple drives, both SSD and rotating, that are APFS and not case sensitive. But my TM target drive was changed and not by me. I read online that TM makes the change automatically. I have no idea why.

 

[Jonzjob]

Looks like it's encrapted folks. It just ain't willing to make it obvious



Oh, just as a matter of interest I never make mastikes, especially in smelling

And now I am wondering what difference the unenkripted T M will make? And I wonder if the left hand really knows that the right hand is there, never mind what it's doing?