drae Posted October 27, 2008 Report Share Posted October 27, 2008 I archive files from two Macs through the company ftp site to our main hard drive which is backed up and taken off site by an archive service. After a year and a half of setting it up I'm getting the following error: Device trouble: “M-F Complete Backup Setâ€, error 225 (FTP: no write privileges, bad name, or disk full). My first issue is to resolve this error, but I also want to know how I can manage the number of snapshot files that are saved on our main drive. I don't need more than 4 month saved. Do I need to change the strategy to include recycle? I've looked through the manual to try to understand what recycle does, but don't get it yet. Can you help with the error, and give me a Network Backup Strategy that I can use? Thank you. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted October 27, 2008 Report Share Posted October 27, 2008 I archive files from two Macs through the company ftp site to our main hard drive which is backed up and taken off site by an archive service.After a year and a half of setting it up I'm getting the following error: Device trouble: “M-F Complete Backup Setâ€, error 225 (FTP: no write privileges, bad name, or disk full). My first issue is to resolve this error It may be that you are encountering a limit in Retrospect. There is a painful hack to let you change the size of FTP segments. See this thread here: ResEdit hack for Retrospect FTP segment size I also want to know how I can manage the number of snapshot files that are saved on our main drive. I don't need more than 4 month saved. Do I need to change the strategy to include recycle? I've looked through the manual to try to understand what recycle does, but don't get it yet. What you really want is "grooming", which can purge out old snapshots, but the Macintosh version of Retrospect doesn't have that. We can hope for Retrospect X, which is supposed to go into beta "real soon now" (later this year), which has been announced as having that feature like the Windows version does. "Recycle" will delete EVERYTHING in the backup set, resetting contents to empty. Yes, that would be a harsh way of dealing with the issue. Another way would be to start a new backup set (with different name), which would leave the old backup set unchanged. Russ Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.