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. InfoScale event logging
Setting custom permissions for InfoScale log files
InfoScale provides tunable parameters that let you modify the log file permissions as needed. You can set the custom permissions during an upgrade using the installer or post-upgrade using the component-specific tunable parameters.
Each InfoScale component has a unique tunable parameter to which you can assign a value to set the desired log file permissions for that component. You can do this manually using the relevant commands or by directly editing the individual component's configuration file.
Note:
When you set the permissions manually, you must restart the individual component service for the changes to take effect.
The log file permissions are set to the value that you provide, irrespective of whether you set the value during an upgrade or after the upgrade.
See Custom permissions for InfoScale log files.
To set log file permissions during upgrade
- When you upgrade an InfoScale product, the installer prompts you as follows:
Do you want to set the permission of the files as per EO logging standards? [y,n,q]
Enter y (Yes). The following prompt appears:
Please provide the proper permission option [b,q,?] (0)
- Enter ? to identify which value to use for a specific permission. The following options are displayed:
0 (default) - 600 permissions, update existing file permissions on upgrade 1 - 640 permissions, update existing file permissions on upgrade 2 - 644 permissions, update existing file permissions on upgrade 3 - Inherit umask, update existing file permissions on upgrade 10 - 600 permissions, don't touch existing file permissions on upgrade 11 - 640 permissions, don't touch existing file permissions on upgrade 12 - 644 permissions, don't touch existing file permissions on upgrade 13 - Inherit umask, don't touch existing file permissions on upgrade
Please provide the proper permission option [b,q,?] (0)
Enter a value from these available options to set the required permissions. For example, enter 10 to set the permissions of all the new log files to the default value of 600 (read-write access to owner), but not change any existing log file permissions.
Note that this value gets applied to all the InfoScale log files. Post upgrade, you can use the manual method to set permissions for log files at an individual component level.
Enter q at the prompt when you finish changing the file permissions as per your needs.
If you do not specify a value, 0 (zero) is considered as the default.
To set log file permissions after upgrade
- Use the appropriate command to set the component-specific tunable parameter.
For VxFS:
To directly set the parameter value, run:
# /opt/VRTS/bin/vxtunefs -D eo_perm=<parameter_value>
To edit the parameter value in the configuration file, run:
# cat /etc/vx/vxfssystem eo_perm <parameter_value>
For VxVM:
To directly set the parameter value, run:
# vxtune log_file_permissions <parameter_value>
For VCS:
To add the value in the
/opt/VRTSvcs/bin/vcsenv
file, run:# export VCS_ENABLE_PUBSEC_LOG_PERM=1
Note:
If there are other components under VCS control, for example, VxCPServ and VxFEN, then a VCS restart is also required for the log file permissions changes of those components to take effect.
For VxCPServ:
Add the VCS_ENABLE_PUBSEC_LOG_PERM=1 parameter value to the
/etc/vxcps.conf
file.For SFDB tools (DBED):
To add the value in the
/etc/vx/vxdbed/dbedenv
file, run:# export VCS_ENABLE_PUBSEC_LOG_PERM=1
For InfoScale Operations Manager:
To edit the
/etc/opt/VRTSsfmh/log_file_permissions.conf
configuration file, run:# /opt/VRTSsfmh/bin/perl /opt/VRTSsfmh/bin/set_logfiles_permissions.pl --logfile_permission=<parameter_value>
Note:
The Inherit umask tunable values (3 and 13) are supported only on Linux.
- Either restart the component-specific services or restart the system for the changes to take effect.
In case of a coordination point server (CP server) configuration under VCS control, stop and restart the
vxcpserv
process using the hastop and hastart commands locally.In case of a CP server configuration in a single-node VCS cluster, use the hastart -onenode command.
In case of SFDB tools, to restart the
vxdbd
daemon, run:# /opt/VRTS/bin/sfae_config disable
# /opt/VRTS/bin/sfae_config enable
In case of systemd environments with the supported Linux distributions, the umask values need to be update at the system level and at the service level. Arctera recommends that you set the same umask values at both levels. Otherwise, you may encounter inconsistent message logging behavior due to discrepancies in the InfoScale log file permissions.
Update the umask values in the following system files:
/etc/bashrc
/etc/init.d/functions
/etc/login.defs
/etc/profile
/etc/rc.d/init.d/functions
Then, update the umask values in the service files. The following procedure uses the example of the InfoScale I/O fencing service (vxfen
).
To set umask values for log files that get updated through systemd
- Edit the service file.
# systemctl edit vxfen
- Add the umask setting to the file and save the changes.
[Service] UMask=0070
- Update the systemd environment for the changes to take effect.
# systemctl daemon-reload