TSM Studio (59)
Checking for Successful Backups in TSM Studio
In this article I will show three ways that you can verify that your Backups were successful using TSM Studio.
The first is from the Events Table
To view the events table goto the Monitor Category and then double click on the Events Dataview
Select the Date Range
The events data is displayed
There are a number of other related views in this Category such as Missed and Failed Backups
View the Backup output from the Summary Table
To view the events table goto the Monitor Category and then double click on the Summary Dataview
Select the Date Range
Use the Filter Backup to just show Backups
Choose Backup
Filter the Successful Column to display Backup Jobs that have failed
A list of all the Failed Backups will now be displayed
The third way to check is to look at File Spaces
The file spaces dataview can be found under the Storage Category
Check the Backup Start Date and the Backup End Date. If the Backup End Date is less than the Backup Start Date or the Backend End Date is blank then there is a problem with the backup of the Node owning this filespace
We also have a specific Dataview to show all suspect File Spaces, goto to teh Troubleshooting Category and select File Spaces where Backup End Date is less than Backup Start Date
*** Disclaimer ***
All the articles that I have written are from my own personal experiences using TSM for the past 15+ years. TSM is a diverse product that can be setup and deployed in many ways. Before using any of the methods in the articles, ensure that you use due diligence to test that all steps will work as described in your environment.
If you have comments, like help with the contents in one of the articles or would like to see an article on a particular TSM topic please send me an email at gelliott@spiritsoftware.biz. You are welcome to use these articles on your own sites as long as you have a link on the article back to this site
Example: Written by Spirit Software Solutions
Graeme Elliott CEO,
Founder and Chief Architect
Spirit Software Solutions
All Articles are copyrighted by Spirit Software Solutions
*** LEGAL STUFF ***
Direct, incidental, consequential, indirect, or punitive damages arising out of your access to, or use of, the site and articles within. Without limiting the foregoing, everything on the site is provided to you ‘AS IS’ WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON INFRINGEMENT. “Please note that some jurisdictions may not allow the exclusion of implied warranties, so some of the above exclusions may not apply to you. Check your local laws for any restrictions or limitations regarding the exclusion of implied warranties.”
Changing the Date on a TSM Server
If you change the date on the underlying Operating System that your TSM Server is running on you will need to run the ACCEPT DATE command. If TSM is up when the date change occurs then you can login to the TSM Server using the Admin CLI or TSM Studio ( example at the end of this article) and run the ACCEPT DATE command.
If your server was down and your windows TSM Server service will not start. Check the event log or console messages for the following error
TSM Server Error: Server: SERVER_NAME ANR0110E An unexpected system date has been detected; the server is disabled. Verify the system date and use the ACCEPT DATE command to establish the current date as valid.
If you are unable to access the server from the ADMIN CLI then go to the command prompt or unix shell, change to the directory where dsmserv.exe (just dsmserv on unix) is installed and run it. When you see the above message enter ACCEPT DATE and once the new date has been accepted run the HALT command to stop TSM and start the TSM Server in the normal way for that Operating System.
Why do you need to do this
If someone has accidentally changed the Operating System date to a future date and the expiration process runs then a lot of data could be lost.
If you can access the TSM Server from TSM Studio then goto to the COMMANDS menu and select ACCEPT DATE
How can I see what files have been restored using TSM Studio
Firstly for the TSM Instance to be able to capture information about restored files the following option must be enabled in the dsmserv.opt and the TSM instance restarted
REPORTRETRIEVE Yes
Then in TSM Studio you can use the Client Node–>Show Restored Files dataview to show restored file for a given date rangle
Restoring a Client Node from Another Client Node
It is possible to impersonate a client node on a different node and there are 2 ways to do this.
The first option is to just change the nodename to match the impersonated name, this requires that you know the password of the nodename to be impersonated.
Either change the nodename in the dsm.opt file to the nodename to be impersonated
or change the nodename in the Backup-Archive Client by going into the preferences
and Changing the Node Name
Alternatively you can use the ASNodeName option. This requires specifying the ASNodeName option either in the dsm.opt file or using the Backup-Archive client and also granting access on the TSM Server to impersonate this Node Name.
Either modify the dsm.opt file as follows
or go into the preferences dialog as above and change the As Node Name field
Now grant the Node Test1 access to impersonate Test2 on the TSM Server.
Open the Client Nodes dataview in the Configuration category in TSM Studio and choose the node that is to be impersonated. Right click to bring up the Commands context menu and choose Grant Proxy Access to and select the Node that will impersonate this node
TSM Studio Server (3)
TSM Studio Server Security
As of TSM Studio Server version 2.9.1.0 security has been tightened up and no longer stores any security information in the registry.
The default logon to TSM Studio Server is now admin with a default password of password, (Domain field should be blank otherwise TSM Studio Server will assume it is a windows userid).
We strongly advise changing the admin password using the following procedure.
To change the password for the inbuilt admin userid use the Security–>Change Admin Password
Security in TSM Studio Server is now defined by assigning role(s) and Windows groups to a TSM Studio Server security group.
The TSM Studio Server security system will automatically create a group named Admins that has access to all functions in TSM Studio Server, the first time it is loaded it will look for the old group definitions in the registry and load them into this group otherwise it will populate with following default groups Administrators, Domains Admins and TSMStudioAdmins.
Also two roles will be created, one called Administrators which is assigned to the Admins Server group and one called Operational Report Viewer for allowing access to the Operational Report Viewer.
To access TSM Studio Server Groups select Security–>Groups
To modify the Admins Group Double Click or select edit from the Toolbar
Add Windows Group that should have admin access to TSM Studio Server, One Group per line
Microsoft SQL Server settings for TSM Studio Server
If SQL Server is running on the same Server as the TSM Studio Server service then we recommend 12GB of memory as a minimum to ensure the healthy running on TSM Studio Server.
By default SQL Server will be configured to use all available memory this will need to be changed so that there is enough free memory for TSM Studio Server to function. It is recommended that SQL Server be given 4GB of memory and the other 8GB is left available for TSM Studio Server.
To change the default memory settings in SQL Server. Start up SQL Server Management Server right click on the server and select properties
Select Memory and then enter 4096 into the Maximum server memory field
Performance Tuning TSM Studio Server
In TSM Studio Server 2.9.011 and above there are a number of added enhancements to help tune TSM Studio for you environment.
The first area to check is on the Concurrency Tab of the TSM Studio Server properties dialog which can be accessed from Configuration–>Properties as shown here
The main setting to check here are Concurrent Reports and Concurrent Collector Threads. Report creation can consume large amount of memory so it is recommended to keep this number low.
Also some of the collections can consume a large amount of transaction log space especially the activity log collector. Each collector can be individually tuned. Goto Configuration->Collection schedules and edit the Activity Log collector and change the Concurrent Collectors to a small number (less than 5 )
Also check out the below link for SQL Server memory settings
https://spiritsoftware.biz/knowledgebase/microsoft-sql-…-studio-server
Dataviews (10)
Alternate Row Colors
Alternate Row BackColor Example
Using the Alternate Row Color feature can make the data easier to read. After opening a dataview right click to bring up the dataview context menu and select the Alternate Row BackColor option or select it from the Toolbar and the color you wish to use
Customizing the Columns
The columns in a Dataview can be customized in a number of ways,
- Columns can be moved
- Columns can be hidden
- Column Display Text can be changed
- The alignment can be changed
- The format of the data can be changed
To modify the columns right click on the dataview to display the dataview context menu and select columns ( or choose columns from the menu bar ). A dialog will be displayed showing a list of all the available columns and their settings.
Use the up and down arrow keys on the menu to change the order the columns are displayed.
To Hide a field click on the Hidden field for the column to hide.
To Change the Display text for a field click over the text in the Column Display Text field.
Use the Alignment Column to select the alignment for that column.
The Format field is used to the control how the column displays its data for example.
N0 defines a number field with no decimal points.
N2 defines a number field with 2 decimal points.
G defines a date field and shows just the date.
g defines a date field and shows the date and time
These are standard dotnet formats. If you want to have the data displayed in a different way let us know and we will help you format the data the way you want to see it.
Displaying Line Numbers
This will display Line Numbers as shown below
Sometimes it is handy to be able to the see line numbers in a dataview.
Right click on the Dataview and select the Line Numbers option from the Dataview context menu ( or from the Main Menu Bar ) to disable/ enable line numbers.
To Enable Line Numbers click on the Line Numbers option from the Dataview Context Menu.
Exporting the Data
From time to time you may wish to export the data from a dataview. TSM Studio provides a number of formats that you can use to export to Excel, PDF, XPS and XML. .
Right click on the Dataview to display the context menu for that Dataview and select from the available Export Options, then choose the ourput file name.
Data exported to XML can be reloaded later using the Load from XML option on the Dataview context menu, this allows you to work offline if you wish.
Filtering the Data
TSM Studio provides extremely powerful filtering capabilities.
At the top of each column on the right hand side where the title is displayed you will also notice a small filter icon. Click on this icon to display the filtering dialog for that column. The icon is only displayed when the mouse is positioned in the column header.
Filtering Examples
Show all rows where Devclass = ‘DISK’
Show all Rows where Stgpool Name is either DISKPOOL or BACKUPPOOL.
TSM (10)
Expiration
Expiring old backup and archive data from TSM is controlled by the EXPINTERVAL in your dsmserv.opt file.
EXPINTERVAL=24 specifies to run the expire process every 24 hours.
EXPINTERVAL=0 disables automatic expiration.
Removing old data from TSM can be run manually using the expire inventory command. Data is expired using the “Management Class” definitions that you have set on your files or if none are defined then the defaults for the policy set are used. ( I will discuss policy sets in an upcoming article )
In version 5 expiration can only be run system wide, in version 6 you can run the expire inventory command on individual nodes, this is useful when changing management classes on individual nodes.
I recommend that you set the EXPINTERVAL to 0 so that you can control at what time this process runs and the setup an admin schedule to run the expire inventory command
Collocation Group TroubleShooting
We suggest you read the following Article on Collocation before reading this Article –> Read Here
As noted in the article on collocation. The main problems you will come across with collocation is running out of scratch tapes andor a large number of tapes in a filling status. The main cause of this is having a storage pool with a collocation method of Group and then having no collocation groups or nodes not in collocation groups.
Using TSM Studio go to the Trouble Shooting category and open the Nodes not in Collocation Group dataview.
To Add a Node(s) to a Group simply right click the select Add to A Group
After putting all your nodes in a group, You will now need to move the data off the current tapes so that TSM can collocate the nodes and their data.
There are a number of ways to do this and here are two of them
1. To do this use the Move Data command on each tape and move the data back to the primary disk pool so that the migration process can move the data back to tape using the collocation you specified.
2. Or use the Move Data command to move the data to the same storage pool as the tape is already in, TSM will then move the data from the selected tape and collocate the data with nodes from the same group on other tapes.
Using TSM Studio to run the move data command. Open the Volumes Dataview from the Libraries and Volumes category Right Click on the Tape and Choose Move Data
Choose the Storage Pool to move the data to
Installing the Administrative CLI – Windows
The Administrative Client is part of the normal windows backup-archive client install but by default it is not installed. You will need to apply a custom install as shown below:
1. Start the Tivoli Storage Manager Client InstallShield(R)
2. Choose the Destination Folder
3. Choose Custom Setup as the Setup Type
4. IMPORTANT – Make sure that you select the Administrative Client Command Line Option as shown below and choose ‘ run all ‘ from my computer
5. Click the Install option
6. To verify the installation, verify the existence of dsmadmc.exe in the C:\Program Files\Tivoli\TSM\baclient directory
You may come across an error if the paths are not correctly set up. If you see the following message when starting the administrative cli program or when testing a TSM Server connection in TSM Studio, follow the suggested action below.
ANS0101E Unable to open English message repository ‘dscenu.txt’
This error is a result of the administrative cli program, “dsmadmc.exe”, unable to find the message file.
To start, you can check if the dscenu.txt file exists in the c:program filestivolitsmbaclient directory ( assuming, you installed the TSM client in the default location ).
If the file exists, try adding the following environment variable
DSM_DIR=C:\Program Files\Tivoli\TSM\baclient
*** Disclaimer ***
All the articles that I have written are from my own personal experiences using TSM for the past 15+ years. TSM is a diverse product that can be setup and deployed in many ways. Before using any of the methods in the articles, ensure that you use due diligence to test that all steps will work as described in your environment.
If you have comments, like help with the contents in one of the articles or would like to see an article on a particular TSM topic please send me an email at gelliott@spiritsoftware.biz. You are welcome to use these articles on your own sites as long as you have a link on the article back to this site
Example: Written by Spirit Software Solutions
Graeme Elliott CEO,
Founder and Chief Architect
Spirit Software Solutions
All Articles are copyrighted by Spirit Software Solutions
*** LEGAL STUFF ***
Direct, incidental, consequential, indirect, or punitive damages arising out of your access to, or use of, the site and articles within. Without limiting the foregoing, everything on the site is provided to you ‘AS IS’ WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON INFRINGEMENT. “Please note that some jurisdictions may not allow the exclusion of implied warranties, so some of the above exclusions may not apply to you. Check your local laws for any restrictions or limitations regarding the exclusion of implied warranties.”
How can I enable VSS Snapshot support on only one windows drive
It is possible to enable VSS on a per drive basis by using the following in the dsm.opt file
INCLUDE.FS C: SNAPSHOTPROVIDER=VSS ( Change C: to the drive letter you require )
Helpful TSM SQL Commands (29)
Show the number of Windows Clients on a TSM Server
TSM v5
SELECT COUNT(*) FROM NODES WHERE PLATFORM_NAME LIKE ‘WIN%’
TSM v6 and above
SELECT COUNT(*) FROM NODESVIEW WHERE PLATFORM_NAME LIKE ‘WIN%’
Show all volumes in an error state
SELECT * FROM VOLUME WHERE UPPER(ERROR_STATE) = ‘YES’
Show the number of Linux Client Nodes on a TSM Server
TSM v5
SELECT COUNT(*) FROM NODES WHERE PLATFORM_NAME LIKE ‘%LINUX%’
TSMv6 and above
SELECT COUNT(*) FROM NODESVIEW WHERE PLATFORM_NAME LIKE ‘%LINUX%’
Show volumes with write errors
SELECT * FROM VOLUMES WHERE WRITE_ERRORS>5 (Use a number relevant for your environment, this should be 0 if using a VTL)
NOTE: The > symbol when using the TSM Admin CLI is also used for redirection. To ensure it is used for correct intention here as a GREATER THAN sign remove the spaces on either side of the > symbol
Show the number of Solaris Client Nodes on a TSM Server
TSM v5
SELECT COUNT(*) FROM NODES WHERE PLATFORM_NAME LIKE ‘%SOLARIS%’
TSMv6 and above
SELECT COUNT(*) FROM NODESVIEW WHERE PLATFORM_NAME LIKE ‘%SOLARIS%’
