Verify that your environment meets the system requirements for MEDITECH.
Operating System
Note: Both Commvault and MEDITECH must validate your deployment configuration to ensure that it can be protected by the Commvault software. Contact us at meditech@commvault.com, and we can assist you in the deployment process
Operating system | Processor architecture |
|---|---|
Microsoft Windows 11 Pro | x64 |
Microsoft Windows Server 2022 Standard Editions | x64 |
Microsoft Windows Server 2022 Datacenter Editions | x64 |
Microsoft Windows Server 2019 Editions | All Windows-compatible processors are supported |
Microsoft Windows Server 2019 Core Editions | All Windows-compatible processors are supported |
Microsoft Windows Server 2016 Editions For more information, see Considerations for Microsoft Windows Server 2016. | All Windows-compatible processors are supported |
Microsoft Windows Client 10 Editions Tape libraries/drives are not supported. | All Windows-compatible processors are supported |
Microsoft Windows Server 2012 R2 Editions For more information, see Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8.x. | All Windows-compatible processors are supported |
Microsoft Windows Server 2012 Editions For more information, see Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8.x. | All Windows-compatible processors are supported |
Hardware
Component | Space required |
|---|---|
Software | 20 GB on the operating system drive This space is used for temporary files copied during the installation or upgrade of the MediaAgent software. |
MediaAgent software and log file growth | 10 GB |
For optimal performance—which is particularly important in the following cases—use a solid-state drive (SSD) technology for the local index cache disk:
NAS filers running NDMP backups
Backing up large file servers
Any situation where performance is critical
For hardware requirements for the index cache, see Indexing: Planning.
Recommended hardware requirements for MediaAgents is explained in the following pages, based on the deduplication mode required for your environment:
Arrays, MEDITECH Platforms, and Processor Architectures
MEDITECH platforms | Array | Processor architecture |
|---|---|---|
Windows x64 |
|
|
Snapshot Mounting
If you want to mount snapshots over a Fibre Channel, then the proxy MediaAgent that you use for IntelliSnap operations must be a physical computer.
If you want to mount snapshots using an iSCSI initiator, then the proxy MediaAgent that you use for IntelliSnap operations can be a virtual machine.
Software That Is Automatically InstalledFile System Agent
If not already installed, the Windows File System Agent or Linux File System Agent is installed. For more information, see the following:
Note: On Windows computers, to successfully restore NAS data and Domino emails on the web, install a 32-bit file system proxy instance on a 64-bit computer.
Microsoft Visual C++ Redistributable 2017
Starting with Service Pack 18, Microsoft Visual C++ Redistributable 2017 (vcredist2017.exe) is automatically installed.
If a computer does not have the most recent Windows updates, the installation of Microsoft Visual C++ Redistributable 2017 will fail in installing Universal C Runtime. The following Windows updates must be installed to prevent the installation failure. The updates are not required on the most recent Windows operating system versions, such as Microsoft Windows 10 and Microsoft Windows Server 2016, because these versions have the Universal C Runtime already installed.
KB2919355
KB2939087
KB2975061
KB2999226
.NET Framework
.NET Framework 4.5 is automatically installed. Note that .NET Framework 4.5 can co-exist with other versions of this software.
Cloud Server
The MediaAgent can be installed on a virtual server in a cloud, such as Virtual Server in Amazon EC2. After the installation, verify that the remote clients can access this MediaAgent.
Tape Hardware
For information about tape hardware/driver support, see Tape Storage Matrix.
DISCLAIMER
Certain third-party software and service releases (together, "Releases") may not be supported by Commvault. You are solely responsible for ensuring Commvault’s products and services are compatible with any such Releases.