Skip to main content
SnapManager Oracle

Using SnapManager for Oracle to create the database profile and assign a protection policy


You must create a profile in SnapManager for Oracle, enable protection in the profile, and assign a protection policy to create a protected backup.

A profile contains information about the database being managed, including its credentials, backup settings, and protection settings for backups. After you create a profile, you do not need to specify database details each time you perform an operation. A profile can reference only one database, but that same database can be referenced by more than one profile.

  1. Go to the SnapManager for Oracle client.

  2. From the Repositories tree, right-click the host, and select Create Profile.

  3. On the Profile Configuration Information page, enter the profile details, and click Next.

    You can enter the following information:

    • Profile name: payroll_prod2

    • Profile password: payroll123

    • Comment: Production Payroll database

  4. On the Database Configuration Information pages, enter the database details, and click Next.

    You can enter the following information:

    • Database name: PAYDB

    • Database SID: payrolldb

    • Database host: Accept the default. Because you are creating a profile from a host in the repository tree, SnapManager displays the host name.

    • Host Account, representing the Oracle user account: oracle

    • Host Group, representing the Oracle group: dba

  5. On the Database Connection Information page, click Use database Authentication to allow users to authenticate using database information.

  6. Enter the database connection details and click Next.

    You can enter the following information:

    • SYSDBA Privileged User Name, representing the system database administrator who has administrative privileges: sys

    • Password (SYSDBA password): oracle

    • Port to connect to database host: 1521

  7. On the RMAN Configuration Information page, click Do not use RMAN and click Next.

    Oracle Recovery Manager (RMAN) is an Oracle tool that helps you back up and recover Oracle databases using block-level detection.

  8. On the Snapshot Naming Information page, specify a naming convention for the Snapshots associated with this profile by selecting variables.

    The smid variable creates a unique snapshot identifier.

    Perform the following:

    1. In the Variable Token list, select usertext and click Add.

    2. Enter payroll.techco.com_ as the host name and click OK.

    3. Click Left until the host name appears just after smo in the Format box.

    4. Click Next.

    The Snapshot naming convention of smo_hostname_smoprofile_dbsid_scope_mode_smid becomes "smo_payroll.techco.com_payroll_prod2_payrolldb_f_a_x" (where "f" indicates a full backup, "a" indicates the automatic mode, and "x" represents the unique SMID).

  9. Select Protection Manager Protection Policy.

    The Protection Manager Protection Policy enables you to select a protection policy that was configured by using NetApp Management Console.

  10. Select TechCo Payroll Data: Backup as the protection policy from the protection policies retrieved from NetApp Management Console, and click Next.

  11. On the Perform Operation page, verify the information and click Create.

  12. Click Operation Details to see information about the profile create operation and volume-based restore eligibility information.

    • The assignment of a NetApp Management Console protection policy to the database profile automatically creates a nonconformant dataset, visible to the NetApp Management Console operator, with the name convention smo_<hostname>_<profilename>, or in this example:

    • If the profile is not eligible for volume restore (also called "fast restore"), the following occurs:

      • The Results tab indicates that the profile creation was successful and that warnings occurred during the operation.

      • The Operation Details tab includes a WARNING log, which states the profile is not eligible for fast restore and explains why.