Hyper Backup did not remove versions for me when doing that. Now I'm out of ideas. ChronoSync is capable of mounting file shares - so this works out pretty well for me. Similar concerns with similar backup apps. I'm running the same as you but not not having any issues. What I can't find is a command that returns a list of the backup versions on the remote server to automate this. I have 256 backup versions.
It took me an hour or so to realize that something wasn't right. I did force low space and Time Machine was fine. Unfortunately I used the generic DiskStation user that I use for several other shared drives, at least one of which is usually mounted. If it's a Time Machine error, it might be the verification failed error. When space is depleted, Time Machine deletes the oldest backups.
Don't know much about SuperDuper or Carbon Copy Cloner, or any of this software. Well, that turned out to be a mistake. I will keep an eye on this thread. Or do I have to delete all my old backups to reach my goal? Dedicating a disk volume to Time Machine is not required, but I wanted a way to limit the space used by Time Machine. Now I know where to get working. I felt reassured though that my profile was also backed up via Crashplan.
Does anyone of you see a solution? Sat May 19, 2018 9:40 pm I use my 918+ 6. I've reached out to Synology and they say it's Apple's fault. Do you have a solution? I'm certain everything is configured properly, it's just acting up. I did set up a quick test using quotas and it seems to be a viable option. I've reached out to Apple and they say it's Synology's fault. What exactly is the issue? Eventually, after many tries, it did connect but same issue - barely moved and then dropped out. I've read several articles on this subject, but somehow I obviously still don't understand.
Going forward if you want to make a new restricted container, the concept isn't hard to map out though. Not sure if this is the answer but I ended up deleting old backups and starting over. Drag the renamed sparse-bundle into the trash. I have my synology ds916+ for about a month now. It's a great part of a layered backup approach to multiple targets, however. Don't think I ever will and I don't recommend you do either regardless of how well the Synology setup which probably uses netatalk works. I keep it off the network ditto the weekly image of the main Windows machine.
Comparable in functions to Time Machine? Better Solution While folders cannot have quotas, it turns out that users can. In this case, your only option is to create a single large shared folder and not use quotas. Since then, my trust in Time Machine has fallen even further. It doesn't need to be in the Apple family. You now can use the other partition for file storage; Time Machine will never touch it.
Time Machine will respect a size determination - but only when you make the container. It will take me days to manually click these stupid things so here's what I've found under the hood. All of these also let you create bootable duplicates and versioned backups. And is this save to do without damaging the bundle? Don't know much about SuperDuper or Carbon Copy Cloner, or any of this software. Is this a valid concern? Then suddenly a couple of days ago I was getting the same message as you did. I do a weekly system image using Carbon Copy Cloner.
Since the volume could handle it, it does appear to respect the quota. Yup, been there, done that many times. Comparable in functions to Time Machine? First, folders do not support quotas. I tried timemachine with a qnap and never got it working reliably and gave up. Most other backup programs let you customize backup behavior to suit your exact needs, and display logs detailing their activities. If you remove some earlier date folders, you will free up some space in order to resize the volume. I've noticed also that periodically perhaps after updates and rebooting that the Time Machine checkbox for the volume in File Services becomes unchecked.
My primary time machine backup used to be to a homegrown server running netatalk. Turn time machine back on and complete a backup. Hey Jabe — Thanks for the comment! Saved my butt a couple of times. It could be a corrupt backup, which is something that's mentioned on some of the apple threads. Creating a new version from the dialogue didn't work, so I had to delete the sparse-image manually and start over. Is this maybe because you are using this Mac File Service, and they are not? I've had this happen on 2 computers.