Frustrated with Smart update and lack of drive space

[vudutu]

I love Super Duper but I am frustrated with one thing. Prehaps this is a feature request or I may be missing how to set up.

I have two BU drives on my OSX server, a Western Digital and a laCie both 465.8 gig drives partitioned into three vols. The total of the three drives I am backing up is 392 so with careful sizing of partitions the data should fit. I create a nightly schedule to one drive and a weekly to the other. The first time I do a full BU everything fits, but after a couple of Smart updates the space need keeps growing (I understand why) and it errors out because of lack of HD space. Not only do I now not have a current BU but I am forced (here is the frustrating part) to go to the the scheduler, check the time and dates for that BU, kill that scheduled BU, create a new one with the correct times and dates.

Why can't I at least double click on the error log scheduled copy and tell it to erase next time rather than having to kill and reschedule the event

OR

Better yet why won't Smart Update recognize that the destination vol is out of space and erase this time and do Smartupdate the next time?

Am I hosed, do I need to go buy another HD?

Personally I would pay triple the price for a ProDuper version that would give me this feature and help me manage in one window all of my drives and schedules.

[dnanian]

I explain how this can happen in the Troubleshooting section of the User's Guide -- it kind of depends on the kinds of things you're doing on the source.

This area is something we're looking at improving in the future...

[vudutu]

Dave, like I said I get WHY it happens I understand that SD Smart update needs space, I just don't want to delete and recreate the schedule each time. The work around might be to just use disk util to reformat the vol or just pitch the data but it seems cumbersome.

[dnanian]

You don't have to delete and recreate the schedule. Just run an erase-then-copy manually.

[vudutu]

Problem is I am not real comfy doing that in the middle of the day with 40 people logged in, I normally schedule BU in the middle of the night. For now I think I will just reformat the drive partition.

[dnanian]

Doing that will change its low-level ID, and then the drive won't be found...

[vudutu]

Thanks Dave
OK if not that what? Pitch everything in the trash and empty?

[dnanian]

Well, if you have an idea of what you've done, you can "help" Smart Update by renaming/moving the same folder...

[vudutu]

I am sorry Dave but I really don't understand what you are getting at.

[dnanian]

If you have two folders on a source, and rename one huge one to a new name, SD! might "see" the new folder (renamed) before it "sees" that the old folder was removed. So, it could copy before it deletes.

If you've done something like that, renaming the folder on the destination will both avoid copying and a potential disk full situation.

[vudutu]

Got ya, in this case that is not feasible, I am backing up my OS vol and a student and faculty home folders on an OSX server so I never actually interact with the data. So for now I think I will just throw away the data and empty trash BU when I get the no room error, is that OK? Just add my request for

"double click on the error log scheduled copy and tell it to erase next time rather than having to kill and reschedule the event"

To your possible update list

Thanks!