Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backup exec 2010 R3: Does AD backup depend on Reparse Points and/or Sparse file creation?

Created: 10 Apr 2012 | 5 comments

Hi,

I'm currently trying to debug a backup to disk on a NAS device (using SMB connectivity and a backup-to-disk folder that we created on the device) that fails during the Active Directory backup on a domain controller (the system state Active Directory subitem).  The backup is on a Server 2008 R2 server, and the backup is set to use Advanced Open File Option, Microsoft Shadow Copy Services, allow Backup Exec to select the shadow copy provider.

During the active directory backup (everything prior to this succeeds), we get a Delayed Write Failed popup, followed by a Windows MUP event 139.  Once this occurs, SMB connectivity with the NAS fails until the server is rebooted, even though the NAS is still on the LAN, and can be used by other devices.

I have submitted a trouble ticket with the NAS vendor, and they asked me to run the B2DTest to the B2D folder on the NAS device.  I did, and the following two failures were noted:

04/06/12 17:56:12 Reparse Points - WARNING - Reparse points not supported on appliance: (0x32) The request is not supported.

04/06/12 17:56:12  The appliance does not support reparse points.  Some
04/06/12 17:56:12  of the advanced B2D technologies such as GRT may not
04/06/12 17:56:12  function.
04/06/12 17:56:12
04/06/12 17:56:12  For GRT to function correctly, either the B2D path
04/06/12 17:56:12  or the temporary path for GRT operations must be an
04/06/12 17:56:12  NTFS partition that supports reparse points.  If this
04/06/12 17:56:12  is not the case, GRT operations will fail.
04/06/12 17:56:12
04/06/12 17:56:12  For more information on this topic please refer to
04/06/12 17:56:12  the Backup Exec Administrators Guide.
04/06/12 17:56:12 Sparse Files - WARNING - Sparse files not supported on appliance: (0x32) The request is not supported.

04/06/12 17:56:12  * Sparse file support is required for Backup Exec
04/06/12 17:56:12  * versions prior to 12.6 for GRT to function.
04/06/12 17:56:12  * If the Backup Exec installation is 12.6 or greater
04/06/12 17:56:12  * this test can be ignored.
04/06/12 17:56:12
04/06/12 17:56:12  The appliance does not support sparse files. Some
04/06/12 17:56:12  of the advanced B2D technologies such as GRT may
04/06/12 17:56:12  not function.
04/06/12 17:56:12
04/06/12 17:56:12  For GRT to function correctly, either the B2D
04/06/12 17:56:12  path or the temporary path for GRT operations
04/06/12 17:56:12  must be an NTFS partition that supports sparse
04/06/12 17:56:12  files.  If this is not the case, GRT operations
04/06/12 17:56:12  fail.
04/06/12 17:56:12
04/06/12 17:56:12  For more information on this topic please refer
04/06/12 17:56:12  to the Backup Exec Administrators Guide.

The Reparse Points only seems to concern GRT, which is only used on Exchange servers? (as far as I know).

I have a trouble ticket opened with the NAS vendor, who asked me to ask Symantec about these two B2D test failures :)  We are a nonprofit organization, and because we obtained Backup Exec through TechSoup (discounted nonrprofit donations), we do not have full support with Symantec to open a trouble ticket with Symantec.

Thank you for your help!

Comments 5 CommentsJump to latest comment

pkh's picture

Do you have any problems with your AD backup if you back it up to a B2D folder created on an internal fixed disk?

FlyboyData's picture

Absolutely no problems running the same backup job to local storage.  We're running the job to near-line storage until we can solve the NAS problem.

Colin Weaver's picture

GRT is used by Active Directory Recovery Agent (ADRA), Exchange Agent, SQL Agent, Sharepoint Agent, Hyper-V Agent and VMware Agent. As per the B2Dtest result, as GRT obviously does use reparse points etc then I would expect potential problems with GRT enabled jobs for any of the above agents if your storage does not support them.

Bear in mind however that if you only need to backup Active Directory for Disaster Recovery (DR) then you don't need ADRA as a System State Backup of a Domain Controller will allow DR including active directory as either authoritative or non-authoritative. ADRA provides the ability to recover deleted users etc without restoring the whole of AD.

FlyboyData's picture

Yeah, we were just using the system state AD backup (and that is where we get the delayed write failed).  So GRT doesn't appear to be a factor here.  The NAS vendor says the device is certified for Symantec Backup Exec 2010, with the caveat that you can't use GRT backups.  I will forward all the info from here on to the NAS vendor.

Thanks for the info so far!

Colin Weaver's picture

OK just be aware that that fact the B2Dtest Tool has a warning for reparse poinst against GRT does not mean that we might not also need it for the System State of a DC (without GRT). However I am not aware of any documentation confirming or denying this.

Have you tested the system state backup using a B2D device that is local to the media server instead of the NAS?