problem alternating targetDrives with same name

[prestonholmes]

We have been using super duper to do nightly smart updates of the server. I want to now rotate that external drive with an identical one on a weekly basis and take it off site.

I've named the volumes on each backup drive the same. But SD is not considering them identical as it is using something more than volume name. I want to be able to use a single nightly script and then just simply swap the drives weekly - is there a way to do this? Will the smart update algorithm handle it?

How can I get "SDTargetVolume" to look simply at volume name?

[dnanian]

Sorry, Preston, you can't: you'd have to use two different sets of saved settings, because the low-level ID of the drive is different. We don't really look at the name, because it can be changed outside of SD!, and we wouldn't want to copy to a drive that *happened* to be named the same, but could be a different drive...

[prestonholmes]

Will something like this be possible in 2.0? For now I'll just write it in the applescript that if exists volume A, use A settings, else if exists volume B use B settings. Am I going to have to delete the SDTargetSource property from the settings file if SD is left open all the time, or is that only an issue on being launched from a settings file?

Hopefully in addition to the kickass improvements in the scheduler, you guys are working on more complete applescript support for all those unforseen situations and scenarios.

Originally Posted by dnanian

Sorry, Preston, you can't: you'd have to use two different sets of saved settings, because the low-level ID of the drive is different. We don't really look at the name, because it can be changed outside of SD!, and we wouldn't want to copy to a drive that *happened* to be named the same, but could be a different drive...

[dnanian]

The only issue here is the settings file that's used. There's no reason to do anything but load the proper settings based on the drive you're going to use.

In the scheduler, you'd just set up the two drives separately, one running on week 1 & 3, one on 2 and 4/5.

We have some ideas for improved AppleScript support, but they're not coming in v2.0.