TMS appliance capacity?

[Jlatessa]

Hello,

What is the suggested max capacity on the TMS appliance?
What are the spec's on the box? Processor and hard disk capacity wise?

[Jlatessa]

alright, answered my own question. I truly am awesome.
Stand alone appliance:
PROCESSOR & MEMORY
Intel® Pentium® 4 LGA775 CPU (Max. Intel® Pentium®
4 LGA775 CPU (Max. 3.6GHz with 800MHz FSB
and 1MB Cache)
240-pin DIMM x 2, support Max. 2GB DRRII 400/533 memory


Recommendation to upgrade to external database with 100 or more endpoints.

[Conquest_Tsi]

Hey mate,

We have been using the appliance for the past year with 20 or so endpoints. Has been going well apart from some IIS issues whcih randomly poke up.

We have since purchased a dedicated server and plan to host the TMS DB on our SQL cluster and use the appliance as a failover/redundant.

[DRI]

Hey mate,

We have been using the appliance for the past year with 20 or so endpoints. Has been going well apart from some IIS issues whcih randomly poke up.

We have since purchased a dedicated server and plan to host the TMS DB on our SQL cluster and use the appliance as a failover/redundant.

Having your TMS sw on a dedicated server and external SQL cluster is cool but the TMS Appliance was not intended or can be used in a failover/redundant setup as you describe above. I recommend you refer to the following documentation that discusses the various redundancy methods that can be used with TMS.

http://www.tandberg.com/collateral/documentation/Installation_Sheets/TANDBERG%20Management%20Suite%20-%20Redundancy%20Configuration%20and%20Overview.pdf

BTW, is the reason your going to a dedicated server and external SQL because of the number systems are growing in your TMS? If not, then the TMS Appliance should be more than sufficient for what you have, i.e. designed and intended for >100 systems.

[Sean Lessman]

TMS Appliance should be more than sufficient for what you have, i.e. designed and intended for >100 systems.

Greater than 100, or less than? :)

Sean

[DRI]

Greater than 100, or less than? :)

Sean

My bad...less than 100 :embarrass

[Conquest_Tsi]

Having your TMS sw on a dedicated server and external SQL cluster is cool but the TMS Appliance was not intended or can be used in a failover/redundant setup as you describe above. I recommend you refer to the following documentation that discusses the various redundancy methods that can be used with TMS.

http://www.tandberg.com/collateral/documentation/Installation_Sheets/TANDBERG%20Management%20Suite%20-%20Redundancy%20Configuration%20and%20Overview.pdf

BTW, is the reason your going to a dedicated server and external SQL because of the number systems are growing in your TMS? If not, then the TMS Appliance should be more than sufficient for what you have, i.e. designed and intended for >100 systems.

Please elaborate, I cant see why not it cant be used in a warm redundant setup, surely the appliance can point to an external SQL database?

Not only will we hit near 100 in the coming year but also ease of management and admin as we will merge TMS into our server admin team for them to look after, update, backup etc Our VC is starting to become quite mission critical and the appliance just dosnt fit into our SOE.

[Jlatessa]

The appliance is not supported with an external SQL database. I can't speak on how feasible it actually is having never attempted it. As far as "warm redundancy" I'm sure you could always port your external SQL DB to the appliance box for local SQL but if VC is becoming quite mission critical there are much better solutions.

We run our corporate TMS fully redundant with the TMS servers behind a pair of redundant load balancers and an external SQL cluster.

[Conquest_Tsi]

Hey Buddy, thanks for your reply.

Did u design/manage these servers urself? Interested to know more on your setup.

[DRI]

Please elaborate, I cant see why not it cant be used in a warm redundant setup, surely the appliance can point to an external SQL database?

Not only will we hit near 100 in the coming year but also ease of management and admin as we will merge TMS into our server admin team for them to look after, update, backup etc Our VC is starting to become quite mission critical and the appliance just dosnt fit into our SOE.

To 'elaborate', it simply wasn't designed nor intended to be used this way. However, I strongly suggest you refer to the Tandberg document in my thread above. What Jlatessa describes as far as his redundant setup is clearly spelled out in this document :)