Table of Contents
Advertisement
Cisco Customer specific TMS Files
These files may be synchronized using any method or tools an administrator chooses. An important
note is the overwriting of files. Some of these files when updated would have the same name as files
on another server. Your synchronization process must take into account which file should be the one
to keep vs. overwriting. This is most critical if you change the email templates or MCU settings
templates. A simple method to address this is to have one server be considered the 'master' and when
updating these template files, have these files overwrite all other copies. Any changes to these files
must be done on the master server. This concern only applies to files that will have duplicate file
names.
A simple example to show how to copy files from one server to another using the built-in utilities of
Windows is shown below. This script can be saved as a batch file and creating a scheduled job to run
it automatically. Create a text file with the following lines, and save as c:\SyncCisco TMSData.bat .
The variables Cisco TMS_DATA_ROOT_SOURCE and Cisco TMS_DATA_ROOT_DEST should be
updated based on your Cisco TMS installation's details
SET TMS_DATA_ROOT_SOURCE=c:\program files\TANDBERG\TMS\wwwTMS\Data
SET TMS_DATA_ROOT_DEST=\\TMSServer2\c$\program
files\TANDBERG\TMS\wwwTMS\Data
xcopy "%TMS_DATA_ROOT_SOURCE%\CiscoSettings\*"
"%TMS_DATA_ROOT_DEST%\CiscoSettings\" /D
xcopy "%TMS_DATA_ROOT_SOURCE%\CompanyLogo\*"
"%TMS_DATA_ROOT_DEST%\CompanyLogo\" /D
xcopy "%TMS_DATA_ROOT_SOURCE%\EmailTemplate\*"
"%TMS_DATA_ROOT_DEST%\EmailTemplate\" /D
xcopy "%TMS_DATA_ROOT_SOURCE%\Image\*" "%TMS_DATA_ROOT_DEST%\Image\" /D
xcopy "%TMS_DATA_ROOT_SOURCE%\Logo\*" "%TMS_DATA_ROOT_DEST%\Logo\" /D
xcopy "%TMS_DATA_ROOT_SOURCE%\Map\*" "%TMS_DATA_ROOT_DEST%\Map\" /D
xcopy "%TMS_DATA_ROOT_SOURCE%\MGCSettings\*"
"%TMS_DATA_ROOT_DEST%\MGCSettings\" /D
xcopy "%TMS_DATA_ROOT_SOURCE%\Software\*" "%TMS_DATA_ROOT_DEST%\Software\"
/D
xcopy "%TMS_DATA_ROOT_SOURCE%\Sound\*" "%TMS_DATA_ROOT_DEST%\Sound\" /D
Using the 'at' program, the batch file can be ran daily automatically. Use the following command at the
command prompt to schedule the job
at 23:00 /EVERY:m,t,w,th,f,s,su c:\SyncTMSData.bat
These files do not change very often, so synchronization does not have to run at a high frequency. A
best practice would be to run an update at most once an hour. The above script illustrates how to copy
files from one server to another. To complete the synchronization, files must be copied from the other
server back to the first as well, to make sure both servers have all files that may have originated on
the other server.
Cisco TMS redundancy configuration and overview
Page 28 of 32
Advertisement
Table of Contents
