Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access- Adding users or roles
- Configuring the network- About configuring the Veritas Access network
- About bonding Ethernet interfaces
- Bonding Ethernet interfaces
- Configuring DNS settings
- About Ethernet interfaces
- Displaying current Ethernet interfaces and states
- Configuring IP addresses
- Configuring Veritas Access to use jumbo frames
- Configuring VLAN interfaces
- Configuring NIC devices
- Swapping network interfaces
- Excluding PCI IDs from the cluster
- About configuring routing tables
- Configuring routing tables
- Changing the firewall settings
- IP load balancing
- Configuring Veritas Access in IPv4 and IPv6 mixed mode
 
- Configuring authentication services
 
- Section III. Managing Veritas Access storage- Configuring storage- About storage provisioning and management
- About configuring disks
- About configuring storage pools
- Configuring storage pools
- About quotas for usage
- Enabling, disabling, and displaying the status of file system quotas
- Setting and displaying file system quotas
- Setting user quotas for users of specified groups
- About quotas for CIFS home directories
- About Flexible Storage Sharing
- Limitations of Flexible Storage Sharing
- Workflow for configuring and managing storage using the Veritas Access CLI
- Displaying information for all disk devices associated with the nodes in a cluster
- Displaying WWN information
- Importing new LUNs forcefully for new or existing pools
- Initiating host discovery of LUNs
- Increasing the storage capacity of a LUN
- Formatting or reinitializing a disk
- Removing a disk
 
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
 
- Configuring storage
- Section IV. Managing Veritas Access file access services- Configuring the NFS server- About using the NFS server with Veritas Access
- Using the kernel-based NFS server
- Accessing the NFS server
- Displaying and resetting NFS statistics
- Configuring Veritas Access for ID mapping for NFS version 4
- Configuring the NFS client for ID mapping for NFS version 4
- About authenticating NFS clients
- Setting up Kerberos authentication for NFS clients
 
- Using Veritas Access as a CIFS server- About configuring Veritas Access for CIFS
- About configuring CIFS for standalone mode
- Configuring CIFS server status for standalone mode
- Changing security settings
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- Setting NTLM
- About setting trusted domains- Specifying trusted domains that are allowed access to the CIFS server
- Allowing trusted domains access to CIFS when setting an IDMAP backend to rid
- Allowing trusted domains access to CIFS when setting an IDMAP backend to ldap
- Allowing trusted domains access to CIFS when setting an IDMAP backend to hash
- Allowing trusted domains access to CIFS when setting an IDMAP backend to ad
- About configuring Windows Active Directory as an IDMAP backend for CIFS
- Configuring the Active Directory schema with CIFS-schema extensions
- Configuring the LDAP client for authentication using the CLI
- Configuring the CIFS server with the LDAP backend
- Setting Active Directory trusted domains
 
- About storing account information
- Storing user and group accounts
- Reconfiguring the CIFS service
- About mapping user names for CIFS/NFS sharing
- About the mapuser commands
- Adding, removing, or displaying the mapping between CIFS and NFS users
- Automatically mapping UNIX users from LDAP to Windows users
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- Setting the CIFS aio_fork option
- About managing local users and groups
- Enabling CIFS data migration
 
- Configuring an FTP server- About FTP
- Creating the FTP home directory
- Using the FTP server commands
- About FTP server options
- Customizing the FTP server options
- Administering the FTP sessions
- Uploading the FTP logs
- Administering the FTP local user accounts
- About the settings for the FTP local user accounts
- Configuring settings for the FTP local user accounts
 
- Using Veritas Access as an Object Store server
 
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems- Creating and maintaining file systems- About creating and maintaining file systems
- About encryption at rest
- Considerations for creating a file system- Best practices for creating file systems
- Choosing a file system layout type
- Determining the initial extent size for a file system
- About striping file systems
- About creating a tuned file system for a specific workload
- About FastResync
- About fsck operation
- Setting retention in files
- Setting WORM over NFS
- Manually setting WORM-retention on a file over CIFS
- About managing application I/O workloads using maximum IOPS settings
 
