If you’re new to IBM Tivoli Storage Manager (IBM TSM from here on), you may be curious as to why there’s so much love for this particular method of data storage and backup. Well, there are several reasons for this, that should illuminate its benefits and the various features putting it ahead of the competition.

Backup is probably one of the two main reasons people look into data storage management software, and this is arguably one of IBM TSM’s strongest features. IBM have implemented what they call a “revolutionary” progressive incremental backup system, that allows you to continuously backup new and changed files, while the old ones are kept as as single copy. Not only is this faster, it saves space, and you’ll soon find that it means you can restore backups and sift through backup data without the hassle of digging through countless identical copies of the same file.…

If you have been trying to upgrade TSM 5 to TSM 6 & received the following error:  “Format Completed with Return Code 499” Then follow the steps below, which I have got from IBM article to fix the problem. I have used these steps & they have worked for me & they should work for you too.

If this is not an upgrade & you started with a clean install, but you still got a missed up database then follow up the steps below & then follow up: “How do you remove a server instance without uninstalling the TSM server?” which will remove the corrupted instance & database & you will be ready for trying to initialize the instance again.…

Today while installing TSM 6.1.2 for one of my client I had end up with a crashed instance of TSM. I did not feel to reinstall TSM & wanted to delete that TSM instance & its database. Below the steps I have used to do just that:

1) Open a DOS command prompt and run “db2ilist”. This will list the TSM instances that are defined to DB2.

2) From the DOS command prompt issue “db2idrop <instance name>”. So if the instance you want to remove is “SERVER1” you would issue “db2idrop server1”

3) Open the registry to HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server. Here you will find the instance. Remove the instance directory. Do not remove HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Server itself.

NOTE: Before making any registry changes it is always advised to export the registry incase you need to recover.…

You might get into the situation where you have to quickly clone your production database to a different server for some release management. In most situations, you will not be able to take that database down, neither have the time to do backup & restore so online transaction consistent database cloning will be a great tool for you. The capability of IBM VDS & DS8000 FlashCopy & vShadow with a bit of scripting can provide you with just that. Below is a small batch files with explanation which can do just that.

======== fcm.bat ========

You might get into the situation where you have to quickly clone your production database to the same server for some release management. In most situations, you will not be able to take that database down, neither have the time to do backup & restore so online transaction consistent database cloning will be a great tool for you. The capability of IBM VDS & DS8000 FlashCopy & vShadow with a bit of scripting can provide you with just that. Below is a small batch file with explanation which can do just that.

==============Fcm2.bat================

del bc1.xml sc1.cmd

C:\fcm2\vshadow.exe -p -t=bc1.xml -script=sc1.cmd y:

echo c:\fcm2\fcmmount.bat >> sc1.cmd

c:\fcm2\vshadow -i=c:\fcm2\bc1.xml

c:\fcm2\sc1.cmd

===============================

===========fcmmount.bat==========

c:\fcm2\vshadow -el=%SHADOW_ID_1%,D:\mytest

c:\fcm2\vshadow -bw=%SHADOW_SET_ID%

====================================

In order for the script above to work you have to create the two batch files with the same names shown above each.…

Although cloning a boot from SAN LUN & Database LUNs to another server or to the same server still not integrated into the current FCM release & planned in the future, its achievable with a bit of scripting, which might require DSCLI access for certain operations. This section will focus on cloning & show how to achieve few cloning scenarios even before it’s fully integrated with IBM Tivoli FlashCopy manager, which is planned as a part of future release.

:

Back to: IBM Tivoli Storage FlashCopy Manager Tutorial Index…

Tivoli FlashCopy Manager offers as great amount of options when it comes to restore as it has for backup. This section will cover the most used ones. The type of features & destination types available will be limited if you don’t have TSM integration. The features & destinations which is only available with TSM integration will be pointed as they are covered.

1-     To start the IBM Tivoli FlashCopy Manager in a stand alone server all you have to do is to click on the IBM Tivoli FlashCopy Manager on the desktop or your program files menu. If you are running in a clustered environment, then you would want to to ensure you start your FCM with the /sqlserver parameters. An example of the command to run the FCM GUI in a clustered environment with an SQL Cluster  name sqlsrvpoc is:

C:\Program Files\Tivoli\FlashCopyManager\flashcopymanager.msc…

Tivoli FlashCopy Manager offers a great amount of options when it comes to backup. This section will cover the most used ones. The type of features & destination types available will be limited if you don’t have TSM integration. The features & destinations which is only available with TSM integration will be pointed as they are covered.

1-     To start the IBM Tivoli FlashCopy Manager in a stand alone server all you have to do is to click on the IBM Tivoli FlashCopy Manager on the desktop or your program files menu. If you are running in a clustered environment, then you would want to to ensure you start your FCM with the /sqlserver parameters. An example of the command to run the FCM GUI in a clustered environment with an SQL Cluster  name sqlsrvpoc is:

C:\Program Files\Tivoli\FlashCopyManager\flashcopymanager.msc…

Tivoli FlashCopy Manager can be operated using the GUI Interface as well using Command line. Actually one of the greatest enhancements in IBM Tivoli FlashCopy Manager v2.1 when compared to Tivoli Copy Services & Advanced Copy Services is the great fresh Graphical Interface & the easiness of backup & restore operations. Below are few snapshots of the new amazing IBM Tivoli FlashCopy manager interfrace:

Back to: IBM Tivoli Storage FlashCopy Manager Tutorial Index…

If you have IBM Tivoli Storage Manager in your environment and you have a Tivoli Data Protection license for the server you have installed Tivoli FlashCopy Manager on, you will need to go through the IBM Tivoli FlashCopy Manager TSM Configuration Wizard as shown below, else you will want to look at the IBM Tivoli FlashCopy Manager Local Configuration Wizard as illustrated in Section 6.1.

1-  Start IBM Tivoli FlashCopy Manager: start => All Programs => Tivoli FlashCopy Manager

2- Expand the menu in the left side of IBM Tivoli FlashCopy Manager and browse to Wizards as showing in the image below. Double click on the TSM Configuration.

3- Check Mark SQL Server and then hit next.

4- On the Requirements Check Page ensure all the status is passed.…