h1

EMC Data Domain System Manager Interface error: “Service Not Available”

July 5, 2017

Recently had an issue with an EMC Data Domain System Manager Web Interface not coming up in my web browsers. I was receiving a “Service Not Available” message. The fix is a rather simple one, just disable HTTPS and then re-enable it as seen below:

sysadmin@DataDomain# adminaccess disable https
HTTPS Access: disabled
sysadmin@DataDomain# adminaccess enable https
HTTPS Access: enabled

h1

EMC Avamar 7.5 is now available

June 30, 2017

I noticed today that EMC Avamar 7.5 is now available for download.  There are several cool new features introduced in this version.  The one I am most excited about and had an opportunity to beta test recently is DD Cloud DR (Data Domain Cloud Disaster Recovery).  DD Cloud DR provides disaster recovery of onsite Avamar virtual machine backups to the the public cloud with the capability of powering the virtual machine backups on as Amazon Web Services EC2 instances (see the Data Domain Cloud Disaster Recovery Installation and Administration Guide and Release Notes for further information).

Another exciting new feature, AVE (Avamar Virtual Edition) is now available for AWS (Amazon Web Services) as well.  AVE w/Data Domain Virtual Edition are now supported for both AWS and Azure versions of AVE.

Avamar 7.5 will also provide support for the following:

  • Data Domain DD02 6.1
  • Data Domain Cloud Tier DR Support
  • EMC Unity OE 4.2 for NDMP backups
  • Isilon OneFS 8.1.0.0
  • Oracle ZFS 8.6.5
  • Microsoft Hyper-V GLR for Microsoft Applications
  • Ability to finally exclude the pagefile.sys from VMware backups
  • ACL restores from VMware File Level Recoveries, something I have been waiting quite awhile for
  • Visibility in vSphere on most recent successful image level backups
  • ESRS intelligence improvements
  • Security enhancements:
    • 775 certificates, LDAP-S Support, Default to SHA-2 certificates and Disable TLS 1.0/1.1

       

I recommend seeing the Avamar 7.5 Release Notes for a full list of new features and issues addressed.  You must use DD OS 5.7 or later on a Data Domain system with an Avamar 7.5 server. Before you upgrade to Avamar 7.5, you must upgrade clients that back up to a Data Domain system to Avamar 7.3 or later.  As always, review the upgrade requirements for Avamar 7.5 before planning upgrades.

Good Luck!

 

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”