Re: Maintenance PLan recommendation

From: Geoff N. Hiten (SRDBA_at_Careerbuilder.com)
Date: 06/02/04 

Date: Wed, 2 Jun 2004 14:31:01 -0400

FYI, I just submitted a community KB article on this. It has been approved
and should show up in the search results sometime in the next 24 hours. 

-- 
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message
news:e$bg8YMSEHA.2408@TK2MSFTNGP10.phx.gbl...
> I can definitely confirm that what Geoff is stating is true.  I just came
> off a project where over 200 servers were all using the MP to backup to
> remote machines.
>
> -- 
>
> Andrew J. Kelly
> SQL Server MVP
>
>
> "Julie" <anonymous@discussions.microsoft.com> wrote in message
> news:1720701c448ba$b687b340$a301280a@phx.gbl...
> > Thanks Geoff,
> >
> > I will give that a try
> >
> > ;)
> >
> > J
> >
> >
> > >-----Original Message-----
> > >UNC names do work, but it requires a few prerequisites.
> > >
> > >First, SQL must be running on a domain-level account.
> > >Second, the SQL Service account must have FULL CONTROL
> > rights to the target
> > >directory.  Do not use administrative (C$, D$, etc)
> > shares.
> > >Third, UNC names only.  Mapped drives don't work
> > reliably.  Type the name in
> > >the 'use this directory' field.  No trailing \ is
> > necessary.
> > >
> > >Yes, BOL says local disks only.  It is wrong.  I have
> > sent feedback to the
> > >BOL team.
> > >
> > >I like to log into the SQL server console as the SQL
> > service account to test
> > >access to the shared folder.
> > >
> > >-- 
> > >Geoff N. Hiten
> > >Microsoft SQL Server MVP
> > >Senior Database Administrator
> > >Careerbuilder.com
> > >
> > >I support the Professional Association for SQL Server
> > >www.sqlpass.org
> > >
> > >"Julie" <anonymous@discussions.microsoft.com> wrote in
> > message
> > >news:1718401c448b5$677667b0$a301280a@phx.gbl...
> > >> Well Geoff that your opinion, but I have never been able
> > >> to get it to work as it always states 'Invalid
> > Directory'
> > >> when I put in the UNC name.
> > >>
> > >> BOL states 'Back up the database to the specified disk
> > >> directory. Only disks located on the same computer as
> > the
> > >> database can be used. Click the browse (...) button to
> > >> change the default directory used to back up the
> > database.
> > >> Only drives on the computer containing the SQL Server
> > >> database being backed up can be selected.'
> > >>
> > >> My understanding from the 'Only disks located on the
> > same
> > >> computer as the database can be used' part is that you
> > >> can't back it up onto a different server.
> > >>
> > >> J
> > >>
> > >> BTW I would be REALLY happy if I was wrong
> > >>
> > >>
> > >> >-----Original Message-----
> > >> >Actually, you can type a UNC name for the backup target
> > >> location.
> > >> >
> > >> >-- 
> > >> >Geoff N. Hiten
> > >> >Microsoft SQL Server MVP
> > >> >Senior Database Administrator
> > >> >Careerbuilder.com
> > >> >
> > >> >I support the Professional Association for SQL Server
> > >> >www.sqlpass.org
> > >> >
> > >> >"Julie" <anonymous@discussions.microsoft.com> wrote in
> > >> message
> > >> >news:170ca01c448ab$ce50dd30$a401280a@phx.gbl...
> > >> >> Just to add something to what Geoff said.
> > >> >>
> > >> >> One of the problems with the Backup and Maintenance
> > plan
> > >> >> is that it only allows backup to the server your on,
> > so
> > >> if
> > >> >> that server goes kaput you will lose the ability to
> > >> >> restore quickly.
> > >> >>
> > >> >> So its good practice to use the SQL commands to
> > backup
> > >> >> your Production database on a different server.
> > However
> > >> >> you cannot use the Maintenance Plan for this.
> > >> >>
> > >> >> My personal feeling about the Mainteance plan is
> > that is
> > >> >> was a very good idea, badly implemented.
> > >> >>
> > >> >> J
> > >> >>
> > >> >>
> > >> >> >-----Original Message-----
> > >> >> >I have taken over for a previous dba at a company
> > this
> > >> >> >week and I am examining the maintenance plans
> > created
> > >> by
> > >> >> >the person before me. They have one maintenance plan
> > >> set
> > >> >> >do full backups AND tran log back ups once a week
> > for
> > >> 11
> > >> >> >DB's. My question is this- Does that seem a bit
> > much to
> > >> >> >put under one plan? Is there a good number of DB's
> > (I
> > >> >> >would have thought only one per plan)that I can
> > break
> > >> >> >this down to? I am witnessing some failures in the
> > >> >> >tranlog backup steps and want to isolate them.
> > Thanks!
> > >> >> >.
> > >> >> >
> > >> >
> > >> >
> > >> >.
> > >> >
> > >
> > >
> > >.
> > >
>
>