Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

AIM upgrade is failing with the message "Not enough space for backup"

0

0

Article ID: KB12955 KB Last Updated: 23 Jan 2009Version: 1.0
Summary:
When upgrading the Advanced Insight Manager (AIM), the installation may fail with the following message Not enough space for backup
Symptoms:
When attempting to upgrade AIM, the installer prints the message Not enough space for backup and prompts the user to either cancel the installation or provide an alternate location for installing AIM. If another directory on the same partition is entered, the same message is displayed again.
=============================================================================== 
Choose Install Folder 
--------------------- 
Please enter the directory where you want to install the AIM Application. 
AIM Application Directory: 
Default Install Folder: /opt/aim 
ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT 
:
===============================================================================
Previous installation detected.
-------------------------------
Install has detected that there is already an AIM installation located in
/opt/aim. Should this installation be upgraded? OK to perform an upgrade, or
Cancel to choose a different folder for installation.
->1- Cancel
2- OK
ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE
DEFAULT: 2
===============================================================================
Not enough space for backup
---------------------------
Install has determined that there is not enough space for backing up the
current installation.
Click OK to provide a different location, or Cancel to exit
->1- OK
2- Cancel
ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE
DEFAULT: 2
Solution:
This happens because the AIM installation detects that there is not enough space to backup the existing version before proceeding with the installation of the new version.
To determine if this is the case, do the following:
  1. Check the amount of available disk space on the server:
    [root@aim]# df -h 
    Filesystem Size Used Avail Use% Mounted on 
    /dev/hda2 35G 26G 7.4G 78% / 
    /dev/hda1 99M 9.1M 85M 10% /boot 
    none 504M 0 504M 0% /dev/shm 
    [root@aim]# 
    

    The output above shows that there is 7.4G of empty space on hda2

  2. Check the amount of space consumed by the aim installation:
    [root@aim]# du -hs /opt/* 
    24G /opt/aim
    

    24G are used by AIM.

  3. Compare the two values.  In our example, there is clearly not enough disk space left to back up the existing AIM installation (24G > 7.4G)

There might be one of several possible issues at the root of this behavior, all related to disk space usage. The following is a description of two such issues.
  1. If you are upgrading an AIM version older that 1.3, you may be running into a problem where jboss logs keep building up and consuming more and more disk space. To verify this check the /opt/aim/jboss/server/default/ directory.
    [root@aim]# du -hs /opt/aim/jboss/server/default/*
    372K    /opt/aim/jboss/server/default/conf
    32K     /opt/aim/jboss/server/default/data
    32M     /opt/aim/jboss/server/default/deploy
    4.0K    /opt/aim/jboss/server/default/deploy-hasingleton
    12K     /opt/aim/jboss/server/default/farm
    22M     /opt/aim/jboss/server/default/lib
    23G     /opt/aim/jboss/server/default/log
    36M     /opt/aim/jboss/server/default/tmp
    5.3M    /opt/aim/jboss/server/default/work 
    

    This shows that the jboss logs are consuming 23G of disk space. To resolve the issue, you could free up disk space by deleting old logs. This problem is corrected in AIM 1.3

  2. This may be happening because a lot of disk space is being consumed by JMBs sent by the network devices to AIM. If this is the case, you may want to consider deleting old JMBs.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search