Dear All, I've been spending some time migrating jobs from an obsolete tape drive which is connected to an SD on one server a few hundred miles away to a rather newer tape unit connected to an SD on another server a few metres away.
As far as I can gather, under 2.4.2 it isn't possible to directly migrate data reading from one SD and writing to another. Let me give you an example of how I've worked around it, calling them SD1 and SD2. A migration job does the following: - Read the data from SD1 - Write it to a temporary staging pool (a file rather than a tape) managed by SD1 Once that's complete, copy the files which make up the staging pool onto the system where SD2 resides and update the database to reflect their location in SD2. Run another migration job which: - Reads the data from the staging pool (which we've now copied to SD2) - Writes it out to the tape managed by SD2. Phew. This leaves me with two questions: 1. Is this the only realistic way to deal with the problem I originally described? 2. Am I the only one to have encountered such a problem? (I'm not sure there's much point in submitting a feature request if I am because it probably won't affect me again anyway). James. -- James Cort IT Manager U4EA Technologies Ltd. -- U4EA Technologies http://www.u4eatech.com ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
