ā10-11-2011 08:48 AM - edited ā03-17-2019 10:33 PM
Hi all,
Somebody know how is the procedure to replicate the config and SQL database between two TMS.
We have one TMS as a primary, and we want the second TMS as a backup (with the services down). We are thinking to do a replication once a week but we donĀ“t know how to do.
We are reading a lot of pdf and installation guide from Cisco / Tandberg, but is impossible to understand very well how to do..... someone have a cookbook (for dummies please!!!)??
Thank you in advance
Juan Granata
Solved! Go to Solution.
ā10-11-2011 09:05 AM
Juan,
As far as I am aware, TMS does not support replicating the SQL database. You can however point multiple TMS servers to the same database.
Thanks,
Justin
ā10-11-2011 09:19 AM
First of all is there a specific reason that you want to use this kind of deployment?
Anyhow your exact deployment wish is not mentioned in the "TMS Server Reduncancy Config guide".
You could also use a sql cluster and two tms connection to it, or if capable, let a virtualization enviroment take care that your TMS does not go down.
To bring a TMS up in case of a failure you need to main parts, the MS SQL DB backup and also copy of the
TMS Agent backup file. I am not aware if you have an IT department, but they might be a good source for help.
short overview what to take care of:
* windows server itself
* services like iss, ms sql, ...
* requiements for tms install (like .net)
* tms installation
* sql db (storing all generic tms stuff)
* opends ldap db (=TMS Agent)
If the directory structure is different you might need to fix the sql file (see sql doc below).
The different ip address / hostname of your spare server might be a problem.
Did you know / read the "TMS Server Reduncancy Config guide"
I would recomend doing so, this shall answer some of your questions or bring up new :-)
Some usefull doc:
Please remember to rate helpful responses and identify
ā10-11-2011 09:05 AM
Juan,
As far as I am aware, TMS does not support replicating the SQL database. You can however point multiple TMS servers to the same database.
Thanks,
Justin
ā10-11-2011 09:19 AM
First of all is there a specific reason that you want to use this kind of deployment?
Anyhow your exact deployment wish is not mentioned in the "TMS Server Reduncancy Config guide".
You could also use a sql cluster and two tms connection to it, or if capable, let a virtualization enviroment take care that your TMS does not go down.
To bring a TMS up in case of a failure you need to main parts, the MS SQL DB backup and also copy of the
TMS Agent backup file. I am not aware if you have an IT department, but they might be a good source for help.
short overview what to take care of:
* windows server itself
* services like iss, ms sql, ...
* requiements for tms install (like .net)
* tms installation
* sql db (storing all generic tms stuff)
* opends ldap db (=TMS Agent)
If the directory structure is different you might need to fix the sql file (see sql doc below).
The different ip address / hostname of your spare server might be a problem.
Did you know / read the "TMS Server Reduncancy Config guide"
I would recomend doing so, this shall answer some of your questions or bring up new :-)
Some usefull doc:
Please remember to rate helpful responses and identify
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide