Does this include the two clients who fail — do THEY also say that their estimates are complete? Or are they still working on estimates, and thus holding up the whole works? All of the estimates seem to need to finish, before anybody gets to start. Deb Baddorf Fermilab
On Aug 17, 2015, at 2:33 PM, Seann <nombran...@tsukinokage.net> wrote: > All, > > I am looking for a little direction on a problem that has cropped up for me > recently. > > I have a backup set, that was created using Amanda 2.5 (default on CentOS > 5.11) and ran very well, both manually and from the cron job I had set for it. > It has approximately 13 hosts to backup, from as simple as backing up a > single directory, to backing up the full system, and it ran with no issues on > CentOS 5.11. > The basic setup is using hard drives as the backup media, compressing the > backups to save space, using server compression, these also use GNU-TAR as > the archive format. > > Fast forward to today, I have the system upgraded to CentOS 7, which also > upgraded to Amanda 3.3.3-13, and after some configuration file re-writing, I > got most of the backups to work. > Two systems, one backing up the web directory, the other backing up the full > disk, fail constantly. > When these two disklist statements are removed, the backup runs, and takes > approximately 2 and a half hours to run on the 8 other hosts (the other 3 > hosts are currently offline and not in scope). > > When the CRON job kicks off at midnight, it runs for over 12 hours (I have > the etimeout set to one day, as the planner kept dying saying to timed out). > This is the same basic error that I get with the two above mentioned failing > backups. > > When the hung backup job is running, I see the dumpers and main dump process > running on the backup server, but nothing in the logs outside of the "We > started the backup job" type of log messages. > On all of the hosts, I don't see the client running, nor to I see any TAR > processes running. > There are also no clues in the logs on which host the server is waiting on, > and checking all the hosts in scope show they are all in the same state, that > is they have sent the estimate to the backup server and are waiting on the > next phase. > > > Any help on this would be appreciated, and also is there a better way of > making sense of the logs (such as using something like Graylog2?), and on > reporting for issues with Amanda 3.3? > > > Regards, > Seann
