Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Deployment best practices
Database maintenance planning
Cisco TMS and Cisco TMSPE both create databases according to the default settings of the SQL server.
The databases are:
The databases are:
n
tmsng (Cisco TMS)
n
tmspe (Cisco TMSPE main)
n
tmspe_vmr (Cisco TMSPE Collaboration Meeting Rooms)
n
tmspe_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.
Database 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
For 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.
recovery 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.
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.
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.
capabilities and 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.
cause the 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:
SQL Server:
n
n
n
(SQL Server 2008)
Cisco TelePresence Management Suite Installation and Upgrade Guide (14.5)
Page 19 of 56
Deployment best practices