Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Using Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
Increasing the size of a file system
To increase (grow) the size of a file system, it must be online. If the file system is not online, an error message is displayed, and no action is taken.
To increase the size of a file system to a specified size
- To increase the size of a file system to a specified size, enter the following:
Storage> fs growto tier_name fs_name new_length [pool1[,disk1,...]] [protection=disk|pool] [balanced] [num_vols]
If no pool is specified with the command, the disks for growing the file system can be taken from any available pool. The protection flag takes the default value of disk in this case. The value of the protection field cannot be set to pool when no pool is specified with the command. This operation may convert the layout of the file system if the command determines that the new file system is too large for the original layout.
If balanced=yes, all the volumes of the file system are grown by the same percentage which is calculated based on the specified new_length. If balanced=no, the file system is grown linearly starting from the last volume.
To increase the size of a file system by a specified size
- To increase the size of a file system by a specified size, enter the following:
Storage> fs growby tier_name fs_name length_change [pool1[,disk1,...]] [protection=disk|pool] [balanced] [num_vols]
If no pool is specified with the command, the disks for growing the file system can be taken from any available pool. The protection flag takes the default value of disk in this case. The value of the protection field cannot be set to pool when no pool is specified with the command. This operation may convert the layout of the file system if the command determines that the new file system is too large for the original layout.
If balanced=yes, all the volumes of the file system are grown by the same percentage which is calculated based on the specified length_change. If balanced=no, the file system is grown linearly starting from the last volume.
fs_name
Specifies the file system whose size is increased. If you specify a file system that does not exist, an error message is displayed.
tier_name
Specifies the tier name.
new_length
Expands the file system to a specified size. The size that you specify must be a positive number, and it must be bigger than the size of the existing file system. If the new file system is not larger than the size of the existing file system, an error message is displayed, and no action is taken.
This variable is used with the Storage> fs growto command.
length_change
Expands the file system by a specified size. The size that you specify must be a positive number, and it must be lesser than the available space. If it exceeds the available space, an error message is displayed, and no action is taken.
This variable is used with the Storage> fs growby command.
pool1[,disk1,...]
Specifies the pool(s) or disk(s) to use for the file system. If you specify a pool or disk that does not exist, an error message is displayed, and the file system is not resized. You can specify more than one pool or disk by separating the name with a comma; however, do not include a space between the comma and the name.
To find a list of existing pools and disks, use the Storage> pool list command.
See About configuring storage pools.
To find a list of the existing disks, use the Storage> disk list command.
The disk needs to be part of the pool or an error message is displayed.
protection
The default value for the protection field is disk.
Available options are:
disk - if the protection is set to disk, then mirrors are created on separate disks. This flag only works for file systems of type mirrored, mirrored-striped, and striped-mirror. The disks may or may not be in the same pool.
pool - if the protection is set to pool, then mirrors are created in separate pools. This flag only works for file systems of type mirrored, mirrored-striped, and striped-mirror. If not enough space is available, then the file system creation operation fails.
num_vols
Number of volumes to be created for growto and growby operations.