During my presentations about TSM for Virtual Environments (TSM4VE) at different customer sites, user events, etc., I noticed that it is often not easy to understand the different transport methods – at a glance. By that, I mean a simple visual comparison between a TSM4VE backup by utilizing the LAN (default), LAN-free backup (SAN) or the HOTADD functionality.
Sometimes, people still think that during the backup, the backup data is temporarily stored on the vStorage Backup Server. That was indeed the case in the old days with VMware Consolidated Backup (VCB) and the dual-hop approach. Nowadays, there is VADP and the backup data stream is single-hop. In all pictures below the TSM4VE metadata stream (purple) is separated from the TSM4VE backupdata stream (green) and isn’t stored on the vBS – it’s backing up directly to the TSM storage hierarchy. In the case of a LAN-backup (NBD/NBDSSL) the backupdata flows “through” the vBS, but it’s not stored – it just “passing by”. In the case of a LAN-free (SAN) backup the backupdata stream skips the vBS altogether.
When you’re running Tivoli Storage Manager for Microsoft SharePoint (aka TSM for SP), most of the times you’ll be backing up a single SharePoint farm. At least, that’s most likely what the software is thinking. In this article is explained how to configure TSM for SharePoint to backup multiple SharePoint farms.
AvePoint is the owner/developer of the DocAve Backup and Restore for Microsoft SharePoint Backup software, which is re-branded by IBM to TSM for SharePoint. That specific version can backup to a TSM server. All other flavors (that can backup to anything but TSM) can be obtained directly by AvePoint.
In TSM v6.3 some new library-related parameters and commands were introduced. One new command was PERFORM LIBACTION, which can be used to define or delete an entire library configuration in one step. One other interesting parameter was LIBTYPE=VTL. It was introduced to improve communications between TSM and a VTL and to utilize the mount performance and scalability enhancements that a VTL offers. I was curious what was the exact logic behind LIBTYPE=VTL. There is some information about this in the TSM v6.3.4 Administrator’s Guide under the section titled “Considerations for using virtual tape libraries” (chapter 7, page 143). It reads:
“There are some considerations for defining a library as a virtual tape library (VTL), including enhancements for performance and setup of your hardware.”
DISCLAIMER: the post below is copied over from the legacy TSMBLOG.org website. For that reason, it’s an old post. I stumbled upon this and checked it out on a more recent TSM server version. It seems that the information provided isn’t valid anymore in recent TSM server releases.
You can limit the maximum number of client sessions that are able to connect to the TSM server simultaneously. Use the ‘SETOPT MAXSESSIONS’ command for this.
Some server options can be updated dynamically (without stopping and restarting the server) by using the SETOPT command, and this is one of them. The corresponding MAXSESSIONS option in dsmserv.opt is changed automatically for you. Just specify the NUMBER of sessions, for example: ‘SETOPT MAXSESSIONS 1000′. The default value is 25.