Nope - that resolves the issue #1, why it had the problem.
Issue #2 is more of an FYI - since Veritas MSSQL agent passes control to a
script, that script can leave the parent job high and dry - in this case when
it attempted to do an incremental backup of a database it did not have a full
backup of.
Instead of the parent job ending with an error code - it never ended, AND also
prevented any additional jobs from running. Since these run every hour that
means that I lost several hours of logs for point in time restores. In this
case I got the logs from 1000 then nothing until after the midnight full backup
ran.
My operators now know to look for log running jobs of this policy, but it would
be nicer if SQL and NetBackup worked better together.
David McMullin
-----Original Message-----
From: bob944 [mailto:bob944 AT attglobal DOT net]
Sent: Saturday, February 21, 2009 1:22 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Cc: David McMullin
Subject: RE: [Veritas-bu] SQL issue
> Update from my DBA - these are transaction log backups, and
> he added a new database - since the TL will fail if there is
> not a backup, that is what caused the issue. Why would
> NetBackup not see this? He claims his SQL scripts ran through
> and finished, but the parent jobs never acknowledged this.
>
> I have received a recommendation to get a patch for the
> bpbrm, but that was based on 5.1 mp6. Shouldn't 6.5.2A have
> any patches from 5.1?
>
>
> NetBackup support response is that this is not their problem.
> Any ideas?
Add a database; do a full. Is there a problem after that?
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|