Operational Procedures Template - NetApp



-563880-371475Operational Procedures FragmentMetadataDescriptionModule NameSnap Creator 3.x Plug-in for MaxDBDocument TypeOperational ProceduresDate2012-01-02AuthorsDietmar EbertFragment VersionNotesFor instructions on using the template, refer to the Modular Architecture Authoring Guidelines.NOTES REGARDING THE OPERATIONAL PROCEDURES TEMPLATE:The “Overview” section is mandatory.The “Guidelines” and “Additional Information” sections are optional.TestTestSnap Creator 3.x Plug-in for MaxDBUse CaseProcedureCreate a backup of a databaseBack up a MaxDB database using the CLIBack up a MaxDB database using the GUIRestore a backup of a databaseRestore a MaxDB database using the CLIRestore a MaxDB database using the GUIRecover a databaseRecover a MaxDB database using the CLIRecover a MaxDB database using the GUIClone a databaseClone a MaxDB database using the CLIClone a MaxDB database using the GUIActivate automatic log backup modeActivate automatic log backup mode using the CLIBack up MaxDB Database Using the CLITo back up a MaxDB database by using the Snap Creator CLI, complete the following steps:Make sure the database is online.Back up the database using Snap Creator.snapcreator --profile <profile_name> [--config <config_name>] --action snap --policy <policy> --verboseWhere:<profile_name> is the name of the profile where the configuration file is located.<config_name> is the name of the configuration file if the name is different from <profile_name>.conf.<policy> is one of the policies specified in the configuration file.Back up MaxDB Database Using the GUITo back up a MaxDB database by using the Snap Creator GUI, complete the following steps:Make sure the database is online.Make sure the Snap Creator Framework GUI is started.Log in to the GUI.In the Backup Profiles pane, expand the profile and mark the configuration. The configuration context is loaded and displayed in the Configuration Context pane.Select the button (Actions menu), and then select Snapshot.Specify additional parameters: policy and user-defined variables. Click Ok.This process starts the backup operation; the output displays in the Console pane.Restore MaxDB Database Using the CLITo restore a MaxDB database from a previous backup by using the Snap Creator CLI, complete the following steps:Make sure the database is offline or in admin mode.Restore the database from a previous backup.snapcreator --profile <profile_name> [--config <config_name>] --action restore --policy <policy>Where:<profile_name> is the name of the profile where the configuration file is located.<config_name> is the name of the configuration file if the name is different from the <profile_name>conf.<policy> is one of the policies specified in the configuration file.Go to the procedure to REF _Ref315339589 \h Recover MaxDB Database Using the CLI or REF _Ref312412676 \h Recover MaxDB Database Using the MaxDB GUI.Restore MaxDB Database Using the GUITo restore a MaxDB database from a previous backup by using the Snap Creator GUI, complete the following steps:Make sure the database is online.Make sure the Snap Creator Framework GUI is started.Log in to the GUI.In the Backup Profiles pane, expand the profile and mark the configuration. The configuration context is loaded and displayed in the Configuration Context pane.Press the Actions button and select Restore.The Snap Creator Framework Wizard is launched. Click Next.Provide details for the restore operation. Select controller, volume name, policy, restore Snapshot name, and restore type from the drop-down lists. The example shows the Restore Details page with Volume Restore being selected. Click Next.Review the information presented in the Summary page and verify that it is correct. Click Finish to initiate the restore operation.On the Volume Restore pane, click Yes to accept the warning regarding the potential data loss.After a short time, a progress bar displays indicating the progress of the selected restore operation. When the restore operation finishes, the following message displays. Click Ok.Repeat the restore operation for each volume or file that is part of the backup and that is needed for the subsequent recovery procedure.Go to the procedure to REF _Ref315339589 \h Recover MaxDB Database Using the CLI or REF _Ref312412676 \h Recover MaxDB Database Using the MaxDB GUI.Recover MaxDB Database Using the CLITo recover a MaxDB database by using the Snap Creator CLI, complete the following steps:Make sure all of the archive logs are in place if the database is configured to create archive logs and to perform a point-in-time recovery.Place the database in admin mode.dbmcli -d <DB_ID> -u <dbm_user>,<dbm_passwd> db_adminWhere:<DB_ID> is the name/identifier of the MaxDB database.<dbm_user> is the user name of the MaxDB database manager.<dbm_passwd> is the password of the MaxDB database manager user.Verify whether the database is restartable.dbmcli –d <DB_ID> -u <dbm_user>,<dbm_passwd> db_restartinfoThis command returns recovery meta information.OKUsed LOG Page 1284693First LOG Page 0Restartable 1Id Restart Record amdlinux2:PAX_20080118_121057Id LOG Info amdlinux2:PAX_20080118_121057Consistent 1Log Volume Enabled 1Log Auto Overwrite 0Master Servernode AMDLINUX2Converter Version 27349Oldest Compatible Version 7.8.01.16Queue Count 2Repository Imports NOThe Restartable field indicates whether the database is restartable (1) or not restartable (0). The Consistent field indicates whether the database is consistent (1) or inconsistent (1). When these fields are used in combination, the database can immediately restart in online mode; otherwise, an archive log backup restore must first be performed.If the database is restartable and consistent (both values are set to 1), the database can be restarted using the following command.dbmcli –d <DB_ID> -u <dbm_user>,<dbm_passwd> db_restartFor additional options using this command, refer to the MaxDB documentation.If the database is not restartable and is inconsistent (both values are set to 0), perform an archive log restore. Depending on the MaxDB version, use either autorecover, or, if not available, use recover_start in combination with recover_replace to loop through the archived logs. Both methodologies recover the database to a specific point in time, as well as to the latest point in time.When the recovery is finished, the database is returned to online mode.Recover MaxDB Database Using the MaxDB GUITo recover a MaxDB database by using the Snap Creator GUI, complete the following step:Depending on the MaxDB version, use MaxDB Database Manager GUI or MaxDB Database Studio to perform a database recovery.For more information about the preferred GUI, refer to the MaxDB documentation.Clone MaxDB Database Using the CLITo clone a MaxDB database by using the Snap Creator CLI, complete the following steps:Make sure the following are properly configured:The source database is online.The configuration parameter SC_CLONE_TARGET is set.The Snap Creator agent specified in SC_CLONE_TARGET is running.Clone the database using Snap Creator.snapcreator --profile <profile_name> [--config <config_name>] --action clone_vol --policy <policy> --verboseWhere:<profile_name> is the name of the profile where the configuration file is located.<config_name> is the name of the configuration file if the name is different from <profile_name>.conf.<policy> is one of the policies specified in the configuration file.Clone MaxDB Database Using the GUITo clone a MaxDB database by using the Snap Creator GUI, complete the following steps:Make sure the source database is online.Make sure the Snap Creator Framework GUI is presented, and then log in.In the Backup Profiles pane, expand the profile and mark the configuration. The configuration context is loaded and displayed in the Configuration Context pane.Select the button (Actions menu), and then select Volume Clone.Specify additional parameters: policy and user-defined variables. Click Ok.This process asynchronously starts the clone operation. The current progress displays in the Console pane.Activate Automatic Log Backup Mode Using the CLITo activate an an automatic log backup by using the Snap Creator CLI, complete the following steps:Make sure there is at least one complete data backup for the database instance.Create a backup template type as FILE and a backup type as AUTO.dbmcli -d <DB_ID> -u <dbm_user>,<dbm_passwd> medium_put <medium_name> <location> <type> <backup_type>Where:<medium_name> is the backup template identifier.<location> is the file (full qualified) for the log backups. This has a version number appended to it.<type> is the type of the backup template.<backup_type> is the type of backup.Activate the automatic log backup.dbmcli -d <DB_ID> -u <dbm_user>,<dbm_passwd> autolog_on <medium_name>Archive backup files on a regular base. For example, use the Snap Creator Framework or OS commands. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download