Upgrading vSphere Data Protection fails at 0% with no errors
search cancel

Upgrading vSphere Data Protection fails at 0% with no errors

book

Article ID: 326932

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Cannot upgrade VMware vSphere Data Protection (VDP)
  • After successfully mounting the VDP upgrade ISO and choosing to start the upgrade, the progress bar stays at 0% and does not update for many hours.
  • You do not see any errors.


Environment

VMware vSphere Data Protection 5.1.x

Cause

This issue occurs if you do not have sufficient space on the / (root) partition of the VDP appliance. You need at least 2 GB of free space to upgrade VDP.
 
To verify the space available on the appliance, run this command from either an SSH session or the vCenter Server console:
 
# df -h
 
If the / directory shows less than 2 GB, the upgrade does not proceed and you do not get any notification of failure.
 
This issue usually occurs if the log files consume too much space on the appliance.

Resolution

To resolve this issue, relocate the /avamarclient directory to /space:
  1. Log in to the VDP appliance as the root user using SSH or the console for the appliance in vCenter Server.
  2. If the appliance is 100% full, delete some files from the /tmp directory to create a new file.
  3. Create a script file named space.sh in the /tmp directory using the vi editor:

    vi /tmp/space.sh
     
  4. Copy and paste this code to the space.sh file:
     
    #!/bin/bash
    #The purpose of this script is to relocate the /avamarclient directory to /space
    #Instructions: From a SSH or Console session within the VDP appliance, Paste the following into ashell script.
    #Version 1.2
    #
    mkdir /space/avamarclient
    echo "moving var directories and creating symlinks"
    mv /usr/local/avamarclient/var /space/avamarclient/var
    ln -s /space/avamarclient/var /usr/local/avamarclient/var
    mv /usr/local/avamarclient/var-proxy-1 /space/avamarclient/var-proxy-1
    ln -s /space/avamarclient/var-proxy-1 /usr/local/avamarclient/var-proxy-1
    mv /usr/local/avamarclient/var-proxy-2 /space/avamarclient/var-proxy-2
    ln -s /space/avamarclient/var-proxy-2 /usr/local/avamarclient/var-proxy-2
    mv /usr/local/avamarclient/var-proxy-3 /space/avamarclient/var-proxy-3
    ln -s /space/avamarclient/var-proxy-3 /usr/local/avamarclient/var-proxy-3
    mv /usr/local/avamarclient/var-proxy-4 /space/avamarclient/var-proxy-4
    ln -s /space/avamarclient/var-proxy-4 /usr/local/avamarclient/var-proxy-4
    mv /usr/local/avamarclient/var-proxy-5 /space/avamarclient/var-proxy-5
    ln -s /space/avamarclient/var-proxy-5 /usr/local/avamarclient/var-proxy-5
    mv /usr/local/avamarclient/var-proxy-6 /space/avamarclient/var-proxy-6
    ln -s /space/avamarclient/var-proxy-6 /usr/local/avamarclient/var-proxy-6
    mv /usr/local/avamarclient/var-proxy-7 /space/avamarclient/var-proxy-7
    ln -s /space/avamarclient/var-proxy-7 /usr/local/avamarclient/var-proxy-7
    mv /usr/local/avamarclient/var-proxy-8 /space/avamarclient/var-proxy-8
    ln -s /space/avamarclient/var-proxy-8 /usr/local/avamarclient/var-proxy-8
    echo "Script Complete - Please log out, and reboot the appliance using Virtual Center - Restart Guest option"
     
  5. Type::wq! to save the file and exit the editor.
  6. Make the script executable using this command:

    chmod +x /tmp/space.sh
     
  7. Run the space.shscript using this command:

    sh /tmp/space.s

     
  8. After the script completes, reboot the appliance.