This is all good, safe, carefully-planned computer system management, but hits a brick wall when all attempts to trash the old backups return an error code -8072. Is it just a permissions problem? Please note that what you post to the list is publicly readable by anyone and regularly indexed by search engines. Depending on your system, the copying may take a while. Run ls -l and take note of the first numbered column. Then add the new drive, and turn Time Machine back on. You can save files to the files partition, leaving the backups partition for Time Machine alone. Here you need to be very careful.
You'll need to use sudo passwd root to give the root account a password before you are able to use it. Therefore, the sparsebundles from Storage 1 are copied to Storage 2 All of the permissions, shares, etc. These are the two partitions on the drive. It may have permissions wrong or locked. Your milage will vary depending on how you renamed the volumes. I consider your existing backups to be toast. Any feedback would be greatly appreciated.
If you select your entire hard drive as your backup set, including system and application files, these files could prevent your business files from backing up efficiently. I found this: But unfortunately it's not what I'm looking for. To unsubscribe, send email to. Note that for network backups, you will need to first access and mount the sparsebundle disk image that Time Machine creates on the drive. This is designed with snapshots built into it, which should form the basis of a replacement for the current Time Machine backup system.
I understand the difficulty with the problem. That alone will take a long, long time. We recommend you add your User folder. However, Time Machine is quite delicate. I feel a right fool now. From the description of the issue, I understand that you are unable to take full ownership of the files and folders. They would not comment on the external drive because it was not theirs.
Then I intend to wipe the first drive and replace the previously copied folder with all my backups back onto it. You must have ownership enabled to use this disk for Time Machine backups. And failing that I'll have to risk shutting the machine down by force. For a file, it should always be 1, but here it is not. I'll report back if I can but I'm presuming it may take some time for the privileges process to conclude.
This solved the issue for me. Within that path is a complete representation of your filesystem. Just leave this folder alone and let Time Machine use it normally. To unsubscribe, send email to. Now I am planning to drag the Backups.
Consider disabling it again when you are done - Ubuntu turns it off for a reason and it really isn't needed by 99% of users 99% of the time. I also had a look in the Achaia forums. What are the proper permissions? Finder will not handle deleting correctly. Now I am planning to drag the Backups. This is one more reason you don't rely on Time Machine as your only backup. Use one for Time Machine backups and another for your personal files.
About Time Capsule, you write you can successfully mount the drive, can you see its contents with the Finder? Hi Alex, Thank you for posting your query in Microsoft Community. Time Machine The Code42 app and Time Machine complement each other well and they can be used on the same device, side-by-side, backing up your live data. That actually caused me some trouble, since I didn't remember setting a root password when installing Ubuntu. To post to the group, send email to. If you have tried changing permissions and still get the same error when trying to trash the Backups.
I cannot access either of them. It may well fix this problem, though, so long as you are assiduously careful to enter the correct command. I want to move only the Time Machine backup to a new partition, not everything. I am not sure what is was that fixed it in the end. Apple discussions have countless examples of this but I can't recall a practical one that fixes it. I didn't mount the drive in any special way, just plugged in. You might be interested to know about sudo shell mode.