InfoScale™ 9.0 Storage Foundation Administrator's Guide - Linux
- Section I. Introducing Storage Foundation
- Overview of Storage Foundation
- 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
- 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
- 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 sites and remote mirrors
- 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. 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 VII. Optimizing storage with Storage Foundation
- Understanding storage optimization solutions in Storage Foundation
- 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
- Section VIII. 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 IX. 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
- 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 X. 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
- Appendix C. Command reference
- Appendix D. Executive Order logging
Configure SecureFS for PostgreSQL using CLI
The following steps describe how to configure SecureFS for PostgreSQL application using the command line (CLI).
You can also configure SecureFS using the InfoScale Operations Manager (VIOM) GUI. Refer to the VIOM documentation for more details.
To configure SecureFS for PostgreSQL using CLI
- Run the command to ensure that
vxfstaskd
is in an active state.# systemctl status vxfstaskd
- Enable Compliance (WORM) or Enterprise (SoftWORM) on data file mount point.
# /opt/VRTS/bin/fsadm -o <worm/softworm> <mount point>
Sample command:
# /opt/VRTS/bin/fsadm -o worm /dbmnt
- Create a secureFS config file on the data file mount point.
# /opt/VRTS/bin/vxschadm create <mount point>
Sample command:
# /opt/VRTS/bin/vxschadm create /dbmnt
- Configure SecureFS for PostgreSQL.
Run the following command if the authentication mode is set to Trust:
# vxschadm add application postgres --pguser postgres --pgauth trust --pgdata /db/pdata --pgarc /arcmnt
Run the following command if the authentication mode is set to Peer:
# vxschadm add application postgres --pguser postgres --pgauth peer --pgdata /db/pdata --pgarc /arcmnt --pgsysuser postgres
- Enable the checkpoint feature on the data file mount point.
# /opt/VRTS/bin/vxschadm add checkpoint <interval in os cron format> <maximum number of checkpoints> <retention period of checkpoint> <time mode> <removable> <mount_point>
Time interval
Format : "mm hh dd MM ww" mm : minutes (0-59) or * hh : hours (0-23) or * dd : days (1-31) or * MM: months (1-12) or * ww: week (0-6) SUNDAY=0, SATURADAY=6
*: Refers 'per', for example per minute, per hour, and so on.
Time mode can be:
m : minutes h : hours d : days M : months y : years
Sample command and output:
# /opt/VRTS/bin/vxschadm add checkpoint "59 15 * * *" 5 1 h 1 /dbmnt
Following are the sample output of the snapshot format:
Example 1: "30 15 * * *" Output: Every day at 1530 hours, the task is run.
Example 2: "30 15 * * 6" :Output: Every Saturday at 1530 hours, the task is run.
Caution: "* * * * *"
Every minute and hour options are not supported.
- If the PostgreSQL instance is under VCS control, you must mark the file system where the PostgreSQL database (DB) resource is online as primary. You can mark the file system as primary by setting the PostgreSQL resource's
SetFSPrimary
attribute value to 1.The
SetFSPrimary
attribute for PostgreSQL resource in VCS configures the file system as primary on the node where the PostgreSQL DB resource is online. This attribute plays an important role when the PostgreSQL database is set up as a VCS resource in the PostgreSQL service group that includes both CFSmount and CVMVoldg resources.Run the following commands to enable the
SetFSPrimary
attribute:# /opt/VRTSvcs/bin/haconf -makerw # /opt/VRTSvcs/bin/hares -modify PostgreSQLresourcename SetFSPrimary 1 # /opt/VRTSvcs/bin/haconf -dump -makero
Note the following when you use this attribute in SecureFS configuration:
This attribute takes effect only when Cluster Server (VCS) manages the startup of the application.
If an application mount point is added after the VCS resource is online, then to mark the mount point as primary on the file system, you must restart the VCS application service group.
When the PostgreSQL resource is online on a node, the InfoScale cluster file system (CFS) should be primary on that same node to ensure that the SecureFS feature functions correctly. To achieve this, set
SetFSPrimary
to 1 where the PostgreSQL resource is present. WithSetFSPrimary
set to 1, the PostgreSQL agent resource ensures that the underlying CFS mount is primary on that node.
If the PostgreSQL instance is not under VCS control, ensure that the FS primary of data file mount point is the system where the PostgreSQL instance is up and running.
Interval of less than one hour is not supported. The checkpoints that get created are non-modifiable checkpoints and can only be mounted in read-only mode. If a new data file or log directory is added to PostgreSQL application and that file or directory is on a new file system, such file system automatically becomes part of the SecureFS configuration on the next checkpoint schedule. Manual intervention is not required.
All SecureFS configuration file operations that are done using # /opt/VRTS/bin/vxschadm must be on the data file mount point.
Note:
Operations that are performed on redo and archive file system can lead to undefined behavior. Previously taken checkpoints and modes that are WORM and aulog, remain as is, even after you delete the checkpoint feature.