h1

Avamar 7.3 is now available

May 5, 2016

Avamar 7.3 is now available for download and some interesting new features are:

  • Customers can now finally deploy Avamar Virtual Edition 7.3 or upgrade from Avamar Virtual Edition 7.2 on their own without the assistance of EMC
    • EMC Remote Proactive Services will continue to be available to perform upgrades for customers
  • Both the OVA and OVF templates are included in Avamar Virtual Edition (AVE) for VMware and can configure network settings dynamically
  • The new Avamar Downloader Service no longer requires running on a separate Microsoft Windows server and can is now supported natively on the Avamar utility node
  • Avamar Data Migration Enabler – A new GUI has been added to the Avamar Data Migration Enabler (ADMe) software simplifying migrations of Avamar backups to the following:  tape, the cloud and removable storage such as USB drives
  • New client support in Avamar 7.3 including: RHEL 7.1 and Microsoft Exchange 2016
  • Support for Virtual Volumes (VVol) on VMAX3 and VNXe

 

  • New features for vRealize and vCloud Data Protection Extensions

*See the release notes for a complete list of new features and fixed problems

 

h1

EMC RecoverPoint GEN5 Logging into the BMC web console fails with “Login failed. Please try again.”

December 11, 2014

I have on several occasion tried to get the Intel Remote Management Module and Integrated BMC web console working on RecoverPoint Gen 5 appliances to allow for remote access to the RPA’s. Each time I was able to enable the BMC web console but when I try to log in I can never get in with default root user password. After doing some research I found KB Article Article Number:000176918. The cause is due to Bugzilla defect number 36883 and the solution is to apply the following script:

Workaround:

Run the signed script below on RPA:
Login as boxmgmt.
Select the following menu options to run the signed script below:
[2] Setup -> [8] Advanced options -> [5] System internal operations -> [1] Run script

Note: Copy the contents of the signed script including the “#”.

ZmM0MDE5MWEyYjRkNzI5OTFlOWQ4NzNlYmEzNDIxY2QKdW5saW1pdGVkCm5vdF9yZXN0cmljdGVk
ClRoZSBpZCBvZiB0aGUgc2NyaXB0IGlzOjM4Mjc4CmZpeCBwZXJtaXNzaW9uIGlzc3VlcyB0byB0
aGUgQk1DIHdlYiBpbnRlcmZhY2UKbWlrZUQKIyEgL2Jpbi9iYXNoIC1mCmlwbWl0b29sIGxhbiBz
ZXQgMSBjaXBoZXJfcHJpdnMgWGFhYVhYWFhYWFhYWFhYCmlwbWl0b29sIGxhbiBzZXQgMiBjaXBo
ZXJfcHJpdnMgWGFhYVhYWFhYWFhYWFhYCmlwbWl0b29sIGxhbiBzZXQgMyBjaXBoZXJfcHJpdnMg
WGFhYVhYWFhYWFhYWFhYCg==
#

h1

Avamar Hotfix 59538 for Avamar Server versions 7.0.0 or 7.0.1 – HFS check process to be unsuccessful and require a rollback

May 29, 2014

All Avamar systems running Avamar Server versions 7.0.0-x and 7.0.1-x could be affected by running backups and garbage collection concurrently causing subsequent HFS Check validations to be unsuccessful, requiring the system to be rolled back to the most recent validated checkpoint.  Do not run backups and garbage collection concurrently until this hotfix is applied; Avamar Hotfix 59538.

 

The following is an example of reference check errors that may appear:

From the /data01/hfscheck/err.log:

2013/11/29-21:04:58.92119 {0.0} [sam@0.0-5A3:181]  ERROR: <0372> hash referenced but not defined —————-92——e3c4b0ae7fd7-e-2013/11/29-21:04:58.92125 {0.0} [sam@0.0-5A3:181]  ERROR: <0372> hash referenced but not defined —————-95——1a3b3c400ecd-c–
2013/11/29-21:04:58.92227 {0.0} [sam@0.0-337:467]  ERROR: <0372> hash referenced but not defined —————-17——ff536bcd4462-0–
2013/11/29-21:04:58.92412 {0.0} [sam@0.0-566:307]  ERROR: <0372> hash referenced but not defined —————-f4——17efeeb97a93-7–

 

Contact EMC Support and reference Article Number:000186506 Version:1 or Hotfix 59538.

h1

Avamar Restore of a Corrupted Office XML file may need special flag to restore correctly

May 6, 2014

The following is an excerpt from the Avamar 7.0 release notes pertaining to Office XML files that may become corrupt during a restore. The workaround is too rerun the restore using the –deflateofficexml=false flag in the Restore Command.  For Avamar version 4.x-6.x, there is an ETA, 

https://emc–c.na5.visual.force.com/apex/KB_ETA?id=kA37000000000Qk

Here is the excerpt from the Avamar 7.0 from the “Windows backup client known problems” section:

26802 Corrupted Office XML files may need special flag to restore correctly

If you back up a corrupted Office XML file (.docx, .xlsx), then an error message

similar to the following may appear when you restore the file and open it:

Excel cannot open the file ‘Spreadsheet.xlsx’ because the file format

or file extension is not valid…

or

The Office Open XML file filename.docx cannot be opened because there

are problems with the contents, Word found unreadable content in

documentfile.docx. Do you want to recover the contents of this

document? If you trust the source, click Yes.

If you open the file anyway, the file may be empty or unusable. When this occurs, rerun

the restore using the –deflateofficexml=false flag in the Restore Command

Line Options dialog box. After restore, when you open the corrupted file you may get

the same Office error message, but if you click OK to open the file anyway, the file

should open correctly.

 

h1

VMware vSphere Web Client error, “An internal error has occurred – Error #1009” when attempting to edit a VM

April 16, 2014

I recently was trying to virtualize a Hyper-V server in a virtual machine located on a VMware ESXi 5.5 Host.  After deploying the VM, if I tried to edit the settings of the VM from the VMware vSphere Web Client I got the following error: 

An internal error has occurred – Error #1009

The fix was adding the following lines to the vmx file and re-importing the VM back into Inventory:

vhv.enable = TRUE

hypervisor.cpuid.v0 = FALSE

guestOS = “windows8srv-64”

h1

Avamar 7.0.1.61 Patch for “Host is in a state that cannot perform snapshot operations” after upgrade to vCenter 5.5

April 16, 2014

If you are experiencing the following VMware backup failures after upgrading vCenter to version 5.5,

“VM Image backups that fail due to the Host in a state that cannot perform snapshot operations.”

 I would recommend contacting EMC Support and requesting a hot fix for upgrading your proxy version to AvamarVMwareCombined-linux-sles11sp3-x86_64-7.0.101-62.rpm

ISSUES FIXED:

—————–

Bug 59992 – CLONE: bug 52705esc 7270:VM image backup fail due to the Host <esxserver> is in a state that cannot perform snapshot operations

Bug 60379 – CLONE: bug 58837esc 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 59963esc 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

h1

Data Domain OS version 5.3 encouraged to upgrade to 5.4

April 16, 2014

I recommend customers running Data Domain with operating system (OS)  5.3 to upgrade to OS 5.4 as soon as possible for support purposes.  The upgrade will assist in quicker time to resolution and more efficient troubleshooting from EMC Customer Service and EMC Data Domain Engineering.  As always, please review the DD OS release notes, especially the Known Issues and Workarounds section before proceeding.