• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

DocAve / TSM for Sharepoint configuration question(s)


Active Newcomer
Hi all,

I've started investigating a problem with our sharepoint environment backups currently where the DocAve software is using a single TSM node to backup across multiple DocAve agents.

As the backup plans start, sessions are triggered on the server, the next plan starts and the previous session stops a new session for each is generated.

This happens until the backup plan is complete, I'm thinking that because of this it's not only slow, but also impacting the ability to prune the TSM DB.

So what I would like to know:
1. Is it normal in a docave environment to have a single TSM device (node) configured for multiple agents?
Eg. AgentA, AgentB, AgentC connect to TSM from a single docave cluser using TSM nodename: avepoint
2. If I create a new node for each agent and correct the plans in docave - will I see an improvement in speed and retention?
3. Our environment uses our default mgmtclass (VE:7, VD:1, RE:31, RETO:90) rather than the docave preferred setting and I want to correct this, any idea on what impact this will have on the existing data to go to VE1, VD:0, RE:0, RETO:0 ?

Lastly: would this scenario likely cause excessive DB growth in a TSM 5.5.4 environment? I ask this as my DB grows approx 5gb every few days and the server itself is only for devtest + avepoint (not doing that much work from other nodes) ?

Thoughts help?

As always appreciate any input :)

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 14 17.1%
  • Keep using TSM for Spectrum Protect.

    Votes: 52 63.4%
  • Let's be formal and just say Spectrum Protect

    Votes: 9 11.0%
  • Other (please comement)

    Votes: 7 8.5%

Forum statistics

Latest member