Here's what it looks like in OmniDiskSweeper:
I found a previous thread about this problem (http://apple.stackexchange.com/questions/112100/what-is-the-use-of-snapshot-db), but no way to stop this issue given that I'm not comfortable going into Terminal and messing around.
MacBook Air, OS X Mavericks (10.9.3)
yes, local snapshots.
http://support.apple.com/kb/ht4878
http://pondini.org/TM/30.html
how to turn them off:
http://osxdaily.com/2011/09/28/disable-time-machine-local-backups-in-mac-os-x-li on/
Local snapshots are useful in a very narrow almost non-existent perspective. Essentially they are not useful.
make constant time machine backups and they will not build up, either that or turn them off.
Your last comment helps a lot - I did just resume backing up to Time Machine after 3 weeks away from it. Will the very large file shrink again on its own as Time Machine backs up? Or should I just turn them off and back on?
(I've never entered anything in command line mode before so it slightly intimidates me.)
angelofhistory wrote:
Or should I just turn them off and back on?
I cant make that decision for you, however from a pure perspective of data backups and genuine data archives, local snapshots dont even come close to qualifying for either.
In the scheme of data protection, local snapshots fall into the arena and class of a tea cozy, useful on an almost non-existent level.
backing up to the very same device (the SSD) which can fail means SSD failure, means they both fail, ...your data and your 'local snapshots'.
always keep at the minimum 2 copies of vital data OFF the computer, 2 is 1 and 1 is none.
and local snapshots and anything IN the computer on its SSD qualifies as nothing.
Local snapshots are useful in the event that files are deleted or the file becomes corrupted and you are away from your backup disk... Something that happens quite often, especially with a MacBook Air.
Austin
I followed the instructions at the link you provided (that is, entering sudo tmutil disablelocal Terminal, then entering my password as prompted), but the snapshots.db file is still there and still 5.2 GB. Will it go away gradually as Time Machine resumes or...?
"especially with a MacBook Air" is a wholly incorrect statement.
local snapshots serve a purpose, however their arbitrary save-feature and nature make them both unwelcome and unnecessary in the extreme to anyone following correct data backup plans and methods.
Methodology to protect your data. Backups vs. Archives. Long-term data protection
You should make a TM backup and wail for the clearing of the local snapshots database before disabling the local snapshots.
Or, as mentioned, just make timely TM backups and not be concerned at all with local snapshots knowing they will vanish of their own accord due to ext. HD Time machine backups.
😊
No, I am saying MacBook Air is a VERY portable computer and therefore it is only reasonable it would be away from the Time Machine backup disk more often than any other kind of computer besides another kind of notebook.
Austin
I did make a TM backup before disabling the local backup. However, I didn't know from your post above that I needed to "wait for the clearing of the local snapshots database" - so I didn't. In any case, having disabled and reenabled the local backup, the 5.2 GB file is still there. So the problem has not been solved.
make a time machine backup to clear the snapshots (eventually)
restart and re-verify the snapshots are cleared.....if same, SMC reset and re-verify
SMC reset
That file has absolutely nothing to do with Time Machine or local snapshots.
Mavericks faux paus 😐
/private/var/db/systemstats/snapshots.db
Linc Davis, it doesn't help to tell me it has "nothing to do" with Time Machine - what (in your view) IS the file?
It's a log. You may be able to reduce its size by the following the instructions in my comment linked above.
Linc Davis, your post above didn't include any instructions. What type of log is it?
Snapshots.db is 5.2 GB and won't stop growing; how can I stop this?
