Forum Discussion

Dtrace_225's avatar
Dtrace_225
Level 3
8 years ago

Configuring VMware that protect Exchange 2010 DAG

  Hi All,  I have to implement same configuration as describe in this post: https://vox.veritas.com/t5/NetBackup/Configuring-GRT-based-Exchange-Backup-using-vmware-backup-policy/m-p/824660#M223697 ...
7.7
Windows Server (2003/2008)
  • Lowell_Palecek's avatar
    Lowell_Palecek
    8 years ago

    ** See update in 25 January 2018 post ** We have demonstrated that we can support this, although you will get a warning from the ASC job.

    Whether or not VMware has improved its ability to snapshot a GPT disk, the NetBackup ASC job for Exchange 8.0 still rejects the GPT disk. The log message you found still applies:

    Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\Direction' is not supported because volume <F:\> is on a GPT disk and is not supported.

Dtrace_225's avatar
Dtrace_225
Level 3

HI All,

I found that costumer MBX DB are on GPT disk, that is not supported by this king of configuration.

01/24/2017 09:07:16 - Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\Direction' is not supported because volume <F:\> is on a GPT disk and is not supported.
01/24/2017 09:07:16 - Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\Direction' is not supported because volume <F:\> is on a GPT disk and is not supported.
01/24/2017 09:07:16 - Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\Informaticiens' is not supported because volume <G:\> is on a GPT disk and is not supported.
01/24/2017 09:07:16 - Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\Informaticiens' is not supported because volume <G:\> is on a GPT disk and is not supported.
01/24/2017 09:07:16 - Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\NBU' is not supported because volume <G:\> is on a GPT disk and is not supported.
01/24/2017 09:07:16 - Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\NBU' is not supported because volume <G:\> is on a GPT disk and is not supported.
01/24/2017 09:07:16 - Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\Utilisateurs3' is not supported because volume <G:\> is on a GPT disk and is not supported.
01/24/2017 09:07:16 - Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\Utilisateurs3' is not supported because volume <G:\> is on a GPT disk and is not supported.
01/24/2017 09:07:16 - Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\Utilisateurs5' is not supported because volume <G:\> is on a GPT disk and is not supported.
01/24/2017 09:07:16 - Warning ascc (pid=9048) Exchange: snapshot preparation successful, with the following condition: GRT Functionality for Database 'Microsoft Information Store:\Utilisateurs5' is not supported because volume <G:\> is on a GPT disk and is not supported.

I can I deal with this?

 

  • Dtrace_225's avatar
    Dtrace_225
    Level 3
    8 years ago

    Master/Media OS 2012 R2 Netbackup version 7.7.3

    Client 7.7.3

    Vsphère 5.5

    • sdo's avatar
      sdo
      Moderator
      8 years ago

      NetBackup v7.7.3 uses VMware VDDK v6.0.

      .

      The VMware VDDK release notes for v5.5.1 notes that there was a bug/limitation in VDDK v5.0 around GPT disks:

      https://www.vmware.com/support/developer/vddk/vddk-551-releasenotes.html

      ...which says:

      "VixMntapi now works better with GPT partitions.
      The VDDK 5.0 Release Notes said that the VixMntapi library did not support GPT. After a root cause analysis, VMware determined that the problem was partition ordering, with the shadow copy partition appearing first although it was index numbered later. So VixMntapi was modified to put the shadow copy partition in its expected order. This change enables file-level restore on Windows Server 2012."

      .

      You say you are using VMware vSphere ESXi v5.5.  Do you really mean v5.5 GA, or has it been patched.  I'd be curious to know "exactly" which version of ESXi you are using.  But I'm not asking because I know of a solution.  I mean, I don't know of a solution either way.... but telling us exactly which version of ESXi you are running might help others forum users provide you with better advice.

      .

      Now then, I can't help but think that... if your ESXi really is v5.5 GA, and not v5.5.1 or later, then maybe the v6.0 VDDK in NetBackup v6.0 is not enough... and so maybe... if your ESXi was v5.5.1 or above, then you might be ok... but then this is proabably nonsense from me... and all because I don't know which exact version of ESXi you are running.  Do you see why we always need to be very specific with forum posts about exactly which versions we are running.

      .

      Anyway, enough of all that conjecture.   Personally, IMO, I think you need to open an official proper Veritas Support case, and reference this forum post... because there could be a little nugget in this forum post (and the forum posts linked from this post itself) which might help the Veritas Support technician pinpoint exactly what the problem is.

      • Dtrace_225's avatar
        Dtrace_225
        Level 3
        8 years ago

        Hi Sdo

         

        Thank for your help. My exact version is Vsphère server 5.5.0. I will open a case.

         

        Thank again