12 Replies Latest reply: Mar 31, 2013 10:48 PM by adaikkap RSS

Unable to restore a VM or mount a SnapVaulted backup

yannbizeul
Currently Being Moderated

Using OnCommand console, I'm trying to mount a backup, and all I get is :

 

DX-FR-W8-VMW.france.xxx.com: OnCommandHSVMware: hsMount3 98b6e271e094a3d146cc9fff95657cc9: FLOW-11019: Failure in InternalMetadataFormatTask: No storage system configured with interface "10.20.30.206" (10.20.30.206)

 

In storage, this FAS2040 is well known by this IP address, but if it can help, its IP on 10.25 network must be used to be mounted on VMware, this is where the NFS network belong.

 

Backups are working fine

 

OC VMware.jpg

  • Re: Unable to restore a VM or mount a SnapVaulted backup
    kjag
    Currently Being Moderated

    Hi,

     

    As you are doing this operation from the backup node, Host Service might not aware of the credentials of the backup node. You need to push the credentials into Host Service using the below steps.

     

    1. Go to Host Service page

     

    2. Launch edit and push the credentials of the secondary controller(where you are trying to mount/restore the backup)

     

    -KJag

    • Re: Unable to restore a VM or mount a SnapVaulted backup
      yannbizeul
      Currently Being Moderated

      That's an interesting answer, but this system do not appear in host services, because it is not used as a primary storage, only for snapvault, and because of that (VMware has no knowledge of a system at this IP) it does not show up.

      I can add it manually in the service edit window, but when I confirm, it does not stick in the bottom list, only the primary systems currently mounted does.

      I don't think this is the problem because it used to work with the same situation.

       

      Envoyé de MobileMail

       

      Le 7 mars 2012 à 07:31, "kjag" <xdl-communities@communities.netapp.com> a écrit :

       

       

      Re: Unable to restore a VM or mount a SnapVaulted backup

      created by kjag in OnCommand Mgmt Software - View the full discussion

      Hi,

       

       

       

      As you are doing this operation from the backup node, Host Service might not aware of the credentials of the backup node. You need to push the credentials into Host Service using the below steps.

       

       

       

      1. Go to Host Service page

       

       

       

      2. Launch edit and push the credentials of the secondary controller(where you are trying to mount/restore the backup)

       

       

       

      -KJag

       

      Reply to this message by replying to this email -or- go to the message on NetApp Community

      Start a new discussion in OnCommand Mgmt Software by email or at NetApp Community

      Ce message et éventuellement les pièces jointes, sont exclusivement

      transmis à l'usage de leur destinataire, et leur contenu est strictement

      confidentiel.

       

      Si vous recevez ce message par erreur, merci de le détruire et d'en avertir

      immédiatement l'expéditeur.Vous n'êtes en effet pas autorisé, dans cette

      hypothèse,à copier, distribuer ou conserver ce message.

  • Re: Unable to restore a VM or mount a SnapVaulted backup
    pd@teamix.de
    Currently Being Moderated

    IHAC who had exactly the same symptoms. The message was

    No storage system configured with interface "192.168.x.x" (192.168.x.x)

    The fix was to do "options license_feature.multistore.enable on" on the controller which is mentioned in the error message (running 8.1). The eventlog of the server where the Host Package is running (in the application branch of the event viewer) was pretty helpful there. Every other log I checked was a complete dead end.

     

    I just wanted to mention this, because a google search for "No storage system configured with interface" yields exactly two hits, one of which is this thread.

     

    After that I did "dfm hs controller setlogin -p https <HSID> 192.168.x.x" on the OnCommand Server and restarted the Host Service. Not sure, if the last one was needed, but after that the controller instantly appeared under the managed systems and everything worked.

     

    cheers,

    Patrick

More Like This

  • Retrieving data ...