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 IP addresses
During installation, you specified a range of public IP addresses to be used for physical interfaces. You also specified a range for virtual interfaces. You can see which of these addresses are assigned to each node. You can use this procedure to verify the IP addresses in your configuration. You can add additional IP addresses if you want to add additional nodes and no other IP addresses are available.
To display all the IP addresses for the cluster
- To display all of a cluster's IP addresses, enter the following:
Network> ip addr show
The output headings are:
IP
Displays the IP addresses for the cluster.
Netmask
Displays the netmask for the IP address. Netmask is used for IPv4 addresses.
Specify an IPv4 address in the format AAA.BBB.CCC.DDD, where each number ranges from 0 to 255.
Prefix
Displays the prefix used for IPv6 addresses. The value is an integer in the range 0-128.
Device
Displays the name of the Ethernet interface for the IP address.
Node
Displays the node name associated with the interface.
Type
Displays the type of the IP address: physical or virtual.
Status
Displays the status of the IP addresses:
ONLINE
ONLINE (console IP)
OFFLINE
FAULTED
A virtual IP can be in the FAULTED state if it is already being used. It can also be in the FAULTED state if the corresponding device is not working on all nodes in the cluster (for example, a disconnected cable).
To add an IP address to a cluster
- To add an IP address to a cluster, enter the following:
Network> ip addr add ipaddr netmask | prefix type [device] [nodename] [fqdns]
ipaddr | Specifies the IP address to add to the cluster. Do not use physical IP addresses to access the Veritas Access cluster. In case of failure, the IP addresses cannot move between nodes. A failure could be either a node failure, an Ethernet interface failure, or a storage failure. You can specify either an IPv4 address or an IPv6 address. |
netmask | Specifies the netmask for the IP address. Netmask is used for IPv4 addresses. |
prefix | Specifies the prefix for the IPv6 address. The accepted range is 0-128 integers. |
type | Specifies the IP address type, either virtual or physical. If type is virtual, the device is used to add new IP address on that device. If type is physical, the IP address gets assigned to given node on given device. In this case, you have to specify the nodename. |
device | Only use this option if you entered virtual for the type. |
nodename | Any node of the cluster |
fqdns | Specifies a comma-separated list of Fully Qualified Domain Name (FQDN) of the IP address. The fqdn can include the characters: a-z|A-Z|0-9 or a hyphen (-). Each level of the FQDN should be between 1 and 63 characters long and should not start or end with a hyphen (-). The last Top Level Domain (TLD) must be at least two characters and have a maximum of six characters. |
To change an IP address to online on a specified node
- To change an IP address to online on a specified node, enter the following:
Network> ip addr online ipaddr nodename
ipaddr
Specifies the IP address that needs to be brought online. You can specify either an IPv4 address or an IPv6 address.
nodename
Specifies the nodename on which the IP address needs to be brought online. If you do not want to enter a specific nodename, enter any with the IP address.
You can also modify an IP address. But note that you cannot use the ipr addr modify command to modify the IP addresses in the following scenarios:
IP is used by the NetBackup client
Replication IP
IP is used by deduplication service
IP is used by Veritas Data Deduplication server
IP is used by the NetBackup primary server
IP is used by the NetBackup media server
To modify an IP address
- To modify an IP address, enter the following:
Network> ip addr modify oldipaddr newipaddr netmask | prefix fqdns
oldipaddr
Specifies the old IP address to be modified, as either an IPv4 address or an IPv6 address. The specified oldipaddr must be assigned to the cluster.
newipaddr
Specifies the new IP address, as either an IPv4 address or an IPv6 address. The new IP address must be available.
netmask
Specifies the netmask for the new IP address. Netmask is used for IPv4 addresses.
prefix
Specifies the prefix for the IPv6 address. The value is an integer in the range 0-128.
fqdns
Specifies a comma-separated list of Fully Qualified Domain Name (FQDN) of the IP address. The fqdn can include the characters: a-z|A-Z|0-9 or a hyphen (-). Each level of the FQDN should be between 1 and 63 characters long and should not start or end with a hyphen (-). The last Top Level Domain (TLD) must be at least two characters and have a maximum of six characters.
fqdns can have NONE value. NONE is used to remove the existing FQDN entry from the
/etc/hostsfile.
To remove an IP address from the cluster
- To remove an IP address from the cluster, enter the following:
Network> ip addr del ipaddr
where ipaddr is either an IPv4 address or an IPv6 address.