Search <book_title>...

Veritas InfoScale™ 7.4 Solutions Guide - Linux

Last Published: 2019-07-18

Product(s): InfoScale & Storage Foundation (7.4)

Platform: Linux

Section I. Introducing Veritas InfoScale
1. Introducing Veritas InfoScale
  1. About the Veritas InfoScale product suite
  2. Components of the Veritas InfoScale product suite
Section II. Solutions for Veritas InfoScale products
1. Solutions for Veritas InfoScale products
Section III. Stack-level migration to IPv6 or dual stack
1. Stack-level migration to IPv6 or dual stack
  1. Migrating Veritas InfoScale products to support IPv6/dual-stack
Section IV. Improving database performance
Section V. Using point-in-time copies
Section VI. Maximizing storage utilization
1. Optimizing storage tiering with SmartTier
2. Optimizing storage with Flexible Storage Sharing
Section VII. Migrating data
Section VIII. Just in time availability solution for vSphere
1. Just in time availability solution for vSphere
Section IX. Veritas InfoScale 4K sector device support solution
1. Veritas InfoScale 4k sector device support solution
Section X. Reference
1. Appendix A. Veritas AppProtect logs and operation states
  1. Log files
  2. Plan states
2. Appendix B. Troubleshooting Veritas AppProtect
  1. Troubleshooting Just In Time Availability

Backing up a snapshot of a mounted file system with shared access

While you can run the commands in the following steps from any node, Veritas recommends running them from the master node.

To back up a snapshot of a mounted file system which has shared access

On any node, refresh the contents of the snapshot volumes from the original volume using the following command:
```
# vxsnap -g database_dg refresh snapvol source=database_vol \
  [snapvol2 source=database_vol2]... syncing=yes
```
The syncing=yes attribute starts a synchronization of the snapshot in the background.
For example, to refresh the snapshot snapvol:
```
# vxsnap -g database_dg refresh snapvol source=database_vol \
  syncing=yes
```
This command can be run every time you want to back up the data. The vxsnap refresh command will resync only those regions which have been modified since the last refresh.
On any node of the cluster, use the following command to wait for the contents of the snapshot to be fully synchronous with the contents of the original volume:
```
# vxsnap -g database_dg syncwait snapvol
```
For example, to wait for synchronization to finish for the snapshots snapvol:
```
# vxsnap -g database_dg syncwait snapvol
```
Note:
You cannot move a snapshot volume into a different disk group until synchronization of its contents is complete. You can use the vxsnap print command to check on the progress of synchronization.
On the master node, use the following command to split the snapshot volume into a separate disk group, snapvoldg, from the original disk group, database_dg:
```
# vxdg split volumedg snapvoldg snapvol
```
For example, to place the snapshot of the volume database_vol into the shared disk group splitdg:
```
# vxdg split database_dg splitdg snapvol
```
On the master node, deport the snapshot volume's disk group using the following command:
```
# vxdg deport snapvoldg
```
For example, to deport the disk group splitdg:
```
# vxdg deport splitdg
```
On the OHP host where the backup is to be performed, use the following command to import the snapshot volume's disk group:
```
# vxdg import snapvoldg
```
For example, to import the disk group splitdg:
```
# vxdg import splitdg
```
VxVM will recover the volumes automatically after the disk group import unless it is set not to recover automatically. Check if the snapshot volume is initially disabled and not recovered following the split.
If a volume is in the DISABLED state, use the following command on the OHP host to recover and restart the snapshot volume:
```
# vxrecover -g snapvoldg -m snapvol
```
For example, to start the volume snapvol:
```
# vxrecover -g splitdg -m snapvol
				
```

On the OHP host, use the following commands to check and locally mount the snapshot volume:

# fsck -t vxfs /dev/vx/rdsk/database_dg/database_vol

# mount -t vxfs /dev/vx/dsk/database_dg/database_vol
			mount_point

For example, to check and mount the volume snapvol in the disk group splitdg for shared access on the mount point, /bak/mnt_pnt:

# fsck -t vxfs /dev/vx/rdsk/splitdg/snapvol
# mount -t vxfs /dev/vx/dsk/splitdg/snapvol /bak/mnt_pnt

Back up the file system at this point using a command such as bpbackup in Veritas NetBackup. After the backup is complete, use the following command to unmount the file system.
```
# umount mount_point
```
On the off-host processing host, use the following command to deport the snapshot volume's disk group:
```
# vxdg deport snapvoldg
```
For example, to deport splitdg:
```
# vxdg deport splitdg
```
On the master node, re-import the snapshot volume's disk group as a shared disk group using the following command:
```
# vxdg -s import snapvoldg
```
For example, to import splitdg:
```
# vxdg -s import splitdg
```
On the master node, use the following command to rejoin the snapshot volume's disk group with the original volume's disk group:
```
# vxdg join snapvoldg database_dg
```
For example, to join disk group splitdg with database_dg:
```
# vxdg join splitdg database_dg
```
VxVM will recover the volumes automatically after the join unless it is set not to recover automatically. Check if the snapshot volumes are initially disabled and not recovered following the join.
If a volume is in the DISABLED state, use the following command on the primary host to recover and restart the snapshot volume:
```
# vxrecover -g database_dg -m snapvol
```
When the recover is complete, use the following command to refresh the snapshot volume, and make its contents refreshed from the primary volume:
```
# vxsnap -g database_dg refresh snapvol source=database_vol \
syncing=yes
```
```
# vxsnap -g database_dg syncwait snapvol
```
When synchronization is complete, the snapshot is ready to be re-used for backup.

Repeat the entire procedure each time that you need to back up the volume.