Re: Sharepoint and SQL Recovery Model



But Given the use of the spsbackup util, is it necessary to keep the DBs
marked as full?
Thanks
Bob

"Ada Pan [MSFT]" <v-adapan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:D6bwHt0nGHA.2024@xxxxxxxxxxxxxxxxxxxxxxxx
Hello Bob,

As I know, SQL Server 2000 uses recovery models to help you plan backups.
You can use either Simply or Full Recovery Model based on your need. The
following information is the differences between Simple or Full Recovery
Model:

o Simple The simple recovery model is designed for databases that need to
be recovered to the point of the last backup. The backup strategy with
this
model should consist of full and differential backups. You cannot perform
transaction log backups when the simple recovery model is enabled. SQL
Server 2000 turns on the Truncate Log On Checkpoint option, which clears
out inactive entries in the transaction log on checkpoint. Because this
model clears out transaction logs, it is ideal for most system databases.

o Full The full recovery model is designed for databases that need to be
recovered to the point of failure or to a specific point in time. With
this
model all operations are logged, including bulk operations and bulk
loading
of data. The backup strategy with this model should include full,
differential, and transaction log backups, or full and transaction log
backups only.

For more information, please see the article below:

SQL Server 2000 Administrator's Pocket Consultant: Database Backup and
Recovery
http://www.microsoft.com/technet/prodtechnol/sql/2000/books/c11ppcsq.mspx


You may need to back up the following databases in SQL Server 2000:

o PortalSiteName _PROF
o PortalSiteName _SERV
o PortalSiteName _SITE
o The SharePoint Portal Server 2003 configuration database. By default,
this database is named SPS_Config_db.

To do this, follow these steps:

1. Create a new folder on the hard disk drive to store the databases that
you back up.
2. Start SQL Server Enterprise Manager.
3. Expand Microsoft SQL Servers, expand the server group, expand the
appropriate server, and then expand Databases.
4. Right-click the database that you want to back up, point to All Tasks,
and then click Backup Database.
5. If a path is displayed in the Destination box, click the path, and then
click Remove.
6. Click Add. Click File name, and then specify the location of the folder
that you created in step 1 and the file name of the backup file. Use a
file
name that is the same as the name of the database. For example, when you
back up the PortalSiteName _PROF database, specify the file name as
PortalSiteName _PROF.
7. Click OK three times.
8. Click OK when you receive the message that the backup operation
completed successfully.
9. Repeat step 4 to step 7 for each database.


For more information, please see the articles below:

894164 How to move the databases that are used by SharePoint Portal Server
2003 to a computer that is running SQL Server
http://support.microsoft.com/?id=894164

Hope this helps.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.



.



Relevant Pages

  • What is the best practice to create Maintenance Plans
    ... There is not a definitive answer to the question of which backup is better. ... the database can be recovered to the point ... Full Recovery or Bulk-Logged Recovery model. ... Transaction Log backup for master database is not allowed. ...
    (microsoft.public.sqlserver.security)
  • RE: Backups have Shadow Copy Problems
    ... with volume Shadow Copy error 800423f4. ... You back up data from a volume that contains a Microsoft SQL Server ... The recovery model of the SQL Server database is configured to use an ... It just ensures backup will continue without reporting the error. ...
    (microsoft.public.windows.server.sbs)
  • Re: Start SQLServerAgent job Synchronously
    ... Wayne Snyder, MCDBA, SQL Server MVP ... > call and the caller resumes processing as soon as the call is made. ... > I have a set of SQLServerAgent jobs, each of which runs a BACKUP DATABASE ...
    (microsoft.public.sqlserver.server)
  • Re: Start SQLServerAgent job Synchronously
    ... Wayne Snyder, MCDBA, SQL Server MVP ... > call and the caller resumes processing as soon as the call is made. ... > I have a set of SQLServerAgent jobs, each of which runs a BACKUP DATABASE ...
    (microsoft.public.sqlserver.programming)
  • Re: "Best Practices" way to distribute MSDE
    ... > Restore a users's selected backup. ... for dayly house-keeping I do usually provide scripted job for database ... that file copy operation (not SQL Server backup!) can be performed.. ... my personala advice is to perform dayly house-keeping actions ...
    (microsoft.public.sqlserver.msde)