Veritas Access Appliance 8.2 Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Managing licenses
- Configuring the network
- About configuring the Access Appliance network
- About bonding Ethernet interfaces
- Bonding Ethernet interfaces
- Considerations for configuration a LACP bond
- Configuring DNS settings
- About Ethernet interfaces
- Displaying current Ethernet interfaces and states
- Configuring IP addresses
- Configuring IP addresses and FQDNs in a non-DNS environment
- Configuring VLAN interfaces
- Configuring NIC devices
- About configuring routing tables
- Configuring routing tables
- Changing the firewall settings
- Configuring Access Appliance in IPv4 and IPv6 mixed mode
- Support for multiple data subnets
- Adding console FQDN to the network and accessing the GUI using the console FQDN
- Configuring authentication services
- About configuring LDAP settings
- Configuring LDAP server settings
- Administering the Access Appliance cluster's LDAP client
- About Active Directory (AD)
- Configuring AD server settings
- Configuring entries for Access Appliance DNS for authenticating to Active Directory (AD)
- Configuring AD/LDAP using the GUI
- Configuring NSS lookup order
- Sign-in options for the Access Appliance UI
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance 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
- Workflow for configuring and managing storage using the Access Appliance 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
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- About using the NFS server with Access Appliance
- Using the kernel-based NFS server
- Accessing the NFS server
- Displaying and resetting NFS statistics
- Configuring Access Appliance 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 Access Appliance as a CIFS server
- About configuring Access Appliance for CIFS
- About configuring CIFS for Active Directory (AD) domain mode
- Adding an SPN entry on the Windows client
- About setting 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
- Enabling CIFS data migration
- Using Access Appliance as an Object Store server
- About the Object Store server
- Use cases for configuring the Object Store server
- Configuring the Object Store server
- About buckets and objects
- File systems used for objectstore buckets
- Enabling WORM on buckets
- Object Access SSL certificate
- Object Access endpoints
- S3 with NFS use case
- S3 with NSP use case
- Configuring the S3 server using GUI
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Managing security
- Setting up FIPS mode
- Configuring STIG
- Setting the banner
- Setting the password policy
- Immutability in Access Appliance
- Deploying certificates on Access Appliance
- Single Sign-On (SSO)
- Configuring multifactor authentication
- About multifactor authentication
- Considerations when configuring multifactor authentication
- Configuring multifactor authentication for your user account
- Disabling multifactor authentication for your user account
- Enforcing multifactor authentication for all users
- Configuring multifactor authentication for your user account when it is enforced in the cluster
- Resetting multifactor authentication for a user
- Section VI. Monitoring and troubleshooting
- Monitoring the appliance
- Configuring event notifications and audit logs
- About troubleshooting
- Monitoring command activity
- Monitoring alerts
- About alert management
- Monitoring events
- Viewing reports
- Viewing cluster storage usage
- Viewing file system usage
- About event notifications
- About severity levels and filters
- About SNMP notifications
- Configuring a syslog server
- Displaying events on the console
- Appliance log files
- Section VII. Provisioning and managing Access Appliance 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 FastResync
- About fsck operation
- Enabling WORM on a file system
- 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 VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About NFS file sharing
- About the NFS shares
- 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
- About the 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
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- About Access Appliance episodic replication
- How Access Appliance Replication works
- Starting Access Appliance 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
- Configuring an episodic replication job using the GUI
- Episodic replication job failover and failback
- Configuring continuous replication
- About Access Appliance continuous replication
- How Access Appliance continuous replication works
- Starting Access Appliance continuous replication
- Setting up communication between the source and the destination clusters
- Setting up the file system to replicate
- Managing continuous replication
- Displaying continuous replication information and status
- Unconfiguring continuous replication
- Preserving the file system on the destination cluster
- Cloud tiering with continuous replication
- Configuring Enterprise Vault with continuous replication
- Configuring a continuous replication job using the GUI
- Continuous replication failover and failback
- Addition of multiple file systems to a Replicated Volume Group
- Using snapshots
- Using instant rollbacks
- About instant rollbacks
- Creating a space-optimized rollback
- Creating a full-sized rollback
- Listing Access Appliance 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 Access Appliance instant rollbacks
- Listing cache objects
- Destroying a cache object of a Access Appliance instant rollback
- Configuring episodic replication
- Section X. Reference
- Index
Creating a file system
Access Appliance supports the following types of file systems:
Cluster File System (CFS) - creates a standard CFS file system. The CFS file system is the default file system when creating a new file system.
Access Appliance supports the following file system layouts:
Simple - creates a file system of a specified size, and you can specify a block size for the file system.
Mirrored - creates a mirrored file system with a specified number of mirrors along with a list of pools and online status.
Mirrored-stripe - creates a mirrored-stripe file system with a specified number of columns, mirrors, pools, and protection options.
Striped - creates a striped file system. A striped file system is a file system that stores its data across multiple disks rather than storing the data on just one disk.
Striped-mirror - creates a striped-mirror file system with a specified number of columns, mirrors, pools, and protection options.
The default block size is determined based on the size of the file system when the file system is created. For example, 1 KB is the default block size for up to a 2-TB file system size. Other default block sizes, 2 KB, 4 KB, and 8 KB are available for different ranges of file system sizes. If you create a 1-TB file system, and then increase it to 3 TB, the file system block size remains at 1 KB.
See the storage_fs(1) man page for detailed examples.
For details on the limitations on the length of the file system name, See About creating and maintaining file systems.
You can also create a file system for customized workloads.
Note:
If the configuration file system creation fails, the originating file system request also fails. Access Appliance requires at least two disks for the mirrored configuration file system, and in case of Flexible Shared Storage (FSS), at least two nodes are required to be part of the storage pool.
Note:
Veritas recommends that you do not create a file system whose name format is such as <file system name_integer>. This is because such file names are reserved for internal objects and may lead to file system creation errors.
To create a simple file system of a specified size
- Create a simple file system with a specified size.
Storage> fs create simple fs_name size pool1[,disk1,...] [blksize] [pdir_enable] [encrypt] [worm] [minret] [maxret]
To create a mirrored file system
- Create a mirrored file system.
Storage> fs create mirrored fs_name size nmirrors pool1[,disk1,...] [protection=disk|pool] [blksize=bytes] [pdir_enable] [encrypt] [worm] [mediatype] [multi_volume] [minret] [maxret]
To create a mirrored-stripe file system
- Create a mirrored-stripe file system.
Storage> fs create mirrored-stripe fs_name size nmirrors ncolumns pool1[,disk1,...] [protection=disk|pool] [stripeunit=kilobytes] [blksize=bytes] [pdir_enable] [encrypt] [worm] [mediatype] [minret] [maxret]
To create a striped-mirror file system
- Create a striped-mirror file system.
Storage> fs create striped-mirror fs_name size nmirrors ncolumns pool1[,disk1,...] [protection=disk|pool] [stripeunit=kilobytes] [blksize=bytes] [pdir_enable] [encrypt] [worm] [mediatype] [multi_volume] [minret] [maxret]
To create a striped file system
- Create a striped file system.
Storage> fs create striped fs_name size ncolumns pool1[,disk1,...] [stripeunit=kilobytes] [blksize=bytes] [pdir_enable] [encrypt] [worm] [minret] [maxret]
fs_name | Specifies the name of the file system being created. The file system name should be a string. If you enter a file that already exists, you receive an error message and the file system is not created. |
size | Specifies the size of a file system. To create a file system, you need at least 10 MB of space. You can create a file system in the following units:
You can enter the units with either uppercase (10 M) or lowercase (10 m) letters. To see how much space is available on a pool, use the Storage> pool free command. |
nmirrors | Specifies the number of mirrors for the file system. You must enter a positive integer. |
ncolumns | Specifies the number of columns for the striped file system. The number of columns represents the number of disks to stripe the information across. If the number of columns exceeds the number of disks for the entered pools, an error message is displayed. This message indicates that there is not enough space to create the striped file system. |
pool1[,disk1,...] | Specifies the pool(s) or disk(s) for the file system. If you specify a pool or disk that does not exist, you receive an error message. You can specify more than one pool or disk by separating the name with a comma. Do not include a space between the comma and the name. To find a list of pools and disks, use the Storage> pool list command. To find a list of disks, use the Storage> disk list command. The disk must be part of the pool or an error message is displayed. |
protection | If you do not specify a protection option, the default is "disk." The available options for this field are:
|
stripeunit=kilobytes | Specifies a stripe unit (in kilobytes). The following are the possible values:
|
blksize=bytes | Specifies the block size for the file system. The following are the possible values in bytes:
Block sizes can affect the file size. For example, to create a file system greater than 32 TB, the block size needs to be 8192. |
pdir_enable | Specifies if you want to enable a partition directory for the file system. By default, this feature is not enabled. |
encrypt | Enable encryption. You can set encrypt=on/encrypt=off. |
worm | Enables WORM. The possible values are worm=yes/worm=no. |
mediatype | Specifies the disk type for the file system. |
multi_volume | Create multiple volumes. |
minret | Specifies the minimum file system retention period. It can contain: [1-9](s|S|h|H|d|D|m|M|y|Y). |
maxret | Specifies the maximum file system retention period. It can contain: [1-9](s|S|h|H|d|D|m|M|y|Y). |
After a file system is created, the file system reserves some space for internal logging. Internal logging provides additional data integrity. Due to the space that is reserved for internal logging, the file system may appear to be used immediately after file system creation. The space that is reserved for internal logging increases with the number of nodes in the Access Appliance cluster.
Log file sizes for the file systems are as follows:
10 GB to 100 GB | Log size = 60 MB per node |
100 GB to 1 TB | Log size = 100 MB per node |
1 TB and above | Log size = 256 MB per node |