• 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.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    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.

TSM for Sharepoint

Jeff_Jeske

ADSM.ORG Senior Member
Joined
Jul 17, 2006
Messages
483
Reaction score
7
Points
0
Location
Stevens Point, WI
Website
http
Another follow up.... I've got the environment configured and backups are running smoothly into TSM on Sata. TSM version 5.4.3.2 with TSM for SharePoint V6.1.

The main thing I do not like about the software is data pruning. Apparently DocAve doesn't know the difference between an active or inactive file. They put a time to live on data based on the backup date. If you set pruning to 60 days it will get rid of anything 60 days old whether its active, inactive, or even the only existing version.

Therefore to expire/prune data in TSM/Sharepoint you need to schedule full backups. Here is a document that offers a bit more info on this:
http://www-01.ibm.com/support/docview.wss?uid=swg21393627
 

Jeff_Jeske

ADSM.ORG Senior Member
Joined
Jul 17, 2006
Messages
483
Reaction score
7
Points
0
Location
Stevens Point, WI
Website
http
Performed bare metal restore of the DocAve server today. A simple TSM Baclient backup doesn't provide recoverability. You have to run a built in "System Backup" feature then backup the files that the system-backup generates.

These files can then be used to recover the DocAve database after a BMR. Not a big deal but something I thought I would share.

... also tested out Data Coalescing which is known as a sythetic full backup. Data coalescing adds incremental backups to the index of the last full backup. This reduces load on the SharePoint DB server by not having to send every piece of data across the wire. It also reorganizes the data within TSM to speed recovery in the event of a full server DR. The process worked as designed but took longer than a normal full backup. The process freed up resources on the DB server and shifted it to the TSM and DocAve servers.

Our monthly full backup is transparent to end users. That combined with the fact that a full DR would happen at the SQL DB level I don’t plan to schedule any data coalescing jobs. We have ours configured for 60 day pruning with a last friday of the month full backup.
 

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: 22 19.5%
  • Keep using TSM for Spectrum Protect.

    Votes: 67 59.3%
  • Let's be formal and just say Spectrum Protect

    Votes: 15 13.3%
  • Other (please comement)

    Votes: 9 8.0%

Forum statistics

Threads
31,852
Messages
134,944
Members
21,832
Latest member
dataguy81
Top