Well, that's just the problem. Because the catalog backup did run for 2,5
days, no backups were started. Here are the last part of the All log
entries :
10/01/2003 19:34:32 dvvbewkgbu00 Info 0 Backup
cleaning media DB(s)
10/01/2003 19:34:37 dvvbewkgbu00 Info 0 Backup
running session_notify
10/01/2003 19:34:37 dvvbewkgbu00 Info 0 Backup
performing database backup
10/01/2003 19:40:30 dvvbewkgbu00 Info 0 Backup
cleaning job DB
11/01/2003 0:00:01 dvvbewkgbu00 bpdbm Info 0 General
GOOD MORNING ****************
12/01/2003 0:00:01 dvvbewkgbu00 bpdbm Info 0 General
GOOD MORNING ****************
13/01/2003 0:00:01 dvvbewkgbu00 bpdbm Info 0 General
GOOD MORNING ****************
As you can see, as of 19:40 until the moment that this all log entries was
saved to this logfile, nothing ran. Around 9:00 this morning, the catalog
backup finished (will as the all log entries again) and then these messages
appeared again (ignore the time and day, it's the type of message I want to
show) :
10/01/2003 12:30:30 dvvbewkgbu00 Info 0 Backup
cleaning job DB
10/01/2003 12:30:41 dvvbewkgbu00 Info 0 Backup
scheduler found no backups due to run
10/01/2003 12:40:30 dvvbewkgbu00 Info 0 Backup
cleaning job DB
10/01/2003 12:40:40 dvvbewkgbu00 Info 0 Backup
scheduler found no backups due to run
10/01/2003 12:50:30 dvvbewkgbu00 Info 0 Backup
cleaning job DB
10/01/2003 12:50:40 dvvbewkgbu00 Info 0 Backup
scheduler found no backups due to run
"Patrick Whelan"
<consultant0610@h To: Bruno.Bossier AT
comparex DOT be
otmail.com> cc:
Subject: Re: [Veritas-bu]
Catalog backup took 2 days
01/13/2003 12:26
That is probably exactly what happened. If there was some kind of network
clitch that would explain it. Did it affect the regular back ups? If so you
might want to touch the file (see manual, I don't have a system) that runs
the cleanup jobs in the background.
= = = Original message = = =
Our customer had a strange problem. The catalog backup started on friday
evening at 19:34 and ended this morning (!) at around 9:00, so in total
almost 2,5 days. This is obviously not correct, because the catalog backup
takes normally around 12 to 15 minutes. We reran this morning a manual
catalog backup which took 12 minutes, as expected. As there was no logging
activated, it's hard to find out why this catalog backup took so long.
There is 1 master server and 8 media servers. Is it possible that for
whatever reason, the catalog backup kept on trying one of the media servers
to read the catalog, but couldn't and therefore kept on waiting until
someone this morning did something causing the backup to finish ?
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___________________________________________________________
Sent by ePrompter, the premier email notification software.
Free download at http://www.ePrompter.com.
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
|
