Forum Discussion

CadenL's avatar
CadenL
Level 6
7 years ago

Unable to expand mailboxes with GRT restores

e have a single Exchange 2016 server running as a virtual machine which we backup using a vmware policy with Exchange GRT and log truncation enabled. The backup completes fine as does the ASC but we're unable to expand the database to see the individual mesages when we request the restore (either from the master server or directly from the client)

The Exchange server has the NFS client, version 8.1 of the NBU client and the Veritas VSS installed and the Master server is an NBU Appliance running 3.1. All the Exchange impersonation permissions have been set and the credentials have been added to both the NBU client services on the Exchange server and in the client properties in the NBU Java console.

When we attempt to expand a users mailbox to see the messages we get and error saying 'System Database Error' and we can't see any messages. We get the same error when on the exchange client BAR or the master server BAR.

Below is an error we see in the nbflc log which we feel is relevent but we cannot find out anything more as to how to troubleshoot this error or what file it's looking for.

0,51216,158,351,2352,1519136187215,11312,16848,0:,94:<from Producer::iterateResource> VDiskMounter::UnMountAllDisks called (../BEDSContext.cpp:159),20:[mounter] ,4
0,51216,158,351,2353,1519136187215,11312,16848,0:,92:<from Producer::iterateResource> VDiskMounter::~VDiskMounter called (../BEDSContext.cpp:159),20:[mounter] ,4
0,51216,158,351,2354,1519136187215,11312,16848,0:,94:<from Producer::iterateResource> VDiskMounter::UnMountAllDisks called (../BEDSContext.cpp:159),20:[mounter] ,4
0,51216,158,351,2355,1519136187215,11312,16848,0:,100:FS_AttachToDLE() Failed! (0x2:The system cannot find the file specified.) (../ResourceChild.cpp:674),28:ResourceChildBEDS::_attach(),1
0,51216,158,351,2356,1519136187215,11312,16848,0:,56:--- EXITING 00000000002FE348 --- (../RAIProducer.cpp:78),23:RAIChildContext::attach,6
0,51216,309,351,846,1519136187215,11312,16848,0:,52:+++ ENTERING 00000000002FE988 +++ (../CFEObj.cpp:49),32:CFEObj::CFEObj(producer, marker),6
0,51216,309,351,847,1519136187215,11312,16848,0:,51:--- EXITING 00000000002FE988 --- (../CFEObj.cpp:49),32:CFEObj::CFEObj(producer, marker),6
0,51216,309,351,848,1519136187215,11312,16848,0:,60:+++ ENTERING 00000000002FEA98 +++ (../CFEObjProducer.cpp:67),34:CFEObjProducer::objProducerHandoff,6
0,51216,309,351,849,1519136187215,11312,16848,0:,68:1 non-object reasons added to the blocker

 

I think the NFS client is perhaps mounting the database ok but NBU then can't browse it as we also see the following warning in the event viewer on the exchange client.

Client for NFS requested a mount with file locking enabled, and the remote Network File System (NFS) server does not support file locking.

Client for NFS mounted the shared resource anyway. File locking may not be available.

To avoid this warning in the future, enable file-locking suppport on the remote NFS server.

 

One final point of note is that the Exchange databases are installed on GPT disks and so we do get a warning within the ASC job saying that GRT can't be used with GPT disks - BUT - we believe this is now supported and this error can be ignored following a Veritas update in the following post (please scroll to the bottom of the post)

https://vox.veritas.com/t5/NetBackup/Configuring-VMware-that-protect-Exchange-2010-DAG/m-p/824661

 

8
Linux
  • Lowell_Palecek's avatar
    Lowell_Palecek
    Level 6
    7 years ago

    To see if it's a problem mounting the backup with NFS protocol, check all occurrences of "nbfs" in the ncflbc log.

    The snippet of log is a narrow window. The fact that it's mostly UnMountAllDisks and the VDiskMounter::~VDiskMounter destructor suggests that you are looking quite a ways downstream from the actual error.

    I can't answer for the significance of the NFS file locking issue. I suggest you use vxlogview on your ncflbc log to make it easier to compare timestamps with your Event Viewer log. Here's what I do:

    >cd <Netbackup\bin>
    >vxlogview -d all -i 351 >..\logs\ncflbc\nblbc.txt

    Yes, we do believe we can support Exchange GRT from VMware backup with the database on a GPT disk.

    If you don't find a solution quickly, I suggest engaging Veritas support. Those folks can give you more holistic help than I can.

      • Systems_Team's avatar
        Systems_Team
        Level 6
        7 years ago

        Hi Caden_L,

        I can confirm that the NFS warnings you see in the Event Viewer on Windows for clients with GRT can be ignored.  We see this on both GRT backups of Active Directory and Exchange, and have done every since we started using GRT.

        You'll likely be getting two warnings - one in the Application event log and one in the System event log, and it only happens during GRT backup.

        Application Event Log Warning

        Windows(R) Lightweight Directory Access Protocol (LDAP) failed a request to connect to Active Directory Domain Services(R) for Windows user <DOMAIN\UserName>.

        Without the corresponding UNIX identity of the Windows user, the user cannot access Network File System (NFS) shared resources.

        Verify that the Windows user is in Active Directory Domain Services and has access permissions.

        System Event Log Warning

        Client for NFS requested a mount with file locking enabled, and the remote Network File System (NFS) server does not support file locking.

        Client for NFS mounted the shared resource anyway. File locking may not be available.

        To avoid this warning in the future, enable file-locking suppport on the remote NFS server.

         

        Hope this helps,

        Steve