My Favorites

Close

Please to see your favorites.


SUSE Manager disk space requirements

This document (7015050) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 1.7
SUSE Manager 2.1

Situation

This article will provide detailed information about sizing requirements for SUSE Manager so admins can plan their disk space accordingly.

Resolution

The following disk space information should help to calculate sufficient storage for SUSE Manager before first deployment. Please note, by default the SUSE Manager installation process creates one Volume Group with one single volume for the root device storing the entire structure such as the embedded database and patch directories. Adjustments to this layout are certainly possible once the base image deployment was finished, however its the admins responsibility to implement and monitor them.

Base system:

  • With embedded PostgreSQL Database: > 20GiB
  • With embedded Oracle Database: > 30GiB

Database:

  • Oracle:
    /opt/apps/oracle/oradata: > 50GiB
    /opt/apps/oracle/flash_recovery_area: ~50GiB

  • PostgreSQL:
    /var/lib/pgsql: > 20GiB
Channels:

The following requirements are per channel:
  • Pool repositories: ~4GiB
  • Updates repositories: ~20GiB
  • SLES Expanded Support repositories: ~100GiB
  • SUSE Manager Tools repositories: ~100Mib
  • Other repositories: ~4GiB

Conclusion:

In order to calculate the necessary disk space use:

<base system> + <database> + <number of channels to mirror> = total disk space


To have sufficient disk space left the recommendation is to have <total disk space> + <2 service packs>. A service pack is considered one new main Pool Channel plus appropriate Updates child channels. Depending on the number of child channels for add-on products such as SDK, HAE or OES there might be more space needed.

Scenario: A SUSE Manager should be responsible to manage an estate of SLES 11 SP2 based systems and be able to migrate them to SP3, the usual PostgreSQL database will be used. For SLES 11 SP2, the SLES 11 SP1 and SP2 repositories need to be synced:

Base system = 20 Gib
Database = 20 Gib
Channels:
SLES 11 SP1 Pool = 4 Gib
SLES 11 SP1 Updates = 20 Gib
SLES 11 SP2 Core = 4Gib
SLES 11 SP2 Updates = 20 Gib
SLES 11 SP3 Pool = 4 Gib
SLES 11 SP3 Updates = 20 Gib
+ appropriate SUSE Manager Tools channels = 112 Gib + <2 Service Packs (~25GB each) reserve> = ~175GiB disk space

Bug Number

877335

Additional Information

Exemplary SUSE Manager:

susemanager:~ # df -h
Filesystem                 Size  Used Avail Use% Mounted on
rootfs                     393G  197G  176G  53% /
udev                       3.8G   96K  3.8G   1% /dev                                            
tmpfs                      3.8G     0  3.8G   0% /dev/shm
/dev/mapper/kiwiVG-LVRoot  393G  197G  176G  53% /
/dev/sda1                  100M   26M   69M  27% /boot

susemanager:~ # du -sh /var/spacewalk/      
174G   /var/spacewalk/

susemanager:~ # mgr-ncc-sync -l | grep P                                     
- P - channel is installed (provided)
[P] rhel-x86_64-server-5
    [P] res5-suse-manager-tools-x86_64                 
    [P] res5-x86_64
[P] rhel-x86_64-server-6
    [P] res6-suse-manager-tools-x86_64
    [P] res6-x86_64
[P] sles10-sp4-pool-x86_64
    [P] sle10-sdk-sp4-pool-x86_64
    [P] sle10-sdk-sp4-updates-x86_64
    [P] sle10-sp4-suse-manager-tools-x86_64
    [P] sles10-sp4-ltss-updates-x86_64
    [P] sles10-sp4-updates-x86_64
[P] sles11-sp1-pool-x86_64
    [P] oes11-sp1-pool-x86_64
    [P] oes11-sp1-updates-x86_64
    [P] sle11-sdk-sp1-pool-x86_64
    [P] sle11-sdk-sp1-updates-x86_64
    [P] sle11-sdk-sp2-core-x86_64
    [P] sle11-sdk-sp2-updates-x86_64
    [P] sles11-sp1-ltss-updates-x86_64
    [P] sles11-sp1-suse-manager-tools-x86_64
    [P] sles11-sp1-updates-x86_64
    [P] sles11-sp2-core-x86_64
    [P] sles11-sp2-extension-store-x86_64
    [P] sles11-sp2-ltss-updates-x86_64
    [P] sles11-sp2-suse-manager-tools-x86_64
    [P] sles11-sp2-updates-x86_64
[P] sles11-sp1-vmware-pool-x86_64
    [P] sles11-sp1-suse-manager-tools-x86_64-vmware
    [P] sles11-sp1-vmware-updates-x86_64
[P] sles11-sp3-pool-x86_64
    [P] oes11-sp2-pool-x86_64
    [P] oes11-sp2-updates-x86_64
    [P] sle11-sdk-sp3-pool-x86_64
    [P] sle11-sdk-sp3-updates-x86_64
    [P] sles11-sp2-suse-manager-tools-x86_64-sp3
    [P] sles11-sp3-updates-x86_64
[P] sles11-sp3-vmware-pool-x86_64
    [P] sle11-sdk-sp3-pool-x86_64-vmware-sp3
    [P] sle11-sdk-sp3-updates-x86_64-vmware-sp3
    [P] sles11-sp2-suse-manager-tools-x86_64-vmware-sp3
    [P] sles11-sp3-vmware-updates-x86_64
[P] suse-manager-proxy-1.7-pool-x86_64
    [P] sles11-sp1-pool-x86_64-proxy-1.7
    [P] sles11-sp1-updates-x86_64-proxy-1.7
    [P] sles11-sp2-core-x86_64-proxy-1.7
    [P] sles11-sp2-updates-x86_64-proxy-1.7
    [P] suse-manager-proxy-1.7-updates-x86_64

susemanager:~ # du -hs /var/lib/pgsql/
14G     /var/lib/pgsql/

Note: If a SUSE Manager runs out of disk space for whatever reason, this can have a severe impact on the database and file structure. Thus disk space monitoring daemons should get set to even a lower threshold as usual to ensure early notification to address this situation. SUSE Technical Services will not provide support for systems suffering from disk space conditions as this may have an effect on the whole system and not just parts which will not be traceable. The only solution to recover is to restore an earlier backup or install SUSE Manager from scratch.

Internal Notes

https://bugzilla.novell.com/show_bug.cgi?id=877335

TAG internal:

If you need to know in advance how much disk space is required by a system hosting a given set of channels, check out https://bugzilla.novell.com/show_bug.cgi?id=877335#c14.

Change Log

2014-June-20 - Sascha Wehnert - added SUMA 2.1 to environment section & changed title
2014-May-13 - Sascha Wehnert - Initial version

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7015050
  • Creation Date:13-MAY-14
  • Modified Date:20-JUN-14
    • SUSESUSE Manager

Did this document solve your problem? Provide Feedback