Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Time Machine could not create a local snapshot to back up from.

I run TM backups for years on a machine in my network and this morning I got this message.

 

Time Machine couldn’t complete the backup to “Ganesh Server.local”.  Etc.

 

See pic.

 

The setup is as follows.  Hard wired network.  MBP backing up to a MM (2020 model) in the network all running 10.15.7.  Fixed IP addresses.  The TM backup is done to an external USB 3 disk attached to the MM.

 

As said worked like a dream for years till I got this message this morning.  As you see on the pic it worked fine at 08.20.  it failed at 09.20 and it keeps failing if I click the ‘Back Up Now” button.

 

Any idea as to how to fix this? 

 

 

 

 

Posted on Feb 10, 2021 12:59 AM

Reply
Question marked as Best reply

Posted on Feb 12, 2021 2:33 AM

I solved it.  As I write the TM is doing its thing.

 

Let me tell you how.

 

I noted that there are a few local snapshots on the machine.   After all the machine was reporting: Time Machine could not create a local snapshot to back up from.

 

So, I checked how many there are with Terminal.

 

tmutil listlocalsnapshots /

 

This showed about 8 of snapshots and I figured maybe any of them or one is corrupted or the likes.  

 

So, I looked for a way to delete them via Terminal.

 

This is what I found:

 

sudo tmutil thinLocalSnapshots / 10000000000 4

 

A brief explanation of what it means: 

/ Refers to the primary hard drive, usually one does not need to change that.  10000000000 refers to how big the amount is one will want to purge.  In this example it is 10 GB. 

 

To purge more, increase the number to any value in bytes, or execute the command several times.  I ran it once and checked if any of them where left using the first command, and all were gone.

 

The 4 stands for “urgency”. 1 is the highest one can use, but 4 is seems enough to delete.

 

Presently the TM is doing a backup and slowly seems to write stuff to the disk. 

 

Hope this helps somebody out there with the same challenge.  

9 replies
Question marked as Best reply

Feb 12, 2021 2:33 AM in response to ChangeAgent

I solved it.  As I write the TM is doing its thing.

 

Let me tell you how.

 

I noted that there are a few local snapshots on the machine.   After all the machine was reporting: Time Machine could not create a local snapshot to back up from.

 

So, I checked how many there are with Terminal.

 

tmutil listlocalsnapshots /

 

This showed about 8 of snapshots and I figured maybe any of them or one is corrupted or the likes.  

 

So, I looked for a way to delete them via Terminal.

 

This is what I found:

 

sudo tmutil thinLocalSnapshots / 10000000000 4

 

A brief explanation of what it means: 

/ Refers to the primary hard drive, usually one does not need to change that.  10000000000 refers to how big the amount is one will want to purge.  In this example it is 10 GB. 

 

To purge more, increase the number to any value in bytes, or execute the command several times.  I ran it once and checked if any of them where left using the first command, and all were gone.

 

The 4 stands for “urgency”. 1 is the highest one can use, but 4 is seems enough to delete.

 

Presently the TM is doing a backup and slowly seems to write stuff to the disk. 

 

Hope this helps somebody out there with the same challenge.  

Feb 10, 2021 8:42 AM in response to ChangeAgent

First thing to check is free space on your boot up drive, as that is where the snapshots used for Time Machine are created. If there is plenty of free space, then other problems can also cause this, but the most common thing is lack of free space.


If you have an additional external drive available, try connecting it DIRECTLY to your Mac and see if Time Machine can complete to that drive. (Time Machine can be used with more than one backup drive, it will alternate between them).

Feb 10, 2021 10:28 AM in response to steve626

Part of the problem might be the OS upgrade being forced to start *before* the Time Machine backup is complete (which is what just happened to me).


My preference is to complete a backup prior to upgrading... it would be nice if logic was built into the upgrade process to wait for a backup to finish before proceeding. Hopefully I'll be able to recover should there be an issue post-upgrade, but I suspect I won't based on the error message.

Feb 10, 2021 12:49 PM in response to steve626

steve626 wrote:

First thing to check is free space on your boot up drive, as that is where the snapshots used for Time Machine are created. If there is plenty of free space, then other problems can also cause this, but the most common thing is lack of free space.


My OS disk is only two-third full. so that can not be it.




If you have an additional external drive available, try connecting it DIRECTLY to your Mac and see if Time Machine can complete to that drive. (Time Machine can be used with more than one backup drive, it will alternate between them).


I try that.




Feb 10, 2021 12:51 PM in response to ach_du_lieber

ach_du_lieber wrote:

Part of the problem might be the OS upgrade being forced to start *before* the Time Machine backup is complete (which is what just happened to me).


Thanks. Not here as far as i am aware.


I Tend to turn of any BU software before I upgrade. however I have not done any software updates for days and the TM worked fine til this AM.



Feb 10, 2021 2:27 PM in response to ChangeAgent

ChangeAgent wrote:

If you have an additional external drive available, try connecting it DIRECTLY to your Mac and see if Time Machine can complete to that drive. (Time Machine can be used with more than one backup drive, it will alternate between them).

I try that.



Usually the next step, if that does not work, is to start checking the file system of the disk (your internal drive), or next, to look into whether the disk is damaged or even failing. Because being unable to write snapshots is anomalous, that should happen with no impediments.


For the backup destination "MM (2020 model) in the network" -- what is that? Is it a supported configuration for Time Machine?

Feb 10, 2021 10:37 PM in response to steve626

steve626 wrote:

Usually the next step, if that does not work, is to start checking the file system of the disk (your internal drive), or next, to look into whether the disk is damaged or even failing. Because being unable to write snapshots is anomalous, that should happen with no impediments.


I did a hardware test and all is well. The SSD is also fine in a read and write test.


For the backup destination "MM (2020 model) in the network" -- what is that? Is it a supported configuration for Time Machine?


MM=Macmini


And yes this is a recognised way of doing it. And I have been for almost 15 years with no problems what so ever using Macminis.

Feb 11, 2021 10:31 AM in response to ChangeAgent

ChangeAgent wrote:

I did a hardware test and all is well. The SSD is also fine in a read and write test.

All is not well because your computer is unable too make snapshots or complete a Time Machine backup.


To check the file system, you need to boot into Recovery and run Disk Utility First Aid on your internal drive to check for errors. These would be for file system errors, which can be caused by hardware problems or by software problems.


Not sure what hardware or read/write test you did, but the Apple hardware tests are limited. I suggest that you run DriveDX, both the health assessment based on SMART, temperature, and failed block count, plus many other parameters, as well as the short and long self tests, the long test will take some time to run.

Time Machine could not create a local snapshot to back up from.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.