Tivoli Storage FlashCopy Manager Internals
4R2P_Lu_Nguyen 2000004R2P Identificações:  dp-exchange flashcopy-manager tivoli-storage-manager dp-sql tsm fcm tivoli performance 1.070 Visitas
When backing up databases using the VSS backup method, you can improve the backup performance by telling FlashCopy Manager to use multiple sessions to communicate with the TSM Server. (This tip assumes you are using multiple disks or LUNs for your database, for example, separate LUNs for your data files and your log files). To do this, set the RESOURCEUTLIZATION parameter in the backup-archive client dsm.opt file. The TSM Performance Tuning Guide (PDF) suggests a value of 5 or 10.
Secondly, when backing up Microsoft Exchange databases, it may be possible to improve performance by skipping the integrity check of the databases. Typically, Microsoft requires an integrity check before a backup is considered "good." However, in Exchange 2010 Database Availability Group (DAG) environments, Microsoft states: "For databases in a DAG that has two or more healthy copies, the database consistency checking step can even be skipped." You should evaluate whether skipping the integrity check is appropriate for your environment. If so, you can tell FlashCopy Manager to skip the integrity check with the SKIPINTEGRITYCHECK parameter.
I don't typically use this space to announce things, since they are already announced through other channels. However, I wanted to let you know about the Early Access and Beta programs for a future release of FlashCopy Manager. This is your chance to not only get a preview of the new features of the future version, but also to make suggestions on how you'd like for future versions to work. Our clients, business partners, and internal IBMers are invited to apply:
4R2P_Lu_Nguyen 2000004R2P 567 Visitas
Microsoft made a number of changes in Exchange Server 2013. With regards to TSM mailbox restore, perhaps the most significant change was the requirement for MAPI clients to use RPC over HTTPS (also known a Outlook Anywhere). RPC over HTTP is no longer supported. When using any new or changed technology, you may encounter some bumps in the road. I've been working with Exchange 2013 for quite some time now, and I would like to share with you a few tips for using mailbox restore with Exchange 2013.
Before you start:
If your environment is configured correctly, mailbox restore will work as with previous versions Exchange. However, if you run into trouble, I suggest the following troubleshooting steps:
4R2P_Lu_Nguyen 2000004R2P Identificações:  problem-of-the-month fcm flashcopy-manager tivoli tsm dp-sql tivoli-storage-manager dp-exchange 613 Visitas
A couple of our clients reported recently that their mailbox restore operations failed intermittently while using Data Protection for Exchange or FlashCopy Manager. Looking at their diagnostic trace (specifically the TraceFileExc.trc file), we noticed FCM was getting a MAPI_E_CALL_FAILED error when it tried to communicate with Microsoft Exchange using MAPI. Long story short, it turns out the mailboxes they were trying to restore contained many folders, and FCM exceeded the MAPI limits in Exchange.
FlashCopy Manager uses Exchange MAPI to perform mailbox restore operations, and it may fail if it has exceeded the limits set by Exchange. To check whether this situation applies to you, look in the event log for Event ID 9646. This Microsoft article briefly discusses this problem for Exchange 2003, but it applies to other versions too. This other Microsoft article details the existing limits and how to increase these limits. objtFolder and objtMessage are the limits that you are most likely to hit, but other limits are possible too. The Windows Application event log will specify which limit you need to increase. After increasing these limits, our clients were able to restore these large mailboxes successfully.
4R2P_Lu_Nguyen 2000004R2P Identificações:  tsm flashcopy-manager performance dp-sql fcm tivoli-storage-manager tivoli dp-exchange 931 Visitas
A couple more FCM performance tips for you. We have released the fix for APAR IC86558 for the TSM Server. It is included in 6.2.5 and 6.3.4. This change allows the TSM Server to manage lots of small files more efficiently in certain situations. For those using Exchange 2010 (which has thousands of 1MB transaction logs), I highly recommend getting this fix. For those running Exchange 2007 and backing up using VSS, I would also recommend this fix. This fix may also help those using FCM to backup their file systems and custom applications, depending on the type of files being backed up.
Secondly, I would like to discuss the BUFFers and BUFFERSIze parameters. For legacy backups, the Data Protection process performs the backups, so these parameters are used. However, for VSS backups, the DSM Agent performs the majority of the transfer to the TSM Server, so you will want to tune the baclient parameters instead. (Be sure to restart the DSM Agent for the changes to take effect). In both cases, though, the default values are the optimal values for most environments.
4R2P_Lu_Nguyen 2000004R2P Identificações:  fcm tivoli flashcopy-manager dp-sql tivoli-storage-manager dp-exchange tsm 1.195 Visitas
FlashCopy Manager contains many components, and writes its data to many different log and trace files. While this helps separate the components so that the logs are easier to read, it can be confusing deciding which logs you need to check in case of a failure. For example, in a typical FlashCopy Manager backup, there are a few distinct phases:
The first step of any problem diagnosis is to determine the phase in which the failure occurred. The most useful log for this step is the tdpexc.log, tdpsql.log, or fcm.log file. Once you know which phase is failing, you will be able to review the appropriate logs to continue your problem diagnosis. The following table contains a high level explanation of the different log files that FCM uses.
Problem Category ---> Log file
Initial Diagnosis ---> tdpexc.log, tdpsql.log, or fcm.log
VSS backup / restore ---> Agent trace (TraceFileAgent.trc)
Legacy backup / restore ---> DP Trace (TraceFileXXX.trc)
MMC GUI ---> Fm trace (TraceFm.trc)
SQL ---> Application Event log
Problems during transfer to TSM ---> tdpexc.log, tdpsql.log, or fcm.log, and potentially API trace (TraceFileXXXAPI.trc)
4R2P_Lu_Nguyen 2000004R2P Identificações:  tsm tivoli-storage-manager dp-exchange tivoli flashcopy-manager dp-sql fcm 716 Visitas
I am a software developer at IBM, working on Tivoli Storage Manager and Tivoli Storage FlashCopy Manager. In the course of my work, I encounter many interesting problems and their innovative solutions. Periodically, I would like to share some of these experiences with you. This blog is intended to be a technical blog, and I hope that it may be useful to others who may encounter similar problems. The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
If you have any topics that you would like for me to discuss in a future blog entry, feel free to let me know in the comments section.