Also all the TSM DB overhead....
        How big is your DB and its cache hit % (but I'm thinking you've
probably already looked into that end)
Are you doing journaling?  (which I personally don't like)
Or INCRBYDATE (again, which I personally don't like)
What about memoryeff diskcache?

I should ask how big those filesystems are... because at some point, the
quantity over powers the mass and you could look into image backups...

You could always utilize snap copy to freeze an image of the filesystems,
then your ~head~ server could become a LAN FREE client, mounting up the
snapped copies and pushing images into TSM (direct to tape).  Do that on the
weekend and incrbydate on week days...

Sadly it's the same old story time and time again...
"it takes a long time to count from 1 to 10M"
        "but they are computers... they can count really fast"
"umm yeah, right..."


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray
Sent: Friday, August 16, 2013 10:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Maximum TSM nodes per server

We are starting to experiencing performance issues on a server that acts as
the "head" for multiple (31 currently) TSM nodes. This server CIFS mounts
multiple departmental filesystems - all in various EMC SAN's.  Each
filesystem is a different TSM node.

The "head" server is running Windows 2012 server with 12GB RAM and
2-quad-core processor.

Anyone out there something like this?  What are the realistic limits?  I
have tried spreading the backup start times as much as I can.

As expected, a lot of the time is spend scanning files - 1-node is >10M
files.

Thoughts?  Comments?  Suggestions?

--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html