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
Prerequisites for configuring SecureFS for PostgreSQL
Note the following requirements before you configure secure file system (SecureFS) for PostgreSQL database.
SecureFS for PostgreSQL is supported on InfoScale 9.0 release onward.
The InfoScale storage disk layout version must be 17 or later.
For enhanced security and resiliency, InfoScale 9.0 introduces a new configuration file format for storing the configuration data in a secure and non-user accessible location. If you want to use the secure file format, you must upgrade the disk layout version (DLV) to 18 and then upgrade the application mount point.
Run the following command to update the DLV version:
# vxupgrade <mount_point>
Run the following command to update to the new secure file format:
# vxschadm update <applicationmaindatadirmountpoint>
Run the command for the PostgreSQL's primary file system (
$PGDATA
) and for all the other mount points used by PostgreSQL.SecureFS for PostgreSQL requires the
libpq
package. Verify that the package is installed on all the nodes.
SecureFS is supported for PostgreSQL version 14 or later.
Ensure that the PostgreSQL application is installed and configured. Verify that the PostgreSQL service is up and running on the node from where you run the SecureFS configuration commands.
Each PostgreSQL instance must use a unique file system. Sharing file systems between instances might lead to SecureFS configuration failures. Ensure that no two PostgreSQL instances share the same file system.
The user authentication method that is specified during SecureFS command execution must be preconfigured in the PostgreSQL backend configuration files, pg_hba.conf
or pg_ident.conf
.
To specify the authentication method in the PostgreSQL configuration:
Open the PostgreSQL configuration files,
pg_hab.conf
, andpg_ident.conf
, in a text editor.Add an appropriate entry depending on your preferred user authentication method.
Save and close the configuration file.
Reload the PostgreSQL service for the changes to take effect.
Run the following command:
# pg_ctl reload -D $PGDATA
The PostgreSQL archive location must reside on a InfoScale File System (VxFS). Modify the PostgreSQL settings and ensure that a VxFS target location is specified.
Ensure that all the directories used by PostgreSQL for storing data and log files reside on a VxFS file system. This allows SecureFS to checkpoint all these file systems in application consistent manner.
Perform the following steps:
Open the
postgresql.conf
file in a text editor.Modify the
archive_command
andarchive_mode
parameters to ensure that the archive location resides on a VxFS file system.Save and close the configuration file.
Restart PostgreSQL for the changes to take effect.
Run the following command:
# pg_ctl restart -D $PGDATA
or,
# systemctl restart <PostgreSQL Service>
To avoid SecureFS configuration failures, ensure that the PostgreSQL archive location resides on a VxFS file system that is different from the VxFS file system where PostgreSQL is deployed.
Ensure that you specify a different VxFS mount point for the archive location. Verify that the mount point is not on a VxFS file system that is already in use by any other PostgreSQL instance.
The PostgreSQL data directory (pg_datadir
) and archive file system (pg_arcfs
) locations can be specified as symbolic links. SecureFS automatically resolves these links and extracts the corresponding mount points that they point to. Additionally, SecureFS also validates whether these mount points reside on a VxFS file system and are WORM or Soft WORM enabled.
Ensure that the symbolic links for pg_datadir
and pg_arcfs
resolve to mount points on a VxFS file system and the main data file system is WORM and Soft WORM enabled.
PostgreSQL tablespace file systems must reside on VxFS file systems. Backups might fail for non-VxFS tablespaces. SecureFS creates a distinct list of tablespace mount points to avoid potential conflicts. Arctera recommends that you avoid using the same VxFS file system for tablespaces and PostgreSQL main data files.
This is a mandatory requirement for configuring SecureFS and Single-Click Recovery features for PostgreSQL. Set the restore_command
attribute in the PostgreSQL configuration to enable backups.
See Enabling PostgreSQL for SecureFS and Single-Click Recovery.