On Fri, 28 Nov 2008, WEAVER, Simon (external) wrote:
> > Hi All > SAP Media Server Win2k3_NBU 5.1 Media + SSO with Master > > Appear to have a problem with a Redo Log policy. > > If it gets a failure (say 96, 6 or 150), the job fails to re-run the > same day, but does re-run on the next backup window. > > Schedule is set to run every 2 hours and I have a window of 2 hours set > during the day. > > If I get no failures, all is well. But one failure, just one seems to > blow the schedule away! > > In some cases, if I re-create a new policy, it seems to be ok, until it > fails again. > > Just wondered if anyone has seen anything like this? Many Thanks > > Regards > > Si > > > This email (including any attachments) may contain confidential and/or > privileged information or information otherwise protected from disclosure. > If you are not the intended recipient, please notify the sender > immediately, do not copy this message or any attachments and do not use it > for any purpose or disclose its content to any person, but delete this > message and any attachments from your system. Astrium disclaims any and all > liability if this email transmission was virus corrupted, altered or > falsified. > --------------------------------------------------------------------- > Astrium Limited, Registered in England and Wales No. 2449259 > REGISTERED OFFICE:- > Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England Simon, Error 6 in database land can mean 100 different things, I suggest turning on debugging and check the database backup logs to see what the real error is first. Justin. _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu