Space requirements for scheduling client updates
Hub servers, spoke servers, and client systems must have enough free disk space to store and install update packages.
The hub server stores update packages for all the client platforms and versions that are installed in your environment. Update packages are automatically replicated to spoke servers. Each spoke server stores update packages for the client operating systems that are registered to that server. When an update schedule runs, the appropriate package is copied to the client system and the client is updated to the specified software version.
Table 1 shows the approximate size of update packages.| Client platform | Disk space |
|---|---|
| AIX® | 1.5 GB |
| Oracle Solaris | 1.2 GB |
| Linux® on Power Systems | 350 MB |
| Linux x86_64 | 950 MB |
| Linux on System z® | 350 MB |
| HP-UX Itanium 2 | 1.5 GB |
| Mac OS X | 200 MB |
| Windows 64-bit | 2 GB |
| Windows 32-bit | 1 GB |
Some additional files are also downloaded to the hub server to manage updates. These files require approximately 150 MB of free space for each operating system.
The total amount of disk space that is required on the hub server depends on the number of client platforms and the number of releases that are retained. Spoke servers typically store a subset of update packages, so less space is required. Clients require enough space to install a single update package.
For example, Windows packages require 2 GB of disk space and AIX packages require 1.5 GB. If you have two different versions of each client installed and you choose to store two releases for each version, the hub server requires approximately 14 GB of disk space. A spoke server that manages only Windows clients requires approximately 8 GB of disk space. Each Windows client requires approximately 2 GB of disk space.