Red Hat NETWORK PROXY 5.3.0 - Guide de l'utilisateur télécharger pdf (Page 250)

Configure Database Recovery Settings

SQL Server supports the following individual “Recovery Models” in SQL Server. They can be set

differently for each database. They are:

Simple: In Simple recovery, the only information kept in the transaction log is data that is necessary to

recover the database to a known good state when the server restarts. It is a misconception that this

setting does not cause the transaction log file to grow. In this mode, SQL Server is in what is known as

“Auto Truncate” mode, which means that the log file is periodically “rolled over” as data is moved

from the log file to the data file. In this mode, transaction log backups are not allowed, and “point in

time” recovery is not available. Due to the nature of VCM, it is recommended that the Simple recovery

model be used for all VMware databases, and that nightly FULL or INCREMENTAL backups be used.

Bulk Logged: In Bulk Logged recovery, the transaction log retains all “normal” transaction

information, and effectively discards those that result from a bulk operation. VCM makes extensive use

of the IROWSETFASTLOAD interface, which is bulk logged.

Full: In Full recovery, the transaction log retains all information until it is effectively purged through

the use of a SQL Server LOG backup operation. This setting is used when the Database Administrator

wants to be able to perform point in time recovery. It is also used to allow incremental backups of the

database. In VCM, there are other factors involved that make point in time recovery at best, tenuous. It

is recommended that you do not use this model. If you do decide to implement Full Recovery it is

critical to set up scheduled (generally daily) backups of the transaction log. The log files will continue to

grow and accumulate changes until they are backed up, so a Full Recovery database without scheduled

backups can quickly fill its disk and stop the system.

NOTE VCM database settings are set to Simple by default. If you change the VCM database recovery

setting to Full, you must manage your own log backups.

To configure the database recovery settings, follow these steps:

Connect to the Microsoft SQL Server Management Studio by selecting Start | All Programs |

Microsoft SQL Server 2005 | SQL Server Management Studio.

Expand the SQL instance.

Expand Databases.

Right-click VCM and select Properties. The Database Properties dialog box appears.

In the upper-left pane, click Options. The options pane appears.

In the Recovery model drop-down, select either Simple, Bulk-logged, or Full. Click OK to close the

Database Properties dialog box.

Create a Maintenance Plan for SQL Server 2005

Because VCM relies heavily on its SQL databases for its operation, SQL Server 2005 should undergo

routine maintenance. By setting up the automated maintenance functions on SQL 2005 servers hosting the

VCM database, VCM will run at peak performance and should require little operator intervention during

its lifecycle.

Follow these steps to create a maintenance plan for SQL Server 2005.

1. Start Microsoft SQL Server Management Studio.

vCenter Configuration Manager Installation and Getting Started Guide

250 VMware, Inc.

1 2 ... 245 246 247 248 249 250 251 252 253 254 255 ... 273 274

Pas de commentaire

Red Hat NETWORK PROXY 5.3.0 - Guide de l'utilisateur Page 250