If the Time Capsule is 6-7+ years old, you would probably not want to keep data on the Time Capsule hard drive that you cannot afford to lose, since the hard drive becomes "suspect" about this time. You don't indicate how old the Time Capsule might be, but they do tend to start acting up around 5 years of age. The process will take longer than a normal incremental backup because Time Machine is checking files in addition to running a regular incremental backup. Note.you can watch the progress the same way, but the display will only show it as backup.
#Is backuploupe legit mac
Hold down the Shift key on your Mac while you click on the Time Machine "clock" icon at the top of the screen The process for a backup file of about 200 GB will usually take about 7-10 minutes before a message appears on the screen that the process was successful.
#Is backuploupe legit verification
Note.you can watch the progress of the Verification process by clicking on Open Time Machine Preferences. Hold down the Option key on your Mac while you click on the Time Machine "clock" icon at the top of the screen I really would welcome any advice, I don't want to loose my backups again.Ĭheck to make sure that you are not running any kind of anti-virus application on your Mac, or any other utility that claims to "optimize", "clean", "speed up", etc your Mac.ĭoes the Verification process also hang up when you. I have looked in Console, but I am not sure what I am looking for there is only one error showing there, but googling it, it doesn't seem to be related the error message is " - Unknown CGXDisplayDevice: 0x41dc9d00" and repeats even when no backup is underway. I am using a 2011 iMac, with High Sierra and a gigabite ethernet network connected via an Airport Extreme to the Airport Time Capsule."įollowing that post and responses received, I attempted to run Disc First Aid, but this just froze and I ended up reformating the drive and starting again with Time Machine backups.Īll has gone well until this week, when once again the verification is stopping at 74%, exactly as before. Is there a way of finding out what is happening and if there is an issue with the backups? I really don't want to delete the backup files and start again if I don't have to as I have backups going back a couple of years. I have left it verifying for upto a week, but once it is stuck it never moves on until I skip verification and then it will work okay for a few times. However, it regularly stops during verification and always at 74%.
My Time Machine backups seem to be working correctly, in that it runs backups and I can enter time machine to see files in the backup.
My experience is 20 GB of storage overhead is extremely unlikely so my hunch is it is an overly cautious estimate where the designers wanted to be "better safe than sorry" with making sure the actual backup used less space than estimated.I posted the following question in December last year.
#Is backuploupe legit software
As the software is likely glossing over these details or making overly conservative estimates on how much slack space is going to be needed on the destination. The file size is 536 bytes, yet it takes well over 600% more space than needed since that one file takes up a 4 KB block of space on the filesystem. HFS is fairly sophisticated on how it allocates blocks and stores files, but to simplify things - there is potential for huge inefficiency in file system storage.įor example, take this contact card I dragged onto my desktop:
At that point you could use tmutil compare or a tool like Backuploupe to see the actual payload size for that specific backup and feel better about whether this is an issue with directory corruption or just an estimate algorithm that isn't highly accurate for your storage details.ĭue to how files are stored on drives, you could have a lot of files that fit efficiently on the SSD but end up wasting more space when they sit on a larger volume like the 2 TB Time Capsule so it could also be literally correct and no over estimate. The 520 GB in your screen shot is just an estimate and since in some cases the estimate can be high somewhat substantially, you won't know if this is actually a problem until the backup completes.
0 kommentar(er)
