EMC BCVs

Overview
Locations of Files: Scripts, Source, & Logs
Scripts Description and contents
Scripts USAGE
Troubleshooting
Exit Status Values

BCV Overview

BCVs (Business Continuity Volumes) gives you software utilities to mirror and split off the mirror onto current symmetrix volumes (disks). It also provides means of putting your database in backup mode.

The DBMS host will sync/mirror the BCVs. When then have sync'd, the DBMS host will then split the BCVs. From the BCV backup server, the mounting and backup of these split (now separated) BCVs.

If you need to add BCVs (create them) - take them from the highest number symm dev numbers in the freepool. An EMC design.

Location Of Files

All bcv executable & config files are owned by bcvadmin

The bcv scripts are located in: /nfs/admin/bcv/bin
The bcv logs are located in: /nfs/admin/bcv/bcvlog
The netbackup logs are located in: /nfs/admin/bcv/netlog
All bcv source files are located in /nfs/admin/bcv/emc

BCV Scripts

  1. bcvimagecapture: run on DBMS, sync and splits BCVs
  2. bcv-import: imports Veritas disk groups and mounts
  3. bcv-backup: does a netbackup of mounts for HOST
  4. bcv-deport: unmounts and deports Veritas disk groups
All the scripts call the following config files:

All mounts done under: /backup-mounts/$DBMS_HOST-$INSTANCE/$VOLUME_NAME

BCV Troubleshooting

You get paged with a problem.

Coordinate with the oncall DBA.

  1. Call Operations and have them put the BCV autosys on hold
  2. Fix the issue:
    3. If it fails on bcvimagecapture: move to next major step.

    If it fails on bcv-import: try importing the HOSTNAME.dg and mounting /backup-mounts/$DBMS_HOST-$INSTANCE/$VOLUME_NAME. Correct issue if you cannot do that. Then unmount /backup-mounts/$DBMS_HOST-$INSTANCE/$VOLUME_NAME, deport HOSTNAME.db

    If it fails on bcv-backup: find out if netbackup is working. Then unmount /backup-mounts/$DBMS_HOST-$INSTANCE/$VOLUME_NAME, deport HOSTNAME.db.

    If it fails on bcv-deport: Find out why it could not umount and export. unmount /backup-mounts/$DBMS_HOST-$INSTANCE/$VOLUME_NAME, deport HOSTNAME.db

  3. Have Ops restart the autosys BCV (start the entire process over)

    4. There is elaborate error checking. When an error occurs, a page and/or email is sent (depends on what the page and mail settings are for a particular error). There is no force to override/overcome an error. We made no assumptions and therefore it is up to the Administrators to figure out why the scripts failed based on the error, then fix the error cause, and restart the autosys job/block from beginning.

    BCV Scripts Usage

    bcvimagecapture: bcvimagecapture [-v] full|inc instance_name 0-9

    example: -v full MDMT 0

    bcv-import, bcv-backup, bcv-deport: [-v] hostname INSTANCE

    example: -v myhost MDMT

    Exit Status Codes

    1. 0 success
    2. 1 FATAL error
    3. 2 cannot create file
    4. 3 cannot open file
    5. 4 no BCV disk group
    6. 5 no GK devices
    7. 6 fsflush fail
    8. 7 veritas error
    9. 8 veritas import/deport error
    10. 9 usage error
    11. 10 configuration error in setting VAR
    12. 11 unsupported DBMS
    13. 12 mismatch DBMS instances
    14. 13 failed DBMS freeze
    15. 14 failed DBMS thaw
    16. 15 failed BCV establish
    17. 16 failed BCV split