Consider the following recommendations for your file server and other storage platforms:
-
To provide greater flexibility during upgrading, these storage platforms can be scaled up and out.
-
Industry-standard file storage systems such as storage area networks (SAN), direct-attached storage (DAS), and network-attached storage (NAS) can also be used.
-
CPU use is minimal, but it increases when Distributed Disk Services is used. Two to four cores is usually appropriate for machines running Distributed Disk Services.
-
When designing a file server or other storage platform, keep security, backup and recovery strategies, and retention policies in mind.
-
Use OnBase managed copies for high availability.
-
OnBase Disk Groups can be configured to work with other technologies outside of the application.
-
Other technologies, such as storage area network replication or software solutions that provide virtual copies, can be used for high availability.
-
RAID setup depends on the storage solution and architecture.
-
Consider using mount points for OnBase Disk Groups on Windows file servers to increase availability.
-
Because all OnBase Disk Groups on a logical unit number or partition will require addressing if that logical unit number fills and cannot be expanded, a single large logical unit number is not the best approach. Use multiple smaller logical unit numbers to allow the storage platform to be upgraded without interrupting Disk Group activity.
-
Allocate storage logical unit numbers in pairs for the file server to separate active OnBase Disk Groups from the system Disk Group of other busy OnBase Disk Groups.
-
Write caching helps document ingestion, since the data is backed up instantaneously on the cache.
-
When possible, place the file storage in close proximity to the batch ingestion processes.
-
For the database, any storage that can provide <5ms response for log files and <20ms response for data files will perform well.
-
For performance and growth management, use multiple partitions in the database so database file groups can be distributed.
-
In virtual machines, remember that a single VM data store can support multiple operating system partitions. This is especially important to prevent placing backups on the same disk as source data.
-
Understand the storage architecture and shared components to prevent contention on the storage layer.
-
Ensure operating system partitions are aligned (partition alignment) and Allocation Unit Size (partition cluster size) is set to 65,536 bytes for SQL Server partitions.
-
Additional resources and storage space are needed for 64-bit itemnum and Unicode databases.