I recently reviewd our Veritas backup jobs and found several databases
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thing
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. LaoyanGenerally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment