2011-12-05 12:10 PM - edited 2015-12-18 01:23 AM
We use SMO to on Linux to protect our Oracle 10gR2 DB. In the past, the average for SMO to put the DB in hotbackup and initiate the snap was about 12 minutes. As of 12/1, the time has jumped up to an average of 1hr,20minutes. Can anyone provide some insight on how to troubleshoot this performance problem.
2011-12-19 01:47 AM
first open a support case with netapp to help you troubleshoot it, they'll ask you to create a diagnostic file of the backup that is taking a long time, as well as the nSanity output from both the servers and the controllers.
to create the SMO diag, right-click over the backup and choose create diagnostics.
to create the nSanity, go to the NOW website, click on toolchest and look for nSanity.
step 2, is to look into the logs and find out if SMO is taking longer on database operations, or during snapdrive operations.
you can find the logs for smo under /var/log/smo
and for snapdrive in /var/log/sd-trace.log (it gets recreated every time sdu is executed)
also if you're in an ITIL kind of organization check if any changes were logged against that server around the 1/12,