Backup to share with GRT fails

[BrianSym]

Hello,

Exchange 2007
Backup exec 12.5 latest version hotfixes etc.

When backing up exchange with GRT to tape or to a local backup to disk folder, all works fine.

If we try and backup to a backup to disk folder that is a share on a remote system, we get the following.

BEREMOTE: [08/11/09 10:37:00] [1756]     CreateBSD: It is a pdi data transfer operation, creating pdi DLE
BEREMOTE: [08/11/09 10:37:00] [1756]     CreateBSD: Failed to create pdi dle \\servername.domain.com\Microsoft Information Store\Second Storage Group reason 0xE00084AF
BEREMOTE: [08/11/09 10:37:00] [1756]     startBackup: CreateBSD() failed!
BEREMOTE: [08/11/09 10:37:00] [1756]     Backup Job Stop(10)  - Tue Aug 11 10:37:00 2009


The above is from the SGMon log.

This error appears in the backup exec job log.

Completed status: Failed
Final error: 0xe000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.

If I switch off GRT when backing up to this folder, it works fine.

How can we resolve this issue?

[CraigV]

I'd go with installing the Remote Agent for Windows Servers manually on the server you're trying to back up too. Without RAWS, your backup server wouldn't know how to communicate with it.
Locally it would work as all your agents are correctly installed.

[BrianSym]

Hi Craig,

The problem is that if I disable GRT, the backup works fine to the remote server. Surely if there was a problem communicating with the share, it wouldn't be able to backup to it at all?

It's not a windows machine so I cannot install the agent on there.

Thanks,

Ryan

[CraigV]

...and I take it that your mapped drive is configured as a B2D? I haven't seen that before, but will try recreate it and see if I get the same issue.

Oh...what OS is the remote machine?

[BrianSym]

Yes, that is correct.

The remote machine is a Data Domain box. This fully supports SAMBA. It should be reproducible using a linux machine.

It all works fine until I enable GRT.

[Ben_L_]

Can you run the B2D test tool from the media server to the share and post the results?

http://seer.entsupport.symantec.com/docs/321584.htm

[Hemant_Jain · Accepted solution]

What version of OS are you using on data domain? Consider upgrading it to 4.6.1.3.
Thanks
 

[BrianSym]

I have this from the logs. Is there a workaround? How do we get hold of 12.6?

08/11/09 16:46:11 Memory Mapped Files - PASSED
08/11/09 16:46:11 Reparse Points - WARNING - Reparse points not supported on appliance: (0x32) The request is not supported.

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

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

[BrianSym]

Hello we are running 4.6.1.0-88314

Does the new version support the reparse points mentioned in the log?

[Hemant_Jain]

Yes Brian

Please upgrade OS, as this current OS that you have has shown problems with GRT for other customers. Recommend you to upgrade to 4.6.1.3.

Thanks

[Brentwood]

I have the same issue as Brian is having.  but I cannot upgrade to 4.6.1.3 as this is not available for a DD510.  I am currently running 4.6.1.0.

what other suggestions do you have?

[Hemant_Jain]

As per data domain there are couple of issues with 4.6.1.0 and backup Exec GRT, which they fixed in 4.6.1.3. I would advise you to get in touch with data domain support for further clarification on this. I am sure, they would have some documentation on limitations they have faced with supporting Backup Exec GRT. I am not sure if downgrading would be helpful. I would advise you to get in touch with data domain support on this.

Thanks

[BrianSym]

I am currently trying to get hold of this version of the firmware (4.6.1.3) for a DD120 box.

[Brentwood]

For anyone else with this issue.

Contacted Data Domain by opening a support case.  With in two hours I received an email that they were going to add 4.6.1.3 to the list of downloads I can access.

I am going to apply the upgrade today and report back tomorrow if tonight backup worked.

[BrianSym]

Yes confirmed Brentwood :)

I am currently awaiting for  the download to be added to my account.

[BrianSym]

Confirmed as working with the new DDomain OS version.

[Brentwood]

I also confirm that the GRT backups work now with the new Data Domain OS