According to the Admin Guide of NMM 2.2.1.
— This command is used to initiate the VSS-based backup. This command can be used with options for database consistency and Jet error checking.
It also states that Exchange eseutil/Chksgfiles api is used for consistency check:
eseutil.exe — This program provided by Microsoft Exchange Server 2003 is used to check that the database and log files do not contain errors, and that the
Exchange Server is valid before performing the restore. For Microsoft Exchange Server 2007, Replication Manager uses the CHKSGFILES API
instead of running eseutil. The CHKSGFILES API provides the same functionality as eseutil.
But the admin guide or RS is not clear about what utility is used for SQL 2005/2007 database consistency check.
• If a proxy client is specified, SQL consistency checks are performed on the proxy client. Related messages are written to the Replication Manager log files (erm_clientxx.log) on the proxy client.
• If no proxy client is specified for an SQL Client resource, consistency checks are performed on the Client resource host. Related messages are logged on the Client resource host in both the Replication Manager log files and the nmm.raw file.
Anyone has any insight.
Checks the logical and physical integrity of all the objects in the specified database by performing the following operations:
Runs DBCC CHECKALLOC on the database.
Runs DBCC CHECKTABLE on every table and view in the database.
Runs DBCC CHECKCATALOG on the database.
Validates the contents of every indexed view in the database.
Validates link-level consistency between table metadata and file system directories and files when storing varbinary(max) data in the file system using FILESTREAM.
Validates the Service Broker data in the database.
This means that the DBCC CHECKALLOC, DBCC CHECKTABLE, or DBCC CHECKCATALOG commands do not have to be run separately from DBCC CHECKDB. For more detailed information about the checks that these commands perform, see the descriptions of these commands.
David S Pravia
i think the question is how the networker module for microsoft applications (NMM) does the consistancy check when doing backups. not HOW TO do it within MSSQL in general.
Hi there Jejje,
I think David's reply is a perfect answer for the original question (which tools uses NMM to perform consistency check of SQL DB's), however it didn't explain how NMM uses those SQL tools to perform consistency check during an NMM backup process.
Basically, as in the case of Exchange backups, NMM, through ReplicationManager module uses ESE util to perform the consistency check of the DB on the snapshot mounted, previously taken by NMM /Exchange Writer or SQL writer). For SQL will use the tools mentioned by David in his previous answer.
Once Snapshot is mounted Replication manager will use the native tool of the DB's to perform the consistency check.
Please let me know if this answered your question or if you need any further informaiton.
Thanks for your replies.
Yes, the original question is "What utility is used by NMM to perform the SQL DB consistency checks". The admin guide is very clear about MS Exchange but not clear about the SQL , since DBCC is not an internal SQL command like eseutil is, it needs a clarification.