Snapshot Procedure for fncdug2 using GUI

High level steps:

Snapshots will be taken of the production database (fncdug2) and the snapshots will then be mounted onto the int/dev DB server (fncdug1). 1. 2. 3. 4. 5. 6. 7. 8. 9. Unmount snapshots from host (if mounted) [fncdug1] or some other host Remove old snapshot volumes (optional) Place DB [on fncdug2] in HOT backup mode Create snapshots (RO) Place DB [on fncdug2 ]out of HOT backup mode Create snapshots (RW ) Export snapshots to requested host. i.e. fncdug1 Mount snapshots onto requested host. i.e. fncdug1 Update 3par_LUN_Map

Details
Background
Fncdug2 has 5 virtual volumes presented to it as vluns from the 3PAR-70 array: 0 fncdug2-home fncdug2 10 fncdug2-index-prod fncdug2 11 fncdug2-arch-prod fncdug2 12 fncdug2-tmp-prod fncdug2 13 fncdug2-data-prod fncdug2 ------------------ host ------------------ host ------------------ host ------------------ host ------------------ host

Fncdug1 has 9 virtual volumes presented to it as vluns on the 3PAR-70 array: 0 fncdug1-index-prod.ro.rw fncdug1 1 fncdug1-tmp-prod.ro.rw fncdug1 2 fncdug1-arch-prod.ro.rw fncdug1 3 fncdug1-data-prod.ro.rw fncdug1 14 fncdug1-home fncdug1 15 fncdug1-arch-int fncdug1 16 fncdug1-data-int fncdug1 17 fncdug1-index-int fncdug1 18 fncdug1-tmp-int fncdug1 ------------------ host ------------------ host ------------------ host ------------------ host ------------------ host ------------------ host ------------------ host ------------------ host ------------------ host

3PAR snapshots
3PAR has 3 kinds of snapshots. Fully copy (RW), read-only (thin), and read-write (thin). We basically only use the last 2. A read-only (thin) can be made from the original volume or a read-write (thin) snapshot. A read-write (thin) snapshot can only be made from read-only (thin) snapshots. So, in order to create a read-write snapshot, you must first create a read-only snapshot. Snapshots can be created in groups to provide a consistent state between various luns (which may be needed for some applications such as databases). Though we can provide only one lun to each server (no physical difference from 3PAR perspective), some hosts may be configured to provide more scsiqueue depth PER lun that it sees. Therefore, we often provide DBAs with more than one lun for the database. This requires that snapshot groups be used when creating snapshots in order to preserve consistency throughout the various luns.

Detailed Steps
1) Have admin unmount snapshot areas from fncdug1 or other host (if mounted)

On 3PAR (CLI): Unexport the luns: 1) 2) 3) 4) removevlun fncdug1-index-prod.ro.rw 0 fncdug1 removevlun fncdug1-tmp-prod.ro.rw 1 fncdug1 removevlun fncdug1-arch-prod.ro.rw 2 fncdug1 removevlun fncdug1-data-prod.ro.rw 3 fncdug1

Remove the snapshot VVs Warning: this deletes these luns 1) removevv fncdug1-index-prod.ro.rw fncdug1-index-prod.ro fncdug1-tmp-prod.ro.rw fncdug1tmp-prod.ro fncdug1-arch-prod.ro.rw fncdug1-arch-prod.ro fncdug1-data-prod.ro.rw fncdug1data-prod.ro

Current State: At this point, fncdug1 (the integration server) should have all LUs associated with the integration DB unmounted and destroyed. The integration server should now be ready to receive new vivols to mount for the integration DB. HAVE DBA place DB on fncdug2 in HOT BACKUP MODE

1. 2. 3. 4.

Login to 3Par GUI # via cd-sanman Left menu select provisioning Center Window highlight Virtual Volumes you want to snap Left mouse click select or select Create Virtual Copy or for more than one snapshot select Create Consistency Group Virtual Copies 5. Enter Destination Volume name and select Read Only or Read/Write. #Read/Write will create the RO and then the RW snapshots.

HAVE DBA place DB out of HOT BACKUP MODE Current State: At this point you have created both an RO and RW snapshots of the development database. Export the LUNS 1. 2. 3. 4. Highlight the Virtual Volume RW snapshot you just created, right mouse click and export Select Virtual Volume you want to export, it probably will already be highlighted. Click Next button Select host you want to export your snapshot to. Set Lun number if you want otherwise, program will take next available Lun. 5. Click on Finish button Current State: At this point, the newly created snapshots, intended for integration DB use, should now be available to the integration server fncdug1. Admin should now be able to mount up new RW snapshots. Use CLI command showvv d on 3PAR to see new WWNs of new snapshot luns. This may help the admin. I usually email this information to admin.