EMC networker Module for Microsoft Applications and DBCCs- DB maintenance

Hi theer,

There was some time ago a similar post about the SQL DB's consistency checks, please take a look here:

https://community.emc.com/message/497613#497613

Let us know if you need any further informaiton.

Thank you.

Carlos.

Thank you for helping, but that clearly states that the issue is not addressed in the software in the last replay on that chain, which means we have to find solutions to do these checks directly prior to running the NNM backups.

"NMM does not perform any consistency check with SQL backups."

Unless a database has a consistency check completed on it, you might be backing up a corrupted database, which is useless.  We also can't always rely on other teams or applications to ensure the backup the systems happens.  As a DBA, it is my job to ensure we are properly backing up the systems.  Sometimes we are even required to prove to auditors how we ensure these backups are proper, so we have to build support around these processes.

Her is what I want to do:

I need tyo split the DBCC jobs from the backup step.  On success, I want to go to a step to execute the backups through NMM.  I need to remotely kick off the process, have the step wait until the process finishes, and report back to SQL Agent that it was successful or not.

Right now:

1. We can't run DBCCs as part of the backup.

2. We can only start the NMM backups without reporting the backups finish or not.

Without these steps, we can't use this product to backup SharePoint from a Database perspective.

No takers on this?  I would love to hear about other admins that need to act as the DBA.  Thx.

The only thing I can say about NMM is that we avoid using it. When it comes to SQL, file or exchange backups the old backup modules are far better and more stable than NMM 2.2.1.

I just hope that NMM 2.3 which should be out next week, is going to be more like the old modules regarding backup, restore and simplicity.

Johannes

SlinkTMP,

I am sorry for the delay - I just saw your post today.

I do not have an answer for you at the moment, but I will research it today and get you the information for the SQL consistency checks. It is my understanding that NMM DOES perform the consistancy check, but I want to 100% before I answer.

As for NMM being unstable, I have found that it is a matter of properly tuning NMM in order to ensure it works well in your environment. I have serveral customers that have installed NMM and it has resolved issues with Exchange and SQL back ups.  But it DOES require some fine tuning.

I will get the information together for you and get back to you by the end of the day today.

Mark

OK - I have done some checking and here is the response I received:

"NMM 2.2.x does not provide an option to run consistency check on SQL databases.  It does that for Exchange only.  NMM 2.3 will be the same.  NMM 2.4 will have NMSQL module embedded in it which does provide –J option.  So it will be possible with NMM 2.4."

So at this point there is no consistency check available for MS SQL with NMM.

Thank you Mark.  I am glad to hear that the original post was right, but this still doesn't address the other problems we are having.  Our SharePoint business teams have a need to use NMM for backing up the SP environment.  That includes our databases.  We have no problem with using NMM for the backups without the consistency checks, but we have to be able to use SQL Server Agent Jobs to call this with error checking.

Here is what we need or we are looking for:

• How do I remotely call the NMM module to run and return an error code (success or failure).  All we seem to be able to do is call the NMM and as soon as it does, it starts it and moves to the next step.  This is no good.  We need to know that it starts and finishes.  Once we have a success of the backup using NMM only then can we move to the next step in the daily maintenance.
  

In a perfect world, we will do the following:

1. Create a SQL Agent Job to run daily maintenance including DBCCs and Backups

2. Create a step to do DBCCs.  If this step fails, stop maintenance and report failure.  On success, Go directly to the backup step.

3. Create a backup step to remote start NMM backups from a command shell (or application) that will stay with this step as long as it takes to report success or failure.  If this step fails, stop maintenance and report failure.  On success, report success.

Do you know of any shops that are successfully using SQL Agents to monitor these backups?

Hi Mark.

Can you tell if NMM 2.4 will be released this year?

Johannes

Hi Johannes,

Yes, we expect NMM 2.4 to be released this year.

-Bobby

Just a quick question Bobby, does the Networker roadmap get published anywhere that mere mortals can see?

I'll take a look on Wikileaks, it might be there

That's what I suspected!

Silly me.....I completely forgot to mention that I take bribes

I'm afraid not David.  The planned dates and features of future NetWorker releases are not externally-viewable.  This changes all the time with technology changes provoking new features to be added to future versions so its publication would cause more confusion than anything else.

-Bobby