InfoScale™ 9.0 Storage Foundation Cluster File System High Availability Administrator's Guide - Linux
- Section I. Introducing Storage Foundation Cluster File System High Availability
- Overview of Storage Foundation Cluster File System High Availability
- About Veritas File System
- About Veritas Replicator
- How Dynamic Multi-Pathing works
- How Volume Manager works
- How Volume Manager works with the operating system
- How Volume Manager handles storage management
- Volume layouts in Veritas Volume Manager
- Online relayout
- Volume resynchronization
- Dirty region logging
- Volume snapshots
- FastResync
- How VxVM handles hardware clones or snapshots
- Volume encryption
- How Veritas File System works
- How Storage Foundation Cluster File System High Availability works
- About Storage Foundation Cluster File System High Availability architecture
- About Veritas File System features supported in cluster file systems
- About single network link and reliability
- About I/O fencing
- About preventing data corruption with I/O fencing
- About I/O fencing components
- About server-based I/O fencing
- About secure communication between the SFCFSHA cluster and CP server
- How Cluster Volume Manager works
- Overview of clustering
- Cluster Volume Manager (CVM) tolerance to storage connectivity failures
- Storage disconnectivity and CVM disk detach policies
- CVM initialization and configuration
- Dirty region logging in cluster environments
- Multiple host failover configurations
- About Flexible Storage Sharing
- Application isolation in CVM environments with disk group sub-clustering
- Overview of Storage Foundation Cluster File System High Availability
- Section II. Provisioning storage
- Provisioning new storage
- Advanced allocation methods for configuring storage
- Customizing allocation behavior
- Using rules to make volume allocation more efficient
- Understanding persistent attributes
- Customizing disk classes for allocation
- Specifying allocation constraints for vxassist operations with the use clause and the require clause
- Creating volumes of a specific layout
- Customizing allocation behavior
- Creating and mounting VxFS file systems
- Creating a VxFS file system
- Mounting a VxFS file system
- tmplog mount option
- ioerror mount option
- largefiles and nolargefiles mount options
- Resizing a file system
- Monitoring free space
- Extent attributes
- Section III. Administering multi-pathing with DMP
- Administering Dynamic Multi-Pathing
- Discovering and configuring newly added disk devices
- About discovering disks and dynamically adding disk arrays
- How to administer the Device Discovery Layer
- Administering DMP using the vxdmpadm utility
- Gathering and displaying I/O statistics
- Specifying the I/O policy
- Discovering and configuring newly added disk devices
- Dynamic Reconfiguration of devices
- Reconfiguring a LUN online that is under DMP control using the Dynamic Reconfiguration tool
- Manually reconfiguring a LUN online that is under DMP control
- Managing devices
- Displaying disk information
- Changing the disk device naming scheme
- Adding and removing disks
- Event monitoring
- Administering Dynamic Multi-Pathing
- Section IV. Administering Storage Foundation Cluster File System High Availability
- Administering Storage Foundation Cluster File System High Availability and its components
- Administering CFS
- About the mount, fsclustadm, and fsadm commands
- When the CFS primary node fails
- About Snapshots on SFCFSHA
- Administering VCS
- Administering CVM
- About setting cluster node preferences for master failover
- About changing the CVM master manually
- Importing disk groups as shared
- Administering Flexible Storage Sharing
- Administering ODM
- About administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- About administering the coordination point server
- About migrating between disk-based and server-based fencing configurations
- Migrating between fencing configurations using response files
- About the vxfentsthdw utility
- Administering SFCFSHA global clusters
- Enabling S3 server
- Using Clustered NFS
- Understanding how Clustered NFS works
- Configure and unconfigure Clustered NFS
- Administering Clustered NFS
- Samples for configuring a Clustered NFS
- Using Common Internet File System
- Deploying Oracle with Clustered NFS
- Administering sites and remote mirrors
- About sites and remote mirrors
- Fire drill - testing the configuration
- Changing the site name
- Administering the Remote Mirror configuration
- Failure and recovery scenarios
- Administering iSCSI with SFCFSHA
- Administering datastores with SFCFSHA
- Administering Storage Foundation Cluster File System High Availability and its components
- Section V. Optimizing I/O performance
- Veritas File System I/O
- Veritas Volume Manager I/O
- Managing application I/O workloads using maximum IOPS settings
- Section VI. Veritas Extension for Oracle Disk Manager
- Using Veritas Extension for Oracle Disk Manager
- About Oracle Disk Manager
- About Oracle Disk Manager and Oracle Managed Files
- Using Cached ODM
- Using Veritas Extension for Oracle Disk Manager
- Section VII. Using Point-in-time copies
- Understanding point-in-time copy methods
- When to use point-in-time copies
- About Storage Foundation point-in-time copy technologies
- Volume-level snapshots
- Storage Checkpoints
- About FileSnaps
- About snapshot file systems
- Administering volume snapshots
- Traditional third-mirror break-off snapshots
- Full-sized instant snapshots
- Creating instant snapshots
- Adding an instant snap DCO and DCO volume
- Controlling instant snapshot synchronization
- Creating instant snapshots
- Cascaded snapshots
- Adding a version 0 DCO and DCO volume
- Administering Storage Checkpoints
- Storage Checkpoint administration
- Administering FileSnaps
- Administering snapshot file systems
- Understanding point-in-time copy methods
- Section VIII. Optimizing storage with Storage Foundation Cluster File System High Availability
- Understanding storage optimization solutions in Storage Foundation Cluster File System High Availability
- About SmartMove
- Migrating data from thick storage to thin storage
- Maintaining Thin Storage with Thin Reclamation
- Reclamation of storage on thin reclamation arrays
- Identifying thin and thin reclamation LUNs
- InfoScale 4K sector device support solution
- Understanding storage optimization solutions in Storage Foundation Cluster File System High Availability
- Section IX. Maximizing storage utilization
- Understanding storage tiering with SmartTier
- Creating and administering volume sets
- Multi-volume file systems
- Features implemented using multi-volume file system (MVFS) support
- Adding a volume to and removing a volume from a multi-volume file system
- Volume encapsulation
- Load balancing
- Administering SmartTier
- About SmartTier
- Placement classes
- Administering placement policies
- File placement policy rules
- Multiple criteria in file placement policy rule statements
- Using SmartTier with solid state disks
- Sub-file relocation
- Administering hot-relocation
- How hot-relocation works
- Moving relocated subdisks
- Compressing files
- About compressing files
- Use cases for compressing files
- Section X. Administering and protecting storage
- Managing volumes and disk groups
- Rules for determining the default disk group
- Moving volumes or disks
- Monitoring and controlling tasks
- Performing online relayout
- Adding a mirror to a volume
- Encrypting existing volumes
- Managing disk groups
- Disk group versions
- Displaying disk group information
- Creating a disk group
- Importing a disk group
- Moving disk groups between systems
- Importing a disk group containing hardware cloned disks
- Handling conflicting configuration copies
- Destroying a disk group
- Backing up and restoring disk group configuration data
- Managing plexes and subdisks
- Erasure coding in Veritas InfoScale storage environments
- Erasure coding deployment scenarios
- Customized failure domain
- Decommissioning storage
- Rootability
- Encapsulating a disk
- Rootability
- Sample supported root disk layouts for encapsulation
- Encapsulating and mirroring the root disk
- Administering an encapsulated boot disk
- Quotas
- Using Veritas File System quotas
- File Change Log
- Support for protection against ransomware
- Non-modifiable storage checkpoints
- Soft WORM storage
- Secure file system
- Secure file system for Oracle Single Instance
- Secure file system for PostgreSQL database
- Managing volumes and disk groups
- Section XI. Reference
- Appendix A. Reverse path name lookup
- Appendix B. Tunable parameters
- Tuning the VxFS file system
- Methods to change Dynamic Multi-Pathing tunable parameters
- Tunable parameters for VxVM
- Methods to change Veritas Volume Manager tunable parameters
- About LLT tunable parameters
- About GAB tunable parameters
- About VXFEN tunable parameters
- Appendix C. Command reference
- Appendix D. Creating a starter database
- Appendix E. Executive Order logging
Configuring OpenStack
OpenStack is a cloud operating system that controls large pools of computer, storage, and networking resources in a data center. OpenStack provides a dashboard that lets you provision resources using a web interface.
Veritas InfoScale is integrated with the following OpenStack components:
Cinder - is a block storage service for OpenStack. Cinder provides the infrastructure for managing volumes in OpenStack. Cinder volumes provide persistent storage to guest virtual machines (known as instances) that manage OpenStack compute software.
Manila - lets you share file systems with virtual machines on OpenStack.
Configuring Cinder
- Ensure that a CFS filesystem exportable through CNFS is configured.
Run the following command
cfsshare display
An output similar to the following indicates it is configured correctly.
CNFS metadata filesystem : /locks Protocols Configured : NFS #RESOURCE MOUNTPOINT PROTOCOL OPTIONS share1 /vx/fs1 NFS rw,sync,no_root_squash,no_subtree_check
A Virtual IP address is used to export CFS through NFS in the OpenStack controller.
- On the OpenStack cluster, edit
cinder.conf
as under[infoscale-1] volume_driver=<Name of the InfoScale Cinder driver> volume_backend_name=<NFS share name. > nfs_shares_config=<File to share details as vip:/exported_dir> nfs_mount_point_base=<Mount point for the share to be mounted on OpenStack Cinder. > nfs_sparsed_volumes=<True - to Preallocate or sparse files> nfs_mount_options= <Mount options for OpenStack Cinder to use for NFS mount> : [DEFAULT] : enabled_backends = lvmdriver-1,infoscale-1
- Edit
/etc/cinder/Infoscale_share_hdd
and add<Virtual IP address>/<mountpoint of the cfsshare volume>
. - Copy
/opt/VRTS/openstack/drivers/veritas_cnfs.py
tocinder/cinder/volume/drivers/
. - Run the following commands to assign write permissions to NFS mount point on the OpenStack controller node.
setfacl -m u:stack:rwx /cinder/cnfs/cnfs_sata_hdd
chmod -R 777 /etc/cinder/infoscale_share_hdd
- Run the following command to restart cinder service.
/etc/init.d/openstack-cinder-volume restart
Review output as under
Stopping openstack-cinder-volume: [ OK ] Starting openstack-cinder-volume: [ OK ]
After you restart the OpenStack Cinder driver, the latest configuration file is introduced. The OpenStack cinder log files are at
/var/log/cinder/volume.log
. - Run the following commands to create a Volume type on the OpenStack controller node and map it to InfoScale.
cinder type-create <New Volume type>
cinder type-key <New Volume type> set volume_backend_name=INFOSCALE_HDD
Any cinder operation performed on the new volume type results in an operation on the NFS mountpoint. Following table describes the mapping of Openstack commands to Infoscale operations.
Table: Mapping of OpenStack commands to InfoScale operations
OpenStack command | InfoScale operation |
---|---|
Creation of a Cinder volume | File creation on NFS mountpoint |
Deletion of a Cinder volume | File deletion on NFS mountpoint |
Creation of snapshot of a Cinder volume | Hardlink creation of file |
Deletion of snapshot of a Cinder volume | Deletion of file |
Creation of Cinder volume from existing snapshot of Cinder volume | Hardlink creation of file |
Creation of cloned Cinder volume | Hardlink creation of file If cloned volume size is not same as source volume, resize file |
Growing of existing Cinder volume | Extending file size |
OpenStack Cinder does not allow you to share a block device simultaneously between virtual machines. Using OpenStack Manila, you can share a single file system between multiple virtual machines. OpenStack Manila provides a shared file system as a service. Infoscale is integrated with OpenStack Manila through an OpenStack Manila driver that lets you share Veritas Access file systems with virtual machines on OpenStack.
Configuring Manila
- As a prerequisite, CFS filesystem must be configured by using cfsshare. Run the following command.
cfsshare display
Output similar to the following indicates a successful configuration.
CNFS metadata filesystem : /locks Protocols Configured : NFS
- On the OpenStack cluster, edit
manila.conf
as under[vinf-share] share_driver= manila.share.drivers.veritas.veritas_infoscale_manila. InfoscaleShareDriver driver_handles_share_servers = False share_backend_name = vinf-share vinf_server_ip = <Infoscale REST server IP address> vinf_port = <Infoscale REST port, default is 5637> vinf_user = <Infoscale REST administrator user> vinf_passwd = <Infoscale REST administrator user's password> vinf_dg = <Infoscale diskgroup on which CNFS cfsshare is configured> vinf_domain = <Infoscale domain> vinf_share_path = <path on Infoscale cluster where cfsshare is mounted> : [DEFAULT] : enabled_backends = lvmdriver-1,vinf-share :
- Copy
/opt/VRTS/openstack/drivers/veritas_infoscale_manila.py
tomanila/manila/share/drivers/veritas/
in the home directory of OpenStack user. - Restart manila services after configuration.
- On the OpenStack controller node, run the following commands to create a share type for va-backend1 and associate the share type to a share backend.
manila type-create <new-backend> False
manila type-key <new-backend> set driver_handles_share_servers=false share_backend_name=vinf-share
Table: Mapping of Manila commands to InfoScale
Manila command | InfoScale operation |
---|---|
Creation of a share | Creation of InfoScale Volume Creation of CNFS cfshsare on Volume |
Deletion of a share | Deletion of CNFS cfsshare Deletion of Volume used for cfsshare |
Creation of snapshot of a share | Creation of InfoScale Volume Creation of snapshot of a shared Volume on a newly created Volume. |
Deletion of snapshot of a share | Deletion of InfoScale Volume on which snapshot resides |
Creation of share from a snapshot of share | Creation of new InfoScale Volume Creation of snapshot of existing snapshot of share Creation of CNFS cfsshare from this new Volume |
Growing / Shrinking an existing manila share | Growing / Shrinking shared Volume |