On Thu, Oct 19, 2017 at 11:06:40 -0400, Jean-Louis Martineau wrote:
> Since you want to vault all full, I would set 'vault' in the local
> storage, set 'dump-selection' in the cloud storage, but will not set
> 'vault-storage'
> That way the vault are scheduled but are not executed because
> vault-storage is not set. Amanda know they must be vaulted.
> Every month, you can run: amdump CONF BADHOST -ovault-storage="cloud"
> to do the vaulting.
I am testing a vaulting setup where I have "vault TestOffsite 0" set on
the main storage and a global "vault-storage TestOffsite".
If the TestOffsite vtapes are not available during the nightly amdump
run, dumps are written to the main storage and I see COPY commands queue
up command_file for the vault storage.
If I then mount the Offsite vtape partition and run an "amdump
TestBackup BADHOST" command, the dumps are successfully copied to the
vault, and amdump sends a report that looks like this:
=====
Hostname: backupserver
Org : TestBackup
Config : TestBackup
Date : November 16, 2017
The next tape Amanda expects to use is: TESTBACKUP-06.
FAILURE DUMP SUMMARY:
planner: FATAL no DLE to backup
STATISTICS:
Total Full Incr. Level:#
-------- -------- -------- --------
Estimate Time (hrs:min) 0:00
Run Time (hrs:min) 0:01
Dump Time (hrs:min) 0:00 0:00 0:00
Output Size (meg) 0.0 0.0 0.0
Original Size (meg) 0.0 0.0 0.0
Avg Compressed Size (%) -- -- --
DLEs Dumped 0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min) 0:00 0:00 0:00
Tape Size (meg) 0.0 0.0 0.0
Tape Used (%) 0.0 0.0 0.0
DLEs Taped 0 0 0
Parts Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
Label Time Size % DLEs Parts
TESTBACKUP-102 0:01 7489M 3.7 9 9
NOTES:
planner: Argument 'BADHOST' matches neither a host nor a disk.
driver: WARNING: got empty schedule from planner
taper: Slot 15 with label TESTBACKUP-15 is usable
taper: Slot 2 with label TESTBACKUP-102 is usable
taper: tape TESTBACKUP-102 kb 7669248 fm 9 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-MB OUT-MB COMP% MMM:SS KB/s MMM:SS KB/s
----------------------- ----------------------- -------------- --------------
(brought to you by Amanda version 3.5)
=====
The main thing I notice is that nothing is listed in the Dump Summary
section. As discussed in earlier emails, if the vault storage is
available during the nightly amdump run, the dumps written to the vault
show up as VAULT lines in the Dump Summary section.... so I'm wondering
if the equivalent dumps performed during a second run should be showing
up here in this report?
A second thing I noticed was the three error/warning messages coming
from the planner and driver caused by the use of "BADHOST". Unless
those messages are actually causing the empty Dump Summary section they
aren't a terrible problem... but especially for sites where the
recommended configuration is to regularly run a separate vaulting run of
amdump (such as the one discussed above), I wonder how difficult it
would be to add support to amdump for a recognized option to turn on a
"do pending vault operations but don't try to back up any new DLEs"
mode?
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
