Backing up MS SQL?

Hi

I'm hoping that some could point me in the right direction for "best
practice" in:

1) securely backing up a complete sql7 and 2000 server containing many
databases.

2) backing up an individual database

3) Securing the transaction on the hour as a mile stone to return to in the
event of error or system failure.

Thanks

MarkHi

The first place to start is Books Online:
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adm
insql.chm::/ad_bkprst_9zcj.htm

John

"mark" <kardtech@.on.aibn.com> wrote in message
news:uFRIb.46$b06.7@.newsfep3-gui.server.ntli.net...
> Hi
> I'm hoping that some could point me in the right direction for "best
> practice" in:
> 1) securely backing up a complete sql7 and 2000 server containing many
> databases.
> 2) backing up an individual database
> 3) Securing the transaction on the hour as a mile stone to return to in
the
> event of error or system failure.
> Thanks
> Mark|||Standard Answer then. Thanks for NO help

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:b8UIb.3645$PB3.32098570@.news-text.cableinet.net...
> Hi
> The first place to start is Books Online:
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adm
> insql.chm::/ad_bkprst_9zcj.htm
> John
> "mark" <kardtech@.on.aibn.com> wrote in message
> news:uFRIb.46$b06.7@.newsfep3-gui.server.ntli.net...
> > Hi
> > I'm hoping that some could point me in the right direction for "best
> > practice" in:
> > 1) securely backing up a complete sql7 and 2000 server containing many
> > databases.
> > 2) backing up an individual database
> > 3) Securing the transaction on the hour as a mile stone to return to in
> the
> > event of error or system failure.
> > Thanks
> > Mark|||"mark" <kardtech@.on.aibn.com> wrote in message
news:iuUIb.85$b06.63@.newsfep3-gui.server.ntli.net...
> Standard Answer then. Thanks for NO help

What about the standard answer don't you like?

With more detail:

1) For backing up the actual installation, I generally find it easier to
reinstall the application if need be.

2) Backing up individual databases, look into creating a maintenance plan.
Or roll your own and use backup database as appropriate.

3) use BACKUP LOG on the required databases.

I'd also recommend getting a book on high availabilibity. The one from MS
press is quite good.

>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:b8UIb.3645$PB3.32098570@.news-text.cableinet.net...
> > Hi
> > The first place to start is Books Online:
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adm
> > insql.chm::/ad_bkprst_9zcj.htm
> > John
> > "mark" <kardtech@.on.aibn.com> wrote in message
> > news:uFRIb.46$b06.7@.newsfep3-gui.server.ntli.net...
> > > Hi
> > > > I'm hoping that some could point me in the right direction for "best
> > > practice" in:
> > > > 1) securely backing up a complete sql7 and 2000 server containing many
> > > databases.
> > > > 2) backing up an individual database
> > > > 3) Securing the transaction on the hour as a mile stone to return to
in
> > the
> > > event of error or system failure.
> > > > Thanks
> > > > Mark
> >|||Thankyou

"Greg D. Moore (Strider)" <mooregr@.greenms.com> wrote in message
news:7oWIb.34408$q55.5924@.twister.nyroc.rr.com...
> "mark" <kardtech@.on.aibn.com> wrote in message
> news:iuUIb.85$b06.63@.newsfep3-gui.server.ntli.net...
> > Standard Answer then. Thanks for NO help
> What about the standard answer don't you like?
> With more detail:
> 1) For backing up the actual installation, I generally find it easier to
> reinstall the application if need be.
> 2) Backing up individual databases, look into creating a maintenance plan.
> Or roll your own and use backup database as appropriate.
> 3) use BACKUP LOG on the required databases.
> I'd also recommend getting a book on high availabilibity. The one from MS
> press is quite good.
>
> > "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> > news:b8UIb.3645$PB3.32098570@.news-text.cableinet.net...
> > > Hi
> > > > The first place to start is Books Online:
> mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\adm
> > > insql.chm::/ad_bkprst_9zcj.htm
> > > > John
> > > > "mark" <kardtech@.on.aibn.com> wrote in message
> > > news:uFRIb.46$b06.7@.newsfep3-gui.server.ntli.net...
> > > > Hi
> > > > > > I'm hoping that some could point me in the right direction for "best
> > > > practice" in:
> > > > > > 1) securely backing up a complete sql7 and 2000 server containing
many
> > > > databases.
> > > > > > 2) backing up an individual database
> > > > > > 3) Securing the transaction on the hour as a mile stone to return to
> in
> > > the
> > > > event of error or system failure.
> > > > > > Thanks
> > > > > > Mark
> > > > > >|||"mark" <kardtech@.on.aibn.com> wrote in message
news:uFRIb.46$b06.7@.newsfep3-gui.server.ntli.net...
> Hi
> I'm hoping that some could point me in the right direction for "best
> practice" in:
> 1) securely backing up a complete sql7 and 2000 server containing many
> databases.

1.1) Schedule a complete backup of all production databases and include
the system databases master, msdb, model at some appropriate
timeslot.
To do this for the first time, try using Enterprise Manager, select
the
"schedule" option and then examine the TSQL code in the scheduled
task. Modify the schedule times to suit your operations.

1.2) Take a copy of the backup files offsite.

> 2) backing up an individual database

As above, so here below ... much like the
Hermetic tradition.

> 3) Securing the transaction on the hour as a mile stone to return to in
the
> event of error or system failure.

You will need to examine the differential backup strategies available
and gauge the best approach for this method in relation to your data.

The M$ documentation is not too bad at all if you are prepared to
go and experiment and learn by practice the operations therein
documented, and I'd be surprised if step by step instructions on
all of the above are not clearly established within it.

Pete Brown
Falls Creek
OZ