On Wednesday 12 September 2007 17:03, David Boyes wrote: > I'm not sure I understand you completely. If you have a storage pool > defined in one SD and another storage pool defined in a separate SD, you > should be able to migrate from one SD to the other, as long as the > director in a particular instance knows about both SDs. We do that now, > and it seems to work OK (particularly if you migrate from a disk pool in > one location to a disk pool in the central location and then migrate to > tape at the central location). We run a separate SD on a different port > for each satellite location.
I guess I don't understand what you are saying above, because it sounds like you can write a backup to SD1, then do a migration job that reads the volume on SD1 and writes it to SD2. Is that what you are doing? and if so, can you explain how? > > You probably couldn't share volumes between SDs, but our central site is > heavily virtualized (mainframes are great for this) so we can control > the assignment of tape drives well. > > Is what you're asking for the ability to share SDs between multiple > directors? > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Bacula-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/bacula-devel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
