WARNING: This web is not used anymore. Please use PDBService.AutomaticRecovery instead!
 

Automatic Recoveries

Automatic test recoveries are indispensable element of any backup system. They not only help to ensure recoverability but also to detect possible corruptions and other problem that cannot be easily spotted. Automatic recoveries are especially important in Oracle environment where backups are being taken inline with transactions modifying data and where single backup strategy may consist of many different types of backups.

This Document shows how to configure hardware and software for test recoveries and finally how to schedule and run recoveries themselves.

Configuration of the recovery system

  • Dedicate hardware for the test recovery system. Minimum requirements are:
    • at least one mid-range server
    • amount of disk arrays sufficient to fit the biggest database that is going to be recovered. Disk arrays can be configured with RAID5. Flash recovery area is not required
  • Configure and install recovery system. Follow installation instructions available here:
    • configure hardware,
    • configure OS, storage, multipathing and oracle account equivalence (in case you have more then 1 mid-range server),
    • install Oracle clusterware (the same version as on production). Name the cluster recor.
    • install Oracle RDBMS software (the same version as on production)
      • use cloning
    • configure listeners using netca,
    • configure ASM instances and tune ASM initialization parameters (Do not create ASM diskgroups)
  • Configure TSM/TDPO clients on the recovery system nodes:
    • NOTE: TSM/TDPO clients on the test recovery system should be configured configured differently from ordinary RAC nodes. The main difference is that instead of having only one set of dsm.opt and tdpo.opt configuration files there should be one such set per every single database that is supposed to be recovered. For every database that will be recovered there must be also a password file generated. The configuration files should stick to the following naming convention: dsm_DB_NAME.opt, tdpo_DB_NAME.opt.
    • download and untar the archive containing configuration files for major databases.
wget ...
sudo tar xvPf recor_tivoli_client_config.tar
    • Check if configuration files exist for all database that will be recovered:
ls /opt/tivoli/tsm/client/oracle/bin/
    • If there are some databases missing create appropriate configuration files:
# for each DB_NAME database:
sudo cp /opt/tivoli/tsm/client/oracle/bin/dsm.opt /opt/tivoli/tsm/client/oracle/bin/dsm_DB_NAME.opt
sudo vi /opt/tivoli/tsm/client/oracle/bin/dsm_DB_NAME.opt  # set properly name of the TSM server
sudo cp /opt/tivoli/tsm/client/oracle/bin/tdpo.opt /opt/tivoli/tsm/client/oracle/bin/tdpo_DB_NAME.opt
sudo vi /opt/tivoli/tsm/client/oracle/bin/tdpo_DB_NAME.opt  # set properly DSMI_ORC_CONFIG and TDPO_NODE variables
sudo tdpoconf password -TDPO_OPTfile=/opt/tivoli/tsm/client/oracle/bin/tdpo_DB_NAME.opt

Scheduling and running test recoveries

Edit | Attach | Watch | Print version | History: r6 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 2008-01-22 - JacekWojcieszuk
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    PSSGroup All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback