XtremIO Virtual Copy Database Environment Setup

Introduction

This section describes the steps to mount the XVC snapshots of the PROD database volumes that you created previously. The steps that are provided in this section apply to both XVC databases, although we use XVC DEV as the database example.

Configuring multipath and udev rules

Perform the following steps as the root user to detect the snapshot volumes, configure the multipath, and create the udev rules:

1. Detect the snapshot volumes by running the following command, which rescans the SCSI bus on the XVC database server:

[root#] rescan-scsi-bus.sh

2. Configure the multipath for the XVC snapshot devices by adding the following entries in the /etc/multipath.conf file.

Note: For each device, the WWID is 3<NAA Identifier>. In this example, the WWID of C2_DATA11_DEV is 3514f0c5a4c200090 and the NAA Identifier is 514f0c5a4c200090.

multipath {

               wwid                    3514f0c5a4c200090

               alias                   C2_DATA11_DEV

        }

       multipath {

               wwid                    3514f0c5a4c200091

               alias                   C2_DATA12_DEV

        }

       multipath {

               wwid                    3514f0c5a4c200092

               alias                   C2_DATA13_DEV

        }

       multipath {

               wwid                    3514f0c5a4c200093

               alias                   C2_DATA14_DEV

        }

       multipath {

               wwid                    3514f0c5a4c200094

               alias                   C2_FRA_DEV

        }

       multipath {

               wwid                    3514f0c5a4c200095

               alias                   C2_REDO1_DEV

        }

       multipath {

               wwid                    3514f0c5a4c200096

               alias                   C2_REDO2_DEV

        }

3. Reload the multipath configuration file:

[root#] service multipathd reload

4. To set the proper database permissions to the snapshot devices, create a udev rules file /etc/udev/rules.d/60-database.rules and add an entry in the file for each snapshot device as follows:

KERNEL=="dm-*", ENV{DM_NAME}=="C2_DATA11_DEV?", OWNER:="dba", GROUP:="dbadmin", MODE="0660"

KERNEL=="dm-*", ENV{DM_NAME}=="C2_DATA12_DEV?", OWNER:="dba", GROUP:="dbadmin", MODE="0660"

KERNEL=="dm-*", ENV{DM_NAME}=="C2_DATA13_DEV?", OWNER:="dba", GROUP:="dbadmin", MODE="0660"

KERNEL=="dm-*", ENV{DM_NAME}=="C2_DATA14_DEV?", OWNER:="dba", GROUP:="dbadmin", MODE="0660"

KERNEL=="dm-*", ENV{DM_NAME}=="C2_FRA_DEV?", OWNER:="dba", GROUP:="dbadmin", MODE="0660"

KERNEL=="dm-*", ENV{DM_NAME}=="C2_REDO1_DEV?", OWNER:="dba", GROUP:="dbadmin", MODE="0660"

KERNEL=="dm-*", ENV{DM_NAME}=="C2_REDO2_DEV?", OWNER:="dba", GROUP:=”dbadmin”, MODE=”0660”

5. Reload the udev rules:

[root#] udevadm trigger 92826588

Depending on the type of DBMS and features implemented, you might have to change the disk-mapping structures, including renaming and remounting. See your vendor documentation for information about how to use snapshot volumes for new database instances.

Mounting the snapshot database

Depending on the DBMS being deployed, the process of mounting the snapshot volumes and preparing the databases might vary. The following steps are general instructions; consult your specific product documentation for details.

1. Prepare the new snapshot database environments as follows:
   1. Create the directory for any database audit files.
   2. Create or copy any necessary initialization parameter files from the PROD database.
   3. On the XVC database server, edit the files by modifying initialization file parameters with the updated values for cluster status, database name, and so on.

2. Mount the snapshot database using the appropriate user ID.

Changing the database file names

Change the database file names as follows:

1. Log in to the newly mounted snapshot database and determine the current datafiles and log file names.

2. Change the location of the database and log files to reflect the new disk group name and location.
3. Using the correct credentials, log in to the database to open the database.
4. Change the database name and DBID.
5. Update the database initialization/settings to reflect the new name.

                  Reset/drop/re-create the former redo/transaction logs.

Updating system configuration settings

Update the system configuration settings as follows:

1. Update or create the relevant system initialization files (spfile).
2. Re-create the TEMP tablespace.

3. Restart the snapshot database.

The XVC snapshot database is created and running. Change other database initialization parameters as needed.