- Creating a file system
- Bringing the file system online or offline
- Listing all file systems and associated information
- Modifying a file system
- Managing a file system
- Destroying a file system
- Upgrading disk layout versions
 
 
- Creating and maintaining file systems
- Section VII. Provisioning and managing Veritas Access shares- Creating shares for applications
- Creating and maintaining NFS shares- About NFS file sharing
- Displaying file systems and snapshots that can be exported
- Exporting an NFS share
- Displaying exported directories
- About managing NFS shares using netgroups
- Unexporting a directory or deleting NFS options
- Exporting an NFS share for Kerberos authentication
- Mounting an NFS share with Kerberos security from the NFS client
- Exporting an NFS snapshot
 
- Creating and maintaining CIFS shares- About managing CIFS shares
- Exporting a directory as a CIFS share
- Configuring a CIFS share as secondary storage for an Enterprise Vault store
- Exporting the same file system/directory as a different CIFS share
- About the CIFS export options
- Setting share properties
- Displaying CIFS share properties
- Hiding system files when adding a CIFS normal share
- Allowing specified users and groups access to the CIFS share
- Denying specified users and groups access to the CIFS share
- Exporting a CIFS snapshot
- Deleting a CIFS share
- Modifying a CIFS share
- Making a CIFS share shadow copy aware
 
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
 
- Section VIII. Managing Veritas Access storage services- Compressing files- About compressing files
- Use cases for compressing files
- Best practices for using compression
- Compression tasks- Compressing files
- Showing the scheduled compression job
- Scheduling compression jobs
- Listing compressed files
- Uncompressing files
- Modifying the scheduled compression
- Removing the specified schedule
- Stopping the schedule for a file system
- Removing the pattern-related rule for a file system
- Removing the modified age related rule for a file system
 
 
- Configuring episodic replication- About Veritas Access episodic replication
- How Veritas Access episodic replication works
- Starting Veritas Access episodic replication
- Setting up communication between the source and the destination clusters
- Setting up the file systems to replicate
- Setting up files to exclude from an episodic replication unit
- Scheduling the episodic replication
- Defining what to replicate
- About the maximum number of parallel episodic replication jobs
- Managing an episodic replication job
- Replicating compressed data
- Displaying episodic replication job information and status
- Synchronizing an episodic replication job
- Behavior of the file systems on the episodic replication destination target
- Accessing file systems configured as episodic replication destinations
- Episodic replication job failover and failback
 
- Configuring continuous replication- About Veritas Access continuous replication
- How Veritas Access continuous replication works
- Starting Veritas Access continuous replication
- Setting up communication between the source and the target clusters
- Setting up the file system to replicate
- Managing continuous replication
- Displaying continuous replication information and status
- Unconfiguring continuous replication
- Continuous replication failover and failback
 
- Using snapshots
- Using instant rollbacks- About instant rollbacks
- Creating a space-optimized rollback
- Creating a full-sized rollback
- Listing Veritas Access instant rollbacks
- Restoring a file system from an instant rollback
- Refreshing an instant rollback from a file system
- Bringing an instant rollback online
- Taking an instant rollback offline
- Destroying an instant rollback
- Creating a shared cache object for Veritas Access instant rollbacks
- Listing cache objects
- Destroying a cache object of a Veritas Access instant rollback
 
 
- Compressing files
- Section IX. Reference
- Index
Configuring the Object Store server
To configure the Object Store server
- Log on to Veritas Access using the Veritas Access command-line interface.
- You can either use an existing pool or create a default storage pool (at least one) on the cluster.You can see the list of existing pools using the storage pool list command. You can create a new pool using the storage create pool command. storage> pool create pool1 disk1,disk2,disk3,disk4 
- Use the storage pool that was created in Step 2 as the default object access pool.You need to set the default pool, as it is required for enabling the Object Store server. objectaccess> set pools pool1 Note: Based on your storage requirements, you can configure different types of storage pools by using the Object Store group commands. 
- Verify the configured storage pool.objectaccess> show 
- Enable and start the Object Store server. objectaccess> server enable objectaccess> server start 
- Configure the cluster using any authentication server (AD, LDAP, or NIS).See the following manual pages for more information on configuring AD, LDAP, or NIS: - CLISH> network man ldap 
- CLISH> network man ad 
- CLISH> network man nis 
 
