Loading...

Check Readiness for File System Clients and Database Clients - Overview

You can use the Check Readiness report to verify that the client and MediaAgent are connected to the CommServe computer and that the database agents are properly configured to run backup and restore jobs.

The readiness report indicates the connectivity state for a client and MediaAgent. It can be run against the following clients:

  • File System
  • DB2
  • Oracle
  • SAP Oracle

Note: When you run the report for an client that has the Oracle Agent, you must enable the operating system authentication on the client for all the Oracle database instances so that the database status will not show UNKNOWN. If the operating system authentication is not enabled, go to the ORACLE_HOME\NETWORK\ADMIN directory and add the following line to the sqlnet.ora file.

set SQLNET.AUTHENTICATION_SERVICES= (NTS)

If you run the report for a client that has a database agent, you can configure the software to run only the client check. For more information, see Enabling or Disabling the Database Readiness Check.

A file system client and MediaAgent client are ready when they are connected to the CommServe computer.

A database client and MediaAgent are ready when they are connected to the CommServe computer and available for backup and restore jobs and meet the following configuration criteria:

Database Client Configuration Criteria
DB2
  1. The DB2 instance status.
  2. The DB2 instance user account.
  3. The DB2 instance user account is a member of the SnapProtect install group.
  4. The DB2 instance user account has read and write permissions for the following directories:
    • The SnapProtect registry
    • The base directory
    • The SnapProtect  log file directory
    • The DB2 Archive Log Directory
    • The DB2 Audit Error Path directory
    • The DB2 Retrieve Path directory
Oracle
  1. The SnapProtect registry, log files and base directories that the database user has read and write permissions for.
  2. The SnapProtect install group the database user is a member of.
  3. The Oracle server status.

    The Oracle server is ready when the Oracle database is in the OPEN or MOUNT state.

    The Oracle server is not ready when the Oracle database is in the NOMOUNT  or SHUTDOWN state.

  4. The RMAN SBT channel allocation.
SAP Oracle
  1. The SnapProtect registry, log files and base directories that the database user has read and write permissions for.
  2. The SnapProtect install group the database user is a member of.
  3. The database status.
  4. The RMAN SBT channel allocation.
  5.  For UNIX configurations, the SAP BACKINT symbolic links to the SnapProtect BACKINT links.

Connectivity Checks

The following network communication checks are performed:

  • Client to CommServe
  • CommServe to Client
  • Client to MediaAgent
  • MediaAgent to Client
  • Client to Deduplication Database MediaAgent, if client-side deduplication is enabled.
  • Deduplication Database MediaAgent to Client, if client-side deduplication is enabled.
  • MediaAgent to Deduplication Database MediaAgent
  • Deduplication Database MediaAgent to MediaAgent

The following resource checks are performed:

  • MediaAgent status, whether online or offline
  • Library, mount path status, whether online or offline
  • Library Controller status, whether online or offline
  • Drive pool, Master pool, Standalone media status
  • Mount path space check, or watermark space check
  • Backup space size check
  • NDMP filer resource check for NAS Subclients
  • Deduplication database store status