Hi We are backing up clients to disk and migrate the jobs later to tape. So we defined a migration job.
The backup jobs named *.stage". And I defined in job resource Selection Type = Job Selection Pattern = ".*\.stage But this seems to try migrate already migrated jobs too. So I looked into the man pages and saw PoolUncopiedJobs which is what I would like to use, but for migration jobs, which does not exist (yet?). However, I know this could be solved using an SQL Query to specify also "from pool", but it seems there is no huge benefit using migration jobs. The only benefit I see is the size of the records in catalogue. Right? Should I move to copy job? Thanks for your comments. -- Adfinis SyGroup AG - Be smart. Think Open Source. René Moser, Senior System Engineer Keltenstrasse 98, CH-3018 Bern Tel.: +41 31 550 31 11 | http://www.adfinis-sygroup.ch
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
