( 2 Votes )

With today's news, IBM is expanding its portfolio and furthering its investments in information and analytics with:

( 2 Votes )

Having checked out an implementation of TSM for Sharepoint, I was surprised to see that backup data was being retained for longer periods than set in the backup plan. I checked the usual places (Server copygroups, expiration processing, etc) but everything seemed in order. I then turned to google and user groups and after many searches I finally stumbled across an answer to the problem. 

This can be caused by two different TSM server settings for the DocAve node.
1.  The node does not have Del Backup set to Yes
2.  The node's txngroupmax is too low Diagnostics:
1. Check the following:
 Query Node F=D for the node in question and ensure the following is set :
      Backup Delete Allowed: Yes

2. Check the actlog for the following
ANR0445W Protocol error on session 1115630 for node nodename (DocAve) - maximum group transaction size exceeded. (SESSION: 1115630) In the case where the node's Backup Delete Allowed is set to No, update the node so that it is set to Yes. In the case where you are getting the delete errors due to maximum group transaction size exceeded, then you need to update the node's txngroupmax.

During a DocAve backup, the data is segmented into 50mb chunks. This is stored individually on TSM as an object. Because DocAve uses the TSM API, the deletion of the old data is done as a single transaction. If the number of objects it is trying to delete is greater than txngroupmax, then the deletion will fail.

For many years, the NetBackup™ product suite has frowned upon technologies that didn’t use full backups as they claimed it impacted the RTO. In a change of face, Symantec now offer both source and target de-duplication in both NetBackup™ and BackupExec™.

This is achieved through the PureDisk™ when storing data in a media server de-dupe pool or a PureDisk storage pool.

For more information see:  http://eval.symantec.com/mktginfo/enterprise/fact_sheets/b-symc_netbackup_7_core_DS_12995286-2.en-us.pdf

EMC also have source and target de-duplication through its acquisition of Avamar and DataDomain.

IBM have released a draft version of the redbook for TSM 6.1.  This discusses the changes made to TSM including command line changes relating to the mov eto DB2.

For more detail, download the readbook at :

http://www.redbooks.ibm.com/redpieces/abstracts/sg247718.html

Ever wondered how to find technical information relating to TSM 6.1? Now you can find it easier with the TSM WIKI http://www.ibm.com/developerworks/wikis/display/tivolistoragemanager/Home

IBM have launch a SAS Drawer for the nSeries system.  For more information see http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS109-632&open&cm_mmc=5733-_-n-_-vrm_newsletter-_-10207_135540&cmibm_em=dm:0:16661896

NetApp have announced the integration of NetApp® SnapMirror® to Tape and SnapshotTM technologies with IBM® Tivoli® Storage Manager (TSM) 6. As a result, NetApp and IBM customers using TSM 6 will experience enhanced backup and disaster recovery capabilities for data stored on NetApp FAS and IBM System Storage® N series storage devices.

TSM 6 leverages NetApp SnapMirror to Tape technology, enabling customers to use TSM Network Data Management Protocol (NDMP) support to back up FAS and IBM N series volumes directly to tape or across the network to any tape device managed by TSM. This can be done without having to scan each volume to find new and changed files, helping reduce the amount of time customers need to back up their FAS and IBM N series systems, which can make the backup process up to 12 times faster.

IBM have announced the latest version of its Storage Manager family of products.

TSM is a highly scalable solution that enables the protection of data across the heterogeous data center. TSM 6.1 takes scalability to the next level by introducing DB2 as the backend database for TSM.

 

The number of times that someone has declared tape "dead" probably numbers in the thousands. Users that deploy disk consistently report that their success ratios for backups and restores climb to 95% or higher. Yet companies should still view disk's place in the backup process as a temporary resting place for data and not a permanent one.

 

In the current climate businesses are freezing or reducing budgets thereby asking IT to ‘do more with less'.  In order for the business to retain market share, the IT systems need to provides business services that are more efficient than the competition.