Forum Discussion

X2's avatar
X2
Moderator
8 years ago

VM Restore - Encountered SSO login failure

Any VMware-NetBackup expert eyes around here?

To do some testing, I restored a RHEL6 32-bit VM from our production VMware environment (ESXi 5.5 U3) to our test VMware environment (ESXi 6.5). Netbackup version being used is 7.7.3 with RHEL 6.8 masters.

One of the tests in the test-ESX environment was to restore the complete VM. The restore job completed successfully with status 0. However, there was some permission issue in the detailed job status (see below). Would it be due to the VM coming from a completely different environment (separate vCenter) -hence the SSO login issue? Any comments would be appreciated.

------

Detailed job status:

07/13/2017 15:45:35 - Info bpdm (pid=4124) completed reading backup image
07/13/2017 15:45:37 - Info bpVMutil (pid=484) Deleting the existing VM with Display Name: RHEL5-v7, Folder Path: /ESX-Test6.5/vm/Test VMs/Linux/, Resource Pool Path: /ESX-Test6.5/host/DC1-Test6.5/Resources, Instance UUID: 50063c5e-1340-2032-2812-9f1be10132fa.
07/13/2017 15:45:49 - Info bpVMutil (pid=484) INF - vmwareLogger: GetTagTypeFromXml: SYM_VMC_ERROR:  INVALID_VM_XML_FILE
07/13/2017 15:45:50 - Info bpVMutil (pid=484) INF - vmwareLogger: SOAP 1.1 fault: "":ServerFaultCode [no subcode]
07/13/2017 15:45:50 - Info bpVMutil (pid=484) "Permission to perform this operation was denied."
07/13/2017 15:45:50 - Info bpVMutil (pid=484) Detail: <NoPermissionFault xmlns="urn:vim25" xsi:type="NoPermission"><object type="OptionManager">VpxSettings</object><privilegeId>System.Read</privilegeId></NoPermissionFault>
07/13/2017 15:45:50 - Info bpVMutil (pid=484) 
07/13/2017 15:45:50 - Info bpVMutil (pid=484) EC Error: 4260 : Encountered SSO login failure, msg=Encountered backup time failure: Tags for this VM are not avaliable
07/13/2017 15:45:50 - Info bpVMutil (pid=484) Successfully created virtual machine RHEL5-v7

Thanks.

Update: Just finished a restore of RHEL6 VM created using our regular deployment (puppet, etc) and it showed same EC Error: 4260 line along with others.

7.7
Linux
  • X2's avatar
    X2
    8 years ago

    Update: The issue was that even though the permissions for the backup user were correct, they were defined at "Datacenter" level and not at vCenter level.

    Once that was corrected, backup and restore worked as expected.

    PS: The issue had reared its head during the snapshot job too, here is the relevant status log for future:

    07/18/2017 16:53:16 - Info bpbrm (pid=476) INF - vmwareLogger: RegisterExtensionAPI: SYM_VMC_ERROR:  SOAP_ERROR
07/18/2017 16:53:16 - Info bpbrm (pid=476) INF - vmwareLogger: SOAP 1.1 fault: "":ServerFaultCode [no subcode]
07/18/2017 16:53:16 - Info bpbrm (pid=476) INF - vmwareLogger: GetTagTypeFromXml: SYM_VMC_ERROR:  INVALID_VM_XML_FILE
07/18/2017 16:53:32 - Critical bpbrm (pid=476) from client rhel6-v7.it.mcgill.ca: VMware_thaw: Unable to unlock virtual machine: /vmmor/vm-1575.
07/18/2017 16:53:46 - Critical bpbrm (pid=476) from client rhel6-v7.it.mcgill.ca: vfm_thaw: method: VMware_v2, type: FIM, function: VMware_v2_thaw
07/18/2017 16:53:46 - Critical bpbrm (pid=476) from client rhel6-v7.it.mcgill.ca: snapshot delete returned status 1
07/18/2017 16:53:46 - Info bpfis (pid=7276) done. status: 1
07/18/2017 16:53:46 - end Application Snapshot: Delete Snapshot; elapsed time 0:00:33
07/18/2017 16:53:46 - Info bpfis (pid=7276) done. status: 1: the requested operation was partially successful

    Thanks for the suggestions/ideas. The extra reading has left me more knowledgeable in this part.

    Marking this as solution - but the credit goes to Veritas support.

  • Thiago_Ribeiro's avatar
    Thiago_Ribeiro
    Moderator
    8 years ago

    Hi 

    I found this TN, can you check?  Maybe it can explain these Info messages of restore.

    https://www.veritas.com/support/en_US/article.v110166564_nbu_vmware_web

    Description

    Tag associations are backed up and restored as part of the VMware backup process. Backup and restore of tag associations is a best effort. Any tag collection errors are shown in the Activity Monitor for the virtual machine snapshot job.

    Because of the best effort on backup and restore of tag associations, you may receive unexpected behavior. Please be aware of the following:

    • You can receive a NetBackup Status Code 0 even if the tag associations are not captured during the backup. Because tag backup is best effort, this error is not considered a failure that halts a backup. Any tag collection errors that occur in the backup are shown in the Activity Monitor for the virtual machine snapshot job.

    • You can receive a NetBackup Status Code 0 on a restore even if tag associations are not restored. Any tag collection errors that occur in the backup are shown in the Activity Monitor for the virtual machine snapshot job.

    • Restores receive a NetBackup Status Code 1 when:

      • The tag doesn't exist on the target vCenter Server. Be aware that NetBackup restores tag associations to virtual machines by the tag identifier not tag name.

      • The virtual machine was restored to a pre-6.0 vCenter Server.

      • Other VMware failures.

       

      Hope this help you.

       

      Regards,

       

      Thiago

    • X2's avatar
      X2
      Moderator
      8 years ago

      Thanks Thiago_Ribeiro, I will look into it and also consult with our VM admins. The ESXi 6.5 environment is a test environment and it could be due to that too.

      The message

      msg=Encountered backup time failure: Tags for this VM are not avaliable

      Just a thought - could it be due to the Web Plugin for NetBackup not being there? VIP does leave an updated time stamp after a successful backup.

      • Thiago_Ribeiro's avatar
        Thiago_Ribeiro
        Moderator
        8 years ago

        Hi X2,

        I'm not sure...In my environment we have ESXi 6.0 and web Plugin for Netbackup installed..but I never try to restore a VM from Vcenter A to Vcenter B (example)...

        I was searching about the error code EC Error: 4260, and I foung this, are you using the same credentials/permission on both sides to make restore? This error error make mention to a possible error to log on Single Sign-on service. I believe that you already check this, but I needed to ask you. Take a look the message from TN.

        https://www.veritas.com/support/en_US/article.000118447

         

        Regards,

         

        Thiago