Troubleshooting

Data Protection for SQL Server supports you in protecting Microsoft SQL Server databases. Data Protection for SQL Server uses the Microsoft Server Managed Objects (SMO) application programming interface (API), and the Microsoft Virtual Shadow Copy Service (VSS).

About this task

If an error condition occurs during a Data Protection for SQL Server event, you typically start with a symptom, or set of symptoms, and trace the root cause. Problem determination, however, is not the same as problem solving. During the process of problem determination, you might obtain sufficient information to enable you to solve the problem. In some cases, you cannot solve a problem even after you determine its cause. For example, a performance problem might be caused by a limitation of your hardware.
  • Diagnosing problems
    One of the most difficult challenges of troubleshooting in a client-server environment is determining which component is the origin of the problem. VSS diagnostic wizards are available to help you test VSS snapshots on your system. You can determine whether the source of the problem is a general VSS issue, or a Tivoli Storage Manager issue, or a Data Protection for SQL client issue.
  • Resolving reproducible problems
    When a component fails to operate as designed, try to reproduce the problem and capture information about the current operating environment at the time of the error. You can troubleshoot VSS backup and restore operations, VSS and SAN Volume Controller, Storwize® V7000, or DS8000® problems.
  • Resolving problems with IBM Support
    Contact IBM Support for further assistance if you have a problem that you are unable to solve by applying maintenance fixes, reproducing the issue, or using the information in previous topics. IBM Support might request to see some or all of the trace and log files while investigating a problem that you report.