1 2 Previous Next 18 Replies Latest reply: Oct 13, 2010 9:39 AM by Hormigo RSS

VMware Image Backup with vCenter 4.0 build 258672 --> KO !

jjay

Firstly, my english is bad (I'm french). 


VMware vCenter Server 4.0 Build 208111 (Windows 2003 SP2 x86)
The VMware Image Level Backup works almost well but I have problems with some VM.
I added the option (x22=8192) to bypass the problem on this files, the backup perform successfully (but i know, i can't restore a VM from scratch).

 

 

If I update the vCenter, the VMware Image Backup doesn't works.

 


VMware vCenter Server 4.0 Build 258672 (Windows 2003 SP2 x86)
The VMware Image Level Backup doesn't works ! I don't see events in the vCenter activity...
In Avamar, the status of client is "Waiting-Client" and after "Time Out - Response".

  • 1. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Brett_Herman

    jjay,

    I have the exact same issue.  I was running with the  x22=8192 workaround and created a ticket with EMC #35521782.  They advised me to update to ESX 4 Updated 2.  I ran update manager and updated all the below items in order:

     

    All ESX 4 Servers to update 2 , and latest patches up to June 30th 2010

    Updated vCenter Server, Client, Update Manager, & Converter to version 258672.

     

    Before the update, backups ran fine with the VM Powered off, or powered on with the x22=8192 switch for the backup.  After the update All I see is Waiting-Client for 5 minutes and then it time-out.  I made no changes to Avamar or the Proxy.

  • 2. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    jjay

    Thanks you Brett_Herman !

    I am happy do not be alone with this issue !

     

    If you have a ticket open at EMC Support, please inform me of the solution.

  • 3. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Hormigo

    Hi all,

     

    I have the same issue!

     

    I open the case SR 35295502.

     

    I'm two week for resolve this problem, and nothing.

     

    Avamar Server: 5.0.0.410

    Avamar Proxy Client 5.0.105

     

    With this client, not necessary use --x22=8192

     

     

    ***********************************************************************

     

    Follow the steps I do.

     

    Installing and Configuring Avamar VMware Image Backup

    • Create Dedicated vCenter User Account for Use With Avamar (page 458)
    • Configure MCS-to-vCenter Authentication (page 459)
    • Deploying an Avamar Image Backup Proxy VM Appliance (page 461)
    • Adding a vCenter Client (page 466)
    • Adding Virtual Machine Clients (page 469)

     

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


    Create Dedicated vCenter User Account for Use With Avamar

     

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

     

     

     

    Configure MCS-to-vCenter Authentication

     

    * Turning Off Certificate Authentication for All MCS-to-vCenter Communications

    Log in  Utility   ADMIN

    dpnctl stop mcs

     

    vi /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml

     

    localize: ignore_vc_cert

     

    change for TRUE:

    <entry key="ignore_vc_cert" value="true" />

     

    save and exit

     

    dpnctl start mcs

     

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

     

     

     

    ************Deploying an Avamar Image Backup Proxy VM Appliance*****

     

    Same name for vCenter, DNS and Avamar Client.


    Log in vCenter (windows)

    Download AvamarVmImageProxy-linux-VERSION.ova (384MB)


    1. In vCenter, click File > Deploy OVF Template.

    2. Select Deploy from file
    localize o arquivo que vc baixou do Avamar

    4. Power on the new proxy virtual machine.

    5. From the vSphere client, right-click the new proxy VM and open a console to it.

    6. When the Main Menu appears, configure the network.
    Coloque o ip que se comunique com o Avamar e o vCenter

    Under Edit DNS configuration

    (NOTE: On this operating system menu, primary DNS is mislabeled Primary DSN.)


    7. Configure the time zone.

    8. Configure proxy backup type.
    Set this option to the operating system running on the intended target
    backup virtual machines. Choices are Windows or Linux (non-Windows
    operating systems).

    I set WINDOWS

    (attention: For backup of Windows Machine, use one Proxy, For backup of NON-WINDOWS Machine use other Proxy. (Create two Proxy server, windows and linux))


    9. Register proxy with an Avamar Management Console.
    Set this option to the Avamar Administrator you want to register the proxy on.

    TYPE IP OF THE AVAMAR SERVER

    In the Avamar show "localhost localdomain" I rename for "avamar_proxy"

    In propertier I select all  Storage


    10. After all four options are set (the menu items indicate so), exit the
    configuration menu by selecting quit.

     

     

    In Avamar, Invited Client.

     

     

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

     

     

    Soon I inform you!

     

    Regards.

  • 4. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Amol

    You need the Vcentre on 4 Update 2

    Avamar Server on 5 SP2 (5.0.2-41)

    Avamar Vmware Proxy on 5.0.105.169

  • 5. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Brett_Herman

    Amol,

         So far that has been the most confident response I've received so far about Avamar with VMWare.  When I called support they could not give me a response that concrete.  Yesterday I spent 156 minutes straight on the line with Avamar Support and their response was to downgrade VSphere 4 to update 1 (which is time consuming) and that will not fix the overall problem.  Please forgive me if I sound naive, but I have some questions,

     

    1.  Have you seen this working? (Why wouldn't Support just tell me to do this)

    2.  Is there a new Proxy version in Avamar 5 Update 2?

    3.  What is the command to show the avamar Proxy version?  In the GUI when I backup the proxy Linux Guest OS, it says Client 5.0.105-169.

    4.  How long/complicated is the Avamar upgrade to Update 2.  We are currently running 5.0.1.32 on the grid.

     

     

    Any help is appreciated!

  • 6. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Amol

    Vcenter Update 2 is not compatible with Avamar SP1 (5.0.1-32) you need to have Avamar SP2 (5.0.2-41)

    As far as proxy is concern you have a proper version of Proxy (5.0.105-169)

     

    As far as your questions are concern

    1> Almost all the bugs are resolved with Avamar SP2 with Vcentre U2 & Proxy 5.0.105-169

    2> The latest proxy is 5.0.105-169

    3> avtar --version will show the version ( Whatever the version of Avtar is the same ver of Proxy)

    4> Avamar SP2 upgrade is not complicated, you can ask the support Engineer to do an emergency Upgrade. Usually upgrade are done on schedule basis but for some special scenarios like this can be done on high priority basis

     

    Regards

    Amol

  • 7. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Brett_Herman

    Thank you Amol, I will work with Avamar in upgrading the Grids and will report back to this forum with my results.  Thanks for the prompt help.

  • 8. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Amol

    In case if you face any problem after upgrade, you can ask the engineer to contact me and I'll work with you

     

    Regards

    Amol

  • 9. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Hormigo

    Hi Amol,

     

    I open Service Request 35604992 for Upgrade from 5.0.100-410 to 5.0.2-41.

     

    The Avamar Proxy is 5.0.105-169.

    The vCenter is 4.0 build 258672 (SP2)

     

    Soon I answer for you with good new (I hope...).

     

    Thanks.

  • 10. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Brett_Herman

    Is there any way to run more that 1 VM backup at a time with a VM Proxy? Or am I stuck running 1 backup at a time?

  • 11. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Hormigo

    Hi,

     

    Imlement more Avamar Proxy.

     

    Look the  PDF:

    EMC ®

    AVAMAR®  FOR VMWARE GUIDE 5.0

    P/N 300-010-712    REV A01

     

     

    You can deploy more than one backup proxy.

    The Avamar system automatically distributes workload to the deployed

    proxies. Multiple proxy capability is desirable for various reasons:

    • Backup workload can be distributed across multiple ESX hosts.

    • Proxies can be positioned at multiple points of SAN LUN connectivity to

    ensure that SAN transport is always used during backups and restores.

    • A high level of concurrent operations is possible in the backup window.

    • Redundancy leads to higher availability.

     

     

    Regards.

  • 12. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Brett_Herman

    Thanks again Amol, this fixed our issue.  SP2 on the Grid solved our problem.  To recap:

     

     

    VMWare vSphere 4 Update 2 (aka 258672)

    Avamar Server 5.0.2.41

    Avamar VM Proxy 5.0.105-169  (Included with SP2 on the Grid)

  • 13. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Hormigo

    Hi Amol,

     

    The problem is solved!!!

     

     

     

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

    VMWare vSphere 4 Update 2 (build 258672)

    Avamar Server 5.0.2.41

    Avamar VM Proxy 5.0.105-169

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

     

    Obs: The Avamar Proxy has be ping all Virtual Machines, by Name and IP.

     

     

     

    Thanks!!!!!!!!

     

     

    Regards,

    Hormigo

  • 14. Re: VMware Image Backup with vCenter 4.0 build 258672 --> KO !
    Dennis Dai

    Hi Hormigo,

     

    Could you share the docuemnt "Installing and Configuring Avamar VMware Image Backup" ?

     

    Thank you,

    Dennis 

1 2 Previous Next