Sie sind auf Seite 1von 3

-----------------------

HOTFIX INFO

NAME: Hotfix 7_0_161-14_HF_192493

REVIEW BOARD URL: Not Applicable

TARGET VERSION: AV_BASE-7_0_161-9

TARGET OS VERSION: SLES11 x64, SLES11 SP3 x64

TARGET OS PATCH LEVEL: SP1

RELEASE TO: General Availability

PATCH DESCRIPTION:
-----------------
This Hotfix resolves Avamar Bug 192493 which a port from the standard Avamar
product to
the Nemo product to address several issues that were found in Hermosa SP1.

ISSUES FIXED:
-----------------

Proxy Changes

Bug 59992 - CLONE: bug 52705-esc 7270:VM image backup fail due to the Host
<esxserver> is in a state that cannot perform snapshot operations
Bug 60379 - CLONE: bug 58837-esc 7122:vm image backups show completed successfully
but log shows they failed
Bug 60499 - esc 7345:HOTFIX:Hermosa SP1 proxy are NOT clearing stale migration
reservation
Bug 60758 - CLONE: bug 59963-esc 7265:Prior snapshots are preventing backup
Bug 60759 - CLONE: Esc 6951: Certain cancellations can cause a cascade of asserts
that appears to have no end [FIX - This hotfix allows avtar to terminate quickly
when canceled in this situation]
Bug 60998 - CLONE: bug 58218-backup VM does not fail back to unquiesce when quiesce
snapshot failed
Bug 188772 - Large Number of ESX Hosts in vCenter Server Cause Proxy to Run Out of
Memory

NWComm Changes

Bug 188523 - esc7310, esc7583 - cdsf export failure after Fatal Error in avnwcomm.
Additional issues with nwcomm failing

MCS Changes

Bug 192758 - CLONE: bug 58797-esc7114:Vmimage Restore sits in waited queued state
for 7 SP1
Bug 192761 - CLONE: bug 59193-VM client may be marked as "deleted" incorrectly.
Bug 192771 - CLONE: bug 57709-esx6917:Cannot restore VM after upgrade to 7.0 --
restore is reject because ESX is not in vCenter
Bug 192765 - esc6827:BRSIL: Avamar 7 Vmware backups hanging after migrating to
vCenter 5.5 with ESXi 5.1 hosts
Bug 192437 - CLONE: bug 188453-esc 7594:MCS crashed due to lack of jdbc connections
Bug 192762 - CLONE: bug 57871-MCS should not validate GSAN stripe utilization (meta
capacity) if no DD attached
PATCH PREREQUISITE:
------------------------
Nemo Appliance version 1.0.1.9 or 1.0.1.17

IMPORTANT NOTES AND WARNINGS:


-----------------------------
It is not possible to backout this change once applied. The only way to backout
this hotfix would be to redeploy a fresh Nemo Appliance.

PATCH DELIVERABLES:
------------
The deliverable for this hotfix are a set of releng RPM builds.

Some RPMs must be installed on the Avamar Server. Different packages must be
installed on any External Proxies that exist

For VBA appliance running SLES11

AvamarVMwareCombined-linux-sles11-x86_64-7.0.161-14.rpm MD5/SHA1:
fb5df863d1f164f80c270e937cacf870
AvamarNWComm-linux-sles11-x86_64-7.0.161-14.rpm MD5/SHA1:
f351e128e82ddc0d4e05bedd71f88bb6
dpnmcs-7.0.61-14.sles11_64.x86_64.rpm MD5/SHA1:
7b05b33699f039b2b2c04f90c563bbf3

For External Proxies running SLES11-SP3

AvamarVMwareCombined-linux-sles11sp3-x86_64-7.0.161-14.rpm MD5/SHA1:
c48be5a542ed68381e11740f56eac769
AvamarNWComm-linux-sles11sp3-x86_64-7.0.161-14.rpm MD5/SHA1:
fab79577e49b0384d1b33c40f529a284

SAVE AND BACKOUT INSTRUCTIONS:


-----------------------------
It is not possible to backout this change once applied. The only way to backout
this hotfix would be to redeploy a fresh Nemo Appliance.

INSTALLATION:
-------------
INSTALL AS ROOT/ADMINISTRATOR (Y/N): Y
Instructions for deploying this configuration are as follows:

On a VBA Appliance

1) To install this patch, copy the following RPMs to the /tmp directory on the VBA
Appliance

AvamarVMwareCombined-linux-sles11-x86_64-7.0.161-14.rpm
AvamarNWComm-linux-sles11-x86_64-7.0.161-14.rpm
dpnmcs-7.0.61-14.sles11_64.x86_64.rpm

2) Log into the VBA Appliance as root and cd /tmp


3) Shutdown all system services by running the following command

dpnctl stop
4) Copy the emwebapp.sh startup file to a temporary location

cp /usr/local/avamar/bin/emwebapp.sh /usr/local/avamar/bin/emwebapp.sh.orig

5) Upgrade RPMs by running the following commands:

rpm -Uvh --force AvamarVMwareCombined-linux-sles11-x86_64-7.0.161-14.rpm


rpm -Uvh --force AvamarNWComm-linux-sles11-x86_64-7.0.161-14.rpm
rpm -Uvh --force --nodeps dpnmcs-7.0.61-14.sles11_64.x86_64.rpm

6) Copy the original emwebapp.sh back to its proper location

cp /usr/local/avamar/bin/emwebapp.sh.orig /usr/local/avamar/bin/emwebapp.sh

7) Delete the RPMs after installation from the /tmp directory and reboot the
appliance.

8) After the appliance has restarted, log-in and Re-register the internal proxies
using the following command

/usr/local/avamarclient/etc/initproxy.sh start

9) Your Avamar configuration is now ready for use.

On an External Proxy

1) To install this patch, copy the following RPMs to the /tmp directory on the
External Proxy

AvamarVMwareCombined-linux-sles11sp3-x86_64-7.0.161-14.rpm
AvamarNWComm-linux-sles11sp3-x86_64-7.0.161-14.rpm

2) Log into the External Proxy as root and cd /tmp


3) Upgrade RPMs by running the following commands:

rpm -Uvh --force AvamarVMwareCombined-linux-sles11sp3-x86_64-7.0.161-14.rpm


rpm -Uvh --force AvamarNWComm-linux-sles11sp3-x86_64-7.0.161-14.rpm

4) Delete the RPMs after installation from the /tmp directory and reboot the
appliance.
5) Your Avamar configuration is now ready for use.