Topics | How To | Related Topics
Unix File System iDataAgents
SAN and Volume Level Agents on UNIX
CVSnaptool for UNIX
When installing the CXBF block filter driver, you were asked to specify a mount point for the copy-on-write cache. Use the example below to mount the partition.
To mount the COW Cache partition:
When you have selected an appropriate volume, mount it to the previously specified mount point using a command similar to the following:
mount /dev/cxbf/dsk/c1t1d1s1 /<mount_point>
Where:
<mount_point> is the mount point you specified during the installation of the CXBF driver.
|
Use the following procedure to create CXBF devices using Volume Explorer.
Before You Begin
If you encounter errors while configuring or deconfiguring CXBF devices on the client, go to /cvd.log on the client for more detailed information concerning the error.
Required Capability: See Capabilities and Permitted Actions
To create a CXBF device:
|
Option available only on Solaris: Enable persistence, if desired.
Oracle uses an environment variable called DBCA_RAW_CONFIG, and mapping file that tells the Oracle database application where to create data files, redo files and control files. DBCA_RAW_CONFIG is the variable indicating path of mapping file.
The mapping file must be modified to point to the CXBF devices created for the RAW devices.
To edit the mapping file:
System=/dev/rdsk/c1t0d2s1
Change to:
System=/dev/cxbf/rdsk/c1t0d2s1
chown Oracle:dba /dev/cxbf/rdsk/c1t1d1s1
chmod 600 /dev/cxbf/rdsk/c1t0d2s1
Use the following procedure to deconfigure CXBF devices using Volume Explorer.
Before You Begin
If a CXBF device on AIX was configured using Volume Explorer (where the CXBF device was added to /etc/filesystems), be sure to mount the CXBF device before you deconfigure it. If an unmounted CXBF device on AIX is deconfigured using Volume Explorer, the /etc/filesystems system file will be out of synchronization with the actual file system configuration.
If /etc/filesystems and the actual file system configuration get out of synchronization, a manual edit of /etc/filesystems is required to correct the inconsistencies. Remove the cxbf entry and uncomment the original entry (that is, remove "*Galaxy" from the beginning of each line).
If you encounter errors while configuring or deconfiguring CXBF devices on the client, go to /cvd.log on the client for more detailed information concerning the error.
Required Capability: See Capabilities and Permitted Actions
To deconfigure a CXBF device:
Related Topics:
Before You Begin
Required Capability: See Capabilities and Permitted Actions
To enable QSnap on a subclient:
Use this procedure to test a CXBF device to see if the driver has successfully attached.
To test the CXBF device:
For the Quick Recovery Agent and Image Level iDataAgents, if the Oracle instance has data files residing on a raw partition, soft links need to be re-established after creating the raw CXBF devices.
For example, if an Oracle volume is linked as:
data1.dbf -> dev/rdsk/c1t1d1s1
To create the links:
rm data1.dbf
ln -s /dev/cxbf/rdsk/c1t1d1s1
chown Oracle:dba /dev/cxbf/rdsk/c1t1d1s1
During Quick Recovery on the QR Agent, the soft links will automatically be associated with the recovery volume. This is analogous to automatically switching the mount points between file system volumes during recovery.
If the selected disk contains an existing file system that is mounted, then the disk will need to be unmounted and mounted on the CXBF device. (All data will be preserved.) For example, if two Oracle volumes were mounted as:
/dev/dsk/c1t1d1s1 /ora_data
/dev/dsk/c2t1d1s1 /ora_logs
Required Capability: See Capabilities and Permitted Actions
To mount them as CXBF devices:
umount
/ora_data
umount /ora_logs
mount /dev/cxbf/dsk/c1t1d1s1 /ora_data
mount /dev/cxbf/dsk/c2t1d1s1 /ora_logs
After mounting volumes as CXBF devices, do not also mount them as ordinary Solaris devices using the dev/dsk path; this might cause a system panic. |
chown Oracle:dba /ora_data
chown Oracle:dba /dev/cxbf/dsk/c1t1d1s1
chown Oracle:dba /ora_logs
chown Oracle:dba /dev/cxbf/dsk/c2t1d1s1
Use the CVSnap Tool to display all CXBF devices.
To display all CXBF devices:
From the command line, type one of the following, depending on your operating system, and press Enter:
Sample output:
No of bf devices 7
c1t0d26s0
c1t0d26s1
c1t0d26s3
c1t0d26s4
c1t0d26s5
c1t0d26s6
c1t0d26s7
Use the CVSnap Tool to display all snapshots on the computer.
To display all snapshots:
From the command line, type one of the following, depending on your operating system, and press Enter:
Use the CVSnap Tool to obtain CXBF device information.
To get CXBF device information:
From the command line, type one of the following, depending on your operating system, and press Enter:
Use the CVSnap Tool to stop and delete a CXBF filter.
After you stop and delete a device, Volume Explorer will no longer be able to detect it; thus the following commands should be run with extreme caution and only when required. |
To stop and delete a CXBF device:
/sbin/cvsnap
All the available CXBF filters will be displayed and from this list you can get the filter number which is the number appended with CXBF.
For example:
cvsnap>show_filters
Sample output:
/dev/cxbf/cxbf1/blk
/dev/cxbf/cxbf3/blk
/dev/cxbf/cxbf4/blk
Here, there are three filters with filter numbers 1,3, and 4.
At the cvsnap> prompt, type stop_filter minor=<filter_minor_number> and press Enter.
For example:
stop_filter minor=1
Sample output:
Stopping CXBF node
over:
minor=1
Use the CVSnap Tool to stop and delete a CXBF filter.
After you stop and delete a device, Volume Explorer will no longer be able to detect it; thus the following commands should be run with extreme caution and only when required. |
To stop and delete a CXBF device:
/sbin/cvsnap
All the available CXBF filters will be displayed and from this list you can get the filter number which is the number appended with CXBF.
For example:
cvsnap>show_filters
Sample output:
/dev/cxbf/cxbf0
/dev/cxbf/cxbf1
Here, there are two filters with filter numbers 0 and 1.
At the cvsnap> prompt, type stop bfminor=<filter_number> and press Enter.
For example:
stop bfminor=0
Sample output:
Stopping CXBF node:
minor=0
Use the CVSnap Tool to defunc and delete a CXBF device.
After you defunc and delete a device, Volume Explorer will no longer be able to detect it; thus the following commands should be run with extreme caution and only when required. |
To defunc and delete a CXBF device:
/usr/sbin/cvsnap
For example:
defunc device=c1t0d6s0
Sample output:
defunc device=c1t0d6s0
device c1t0d6s0 marked defunct.
When new disks are added to a client, and have been labeled, verify that they can be seen. (If not, edit the sd.conf file as shown below.) Then, use Volume Explorer to detect the newly added disks and create cxbf devices on all the volumes of the newly added disk(s).
To edit the sd.conf file:
name="sd" class="scsi" target=0 lun=0 to target=15 lun=7
You will need to add more entries if required by your hardware configuration.
The maximum range of target is 0-255 and for each target LUN the range is 0-255.
It is strongly recommended that you do not edit the file unless required. |
When the disk label has changed, for example, after changing sizes of the partitions/slices, the following procedure needs to be followed to see the new CXBF devices with the correct/updated sizes.
Required Capability: See Capabilities and Permitted Actions
To update the CXBF devices: