Re: Amanda integrity and erc

amanda 3.3 and before do not have crc check. crc check is already in the development tree and will be included in the next major release. Restoring from a corrupted archive depend of the tool used. gtar can generally restore corrupted archive, some manual intervention can be required.

querying device-side compression setting

Hi, I'm setting up amanda 3.3.4 with a Quantum Scalar i500 tape library. Regrading compression options, I'll go with the recommendation in the documentation to let Amanda do the compression client-side. How can I determine if hardware compression is enabled on my tape library? I can't find

'labelstr' param in amanda.conf

Hi, I'm setting up amanda 3.3.4. Regarding 'labelstr' in amanda.conf: The documentation says: If multiple configurations are run from the same tape server host, it is helpful to set their labels to different strings (for example, DAILY[0-9][0-9]* vs. ARCHIVE[0-9][0-9]*) to avoid overwriting

'changerfile' param for tape robots

Hi, I'm working on setting up a robot tape changer. The docs for chg-robot:DEVICE say this:the changerfile parameter can be used to specify a filename at which it should store its state. Ordinarily, this state is stored in a file named after the changer device under $localstatedir/amanda, e.g.,

Re: 'labelstr' param in amanda.conf

On 01/09/2014 01:47 PM, Michael Stauffer wrote: Hi, I'm setting up amanda 3.3.4. Regarding 'labelstr' in amanda.conf: The documentation says: If multiple configurations are run from the same tape server host, it is helpful to set their labels to different strings (for example,

Re: 'changerfile' param for tape robots

The global changerfile is is a configuration file for the old changer API The changer changerfile is used as a state file by some of the new changer. Jean-Louis On 01/09/2014 01:48 PM, Michael Stauffer wrote: Hi, I'm working on setting up a robot tape changer. The docs for chg-robot:DEVICE

Re: 'labelstr' param in amanda.conf

op 09-01-14 19:47, Michael Stauffer schreef: Does this mean that if I have multiple configurations in order to break up a large 30TB data set into managable chunks, each configuration will have to have a particular set of tapes assigned to it? That seems very awkward if so. Why would you make

Re: querying device-side compression setting

On 01/09/2014 01:44 PM, Michael Stauffer wrote: Hi, I'm setting up amanda 3.3.4 with a Quantum Scalar i500 tape library. Regrading compression options, I'll go with the recommendation in the documentation to let Amanda do the compression client-side. How can I determine if hardware