em: terça-feira, 21 de março de 2006 19:58
Para: Edson Noboru Yamada; Mailing List Amanda User
Assunto: Re: dumper issue - timeout problem?
Edson Noboru Yamada schreef:
>
> I´ve been facing a problem when trying to backup one of our clients.
> The backup starts normally, but after some
Hi,
I´ve been facing a problem when trying to backup one of our clients.
The backup starts normally, but after some time, the following message shows up
in the taper log:
dumper: stream_client: our side is 0.0.0.0.45740
driver: result time 553.824 from dumper0: FAILED 01-2 [mesg read:
Conne
Hi,
How long does amanda keep in its catalog a backup image?
I mean, what is the oldest backup I can restore for a specific client?
Is this configurable (for example, keep only the backups not older than 2
months)
or does this depend exclusively on the number of tapes amanda knows?
Thanks
Hi,
I have a few servers to backup; some of them is important
to backup every day (one full backup per week, incremental every day),
and others is enough to backup a single time per week (full).
Is there a easy way to do that? I know that specifying the machines names
as amdump parameters would
> tapecycle?
> Probably not exactly the same semantics but close enough: it is
> counted in number of tapes instead of days (but together with
> runspercycle and runtapes this becomes equivalent).
> Also amanda will warn a few days in advance when you would overwrite
> the last full dump of disk-
Hi,
I´m a Veritas Netbackup admin, and I´m trying to test Amanda
as an alternative.
With Netbackup, it´s possible to define a backup image retention time, that
is the number of days that an a given image must be preserved on a tape; a tape
is only reused if all the backup images it contains are
