Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Deployment best practices
This chapter covers best practices for installation and initial configuration of Cisco TMS.
Database Maintenance Planning
Cisco TMS and Cisco TMSPE both create databases according to the default settings of the SQL server. The databases
are:
are:
■
tmsng (Cisco TMS)
■
tmspe (Cisco TMSPE main)
■
tmspe_vmr (Cisco TMSPE Collaboration Meeting Rooms)
■
tms_userportal (Cisco TMSPE self-service portal)
Below are the best practices for setting up and keeping a maintenance plan for your database or databases. Database
management must be handled through an external tool such as Microsoft SQL Server Management Studio Express.
management must be handled through an external tool such as Microsoft SQL Server Management Studio Express.
Recovery Model
Depending on the desired behavior, the databases may be set up to use the simple or the full recovery model. For
detailed descriptions on the features of each recovery model, see the MSDN article
detailed descriptions on the features of each recovery model, see the MSDN article
Simple Recovery
For typical Cisco TMS deployments, we recommend using the simple recovery model, which only supports recovery
between backups.
between backups.
With this model, you will back up the database at regular intervals, but omit the transaction log. The database will reclaim
log space to limit file sizes, the database transaction log size is modest, and it does not continue to grow in between
database backups.
log space to limit file sizes, the database transaction log size is modest, and it does not continue to grow in between
database backups.
Full Recovery
Experienced SQL Server administrators with larger Cisco TMS deployments may prefer the additional capabilities and
integrity tools offered by the full recovery model, which supports recovery to any point in time using database transaction
logs.
integrity tools offered by the full recovery model, which supports recovery to any point in time using database transaction
logs.
With this recovery model, the database transaction log file will grow continuously between backups, and can cause the
database run out of space and halt if left unmaintained.
database run out of space and halt if left unmaintained.
Regular database and transaction log backups are mandatory with this recovery model.
Identifying or Changing the Recovery Model
To identify or change the recovery model of your database, see the Microsoft instructions for your version of SQL Server:
Cisco Systems, Inc.
16