Bacula-users

Re: [Bacula-users] Migration possible even with volume status "append"

2012-06-27 10:04:19
Subject: Re: [Bacula-users] Migration possible even with volume status "append"
From: Mario Moder <lists AT demaio DOT de>
To: <bacula-users AT lists.sourceforge DOT net>
Date: Wed, 27 Jun 2012 15:56:09 +0200
Am 26.06.2012 20:50, schrieb Martin Simmons:
>>>>>> On Tue, 26 Jun 2012 15:01:30 +0200, Mario Moder said:
>>
>> As the subject says: I have a pool with a file storage and a 
>> migration
>> pool with a tape storage. The documentation says: "Volumes that are
>> still marked Append will not be considered for migration".
>>
>> I have a migration job which does migrate from the appendable volume
>> without an error. Could this be a bug, or is the documention a bit 
>> out
>> of date?
>
> It might work for some values of the "Selection Type" option.  What 
> is your
> migration job configuration?

Sorry, I replied to you only, not to the list...

Thanks for your answer, this could explain it. Here is my migration job 
config:

Job {
   Name = "migrate"
   Type = Migrate
   Level = Full
   Client = bacula-fd
   FileSet="Full Set"
   Messages = Standard
   Pool = File
   Maximum Concurrent Jobs = 4
   Selection Type = Job
   Selection Pattern = "test-micos-job"
}


Greetings,

Mario



------------------------------------------------------------------------------
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 AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users