- Create the access and secret keys for the authorized user, or any user in the authentication server.You have two options for creating the access and the secret keys, either using the Veritas Access RESTful APIs or by using the Veritas Access helper script. Create the access and secret keys using the Veritas Access RESTful APIs: - Before using the Veritas Access RESTful APIs, set the host name resolution for the host as shown in the objectaccess> show output against ADMIN_URL. 
- See the Veritas Access Object Access API Guide on the SORT site for accessing the Object Store server (S3) user management APIs. 
- After creating your access and secret key, you can create a bucket using the S3 API. 
 Create the access and the secret keys using the Veritas Access helper script: - Add the ADMIN_URL name in your /etc/hosts file. - where the ADMIN_URL is admin.<cluster_name> and the port is 8144. This url should point to the Veritas Access management console IP address. 
- Location of the helper script: - /opt/VRTSnas/scripts/utils/objectaccess/objectaccess_client.py
- The Veritas Access helper script can be used from any client system that has Python installed. 
- To run the script, your S3 client needs to have the argparse and requests Python modules. - If these modules are missing, install both these modules using pip or easy_install. 
- If the Object Store server is enabled without the SSL option, you need to add the --insecure option. - clus_01 ~# ./objectaccess_client.py --server admin.clus:8144 --username <uname> --create_key --insecure 
- Create the access and the secret key using the Veritas Access helper script by providing the user name, password, and ADMIN_URL (check the online Help of the Veritas Access helper script for all of the provided operations like list key and delete key). - Create a secret key: - clus_01:~ # ./objectaccess_client.py --create_key --server admin.clus:8144 --username localuser1 --password root123 --insecure UserName : localuser1 AccessKeyId : Y2FkODU2NTU2MjVhYzV Status : Active SecretAccessKey : ODk0YzQxMDhkMmRjM2M5OTUzNjI5OWIzMDgyNzY - The <localuser1> is the local user created on both the Veritas Access cluster nodes with same unique ID. - List a secret key for the specified user: - clus_01:~ # ./objectaccess_client.py --list_key --server admin.clus:8144 --username localuser2 --password root123 --insecure - Delete a secret key for the specified user: - clus_01:~ # ./objectaccess_client.py --delete_key ZTkyNDdjZTViM2EyMWZ --server admin.clus:8144 --username localuser2 --password root123 --insecure 
 
- Use the following objectaccess command to see all the existing access and secret keys in the Veritas Access cluster:objectaccess> account user show 
It is possible to change an already set parameter or set new parameters by specifying different options. For example, you can change the other Object Store server defaults, such as fs_type, fs_size, and other options.
After setting the defaults, you can verify whether the proper value is assigned or not.
objectaccess> set fs_type
mirrored mirrored-stripe simple striped striped-mirror
objectaccess> set fs_type simple ACCESS ObjectAccess INFO V-288-0 Set fs_type successful.
objectaccess> set fs_size 2G ACCESS ObjectAccess INFO V-288-0 Set operation successful.
objectaccess> show Name Value ============= ========================= Server Status Enabled Admin_URL http://endpoint1:8144 S3_URL http://dataendpoint:8143 admin_port 8144 s3_port 8143 ssl no max_s3_threads 8 pools pool_default fs_size 2g fs_type simple fs_blksize 8192 fs_pdirenable yes fs_encrypt off fs_worm yes retention_min 3600s retention_max 36000s
If you have multiple users, and you want to set different default values for different sets of users, you can use the group option.
You can also use the group option to use the existing file systems for bucket creation instead of creating a new file system for every bucket. If you set the group fs_sharing option to yes, and if any request for bucket creation comes from a user who is part of that group, then the S3 server searches for any existing file system created by the specific group user. If an existing file system is found, it uses the existing file system. Otherwise, it creates a new file system for the bucket.
To use the group option
- Create a group in the authentication server (AD/LDAP/NIS) and add the required users to that group.
- Set the group specific configuration for the group created in the authentication server.
- Set or unset the defaults per your requirements.objectaccess> group set fs_type simple VRTS-grp ACCESS ObjectAccess INFO V-288-0 Group set fs-type successful. objectaccess> group set pool VRTS-grp pool1 ACCESS ObjectAccess INFO V-288-0 Success. objectaccess> group show Group Name Fs Sharing Fs Size Fs Type Pool(s) =========== =========== ======== ======== ======== VRTS-grp - - simple pool1 objectaccess> group show Group Name Fs Sharing Fs Size Fs Type Pool(s) =========== =========== ======== ======== ======== VRTS-grp - - - pool1