Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- 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
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- 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
- Configuring an FTP server
- 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
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
File system mount-time memory usage
Mounting a file system on a computer system allocates system memory that is not freed until the file system is unmounted. The amount of memory allocated at mount time is directly proportional to the size of the file system being mounted. The amount of memory that is allocated at mount-time is therefore important information to help determine the system memory requirements for a Veritas Access environment. The mount-time memory requirement is different if you expect to mount a total of 1 PB of storage or 2 PBs of storage. The number of files currently in the file system does not affect the amount of memory allocated at mount-time. The amount of memory allocated at mount-time is also inversely proportional to the file system block size.
The information required to determine the amount of memory allocated at mount time is the total size of all the file systems that are mounted on the same computer system at the same time and the block size of each file system.
The amount of memory allocated at mount time can therefore be estimated by obtaining the total size of all the file systems that are mounted on a system according to the file system block size. So four totals in all, one for each file system block size of 1 KB, 2 KB, 4 KB, and 8 KB.
Table: File system mount-time memory usage
File system block size | Total size of mounted file systems | Memory allocation at mount time |
---|---|---|
1 KB | 'a' TBs | 'w'MBs allocated per TB |
2 KB | 'b' TBs | 'x'MBs allocated per TB |
4 KB | 'c' TBs | 'y'MBs allocated per TB |
8 KB | 'd' TBs | 'z'MBs allocated per TB |
The mount-time memory requirement is therefore:
((a*w) + (b*x) + (c*y) + (d*z))
A file system using a 1 KB block size (the smallest file system block size) allocates approximately eight times more memory at mount time than a file system of the same size using a 8 KB block size (the largest file system block size). For this reason, the Veritas Access file system defaults to a block size of 8 KB if a block size is not specified when creating a file system.
Some customers might like to create small file systems using a 1 KB file system block size and subsequently grow the file system size significantly, as the file system block size cannot be changed after the file system is created. This procedure can result in very large file systems using a 1 KB block size that can result in an unexpectedly large allocation of system memory at mount time.
A Clustered File System (CFS) primary mount requires slightly more memory allocated at mount-time than a CFS secondary. The performance team recommends that the memory utilization of a CFS primary be used as the guideline for calculating the file system mount-time memory requirement.
Table: Memory footprint of 16 file systems with 32 TB size each - CFS primary mount
32 TB each file system | ||||
---|---|---|---|---|
Block size/file system | CFS primary mount | |||
Memory used (MB) | ||||
1 KB | 2 KB | 4 KB | 8 KB | |
1 | 329 | 164 | 82 | 41 |
2 | 659 | 328 | 165 | 82 |
3 | 988 | 491 | 248 | 125 |
4 | 1326 | 657 | 337 | 166 |
5 | 1649 | 821 | 414 | 210 |
6 | 1977 | 985 | 498 | 249 |
7 | 2306 | 1150 | 581 | 291 |
8 | 2635 | 1329 | 665 | 333 |
9 | 2964 | 1483 | 747 | 375 |
10 | 3293 | 1646 | 829 | 418 |
11 | 3624 | 1810 | 913 | 459 |
12 | 3953 | 1975 | 995 | 534 |
13 | 4281 | 2140 | 1077 | 546 |
14 | 4614 | 2307 | 1161 | 589 |
15 | 4942 | 2471 | 1243 | 629 |
16 | 5272 | 2636 | 1325 | 671 |
Table: Memory footprint of 16 file systems with 32 TB size each - CFS secondary mount
32 TB each file system | ||||
---|---|---|---|---|
Block size/file system | CFS secondary mount | |||
Memory used (MB) | ||||
1 KB | 2 KB | 4 KB | 8 KB | |
1 | 187 | 93 | 47 | 21 |
2 | 372 | 186 | 94 | 48 |
3 | 558 | 279 | 139 | 71 |
4 | 742 | 371 | 186 | 94 |
5 | 929 | 465 | 233 | 117 |
6 | 1113 | 557 | 280 | 140 |
7 | 1300 | 650 | 326 | 164 |
8 | 1485 | 743 | 373 | 187 |
9 | 1670 | 837 | 419 | 213 |
10 | 1854 | 928 | 465 | 237 |
11 | 2040 | 1020 | 512 | 259 |
12 | 2224 | 1114 | 558 | 286 |
13 | 2410 | 1208 | 606 | 306 |
14 | 2596 | 1301 | 652 | 330 |
15 | 2780 | 1393 | 701 | 353 |
16 | 2966 | 1485 | 747 | 376 |
Figure: Mount-time memory consumption for 32 TB file systems provides the guideline for the system memory utilization at mount time.