Unsolved
This post is more than 5 years old
1 Rookie
•
31 Posts
0
4680
March 6th, 2017 02:00
Exchange DAG backup on Networker 9.1
Hello, I am testing Exchange 2010 DAG backup on Networker 9.1 (NMM 9.1) on a test setup and getting the same issue as discussed in this post Re: Backup de DAG Exchange 2016
I am backing up to an ATFD.
Error message:
=================================
NSR critical Backup of Saveset 'APPLICATIONS:\Microsoft Exchange 2010\Maildb01\DatabaseFiles' failed with error exch2010-dag:APPLICATIONS:\Microsoft Exchange 2010\Maildb01\DatabaseFiles: Unable to perform backup for save-set ID '3401398588' with DIRECT_ACCESS=Yes, check device and pool configuration to enable Client direct..
=================================
I have assigned all polices to Disk pool but don't know why but it keep choosing to backup to a Default tape pool.
I understand that with Networker 9.1 with Block Based backup it requires to backup to disk, but it keep choosing the tape library and then failed.
The solution for that post did not work for me.
1. I have remote username/password set on the AFTD
2. I have tried setting the UNC path of the AFTD with both shortname and FQDN of the Storage Node (which is the Networker server itself).
I am able to perform a successful save with this command on the client
---> save -b POOL_NAME -a DIRECT_ACCESS=yes C:\"
Any suggestion is greatly appreciated. I have been trying to solve it for a week...
0 events found


ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
March 6th, 2017 06:00
I don't use this setup, but top of my head wasn't there discussion about similar where there was requirement to use only (to have) single device for the pool when using BBB? Perhaps I mixed up something...
martingoh
1 Rookie
•
31 Posts
0
March 6th, 2017 18:00
Hi,
What do you mean? I only have a single device for the disk pool - ATFD
CarlosRojas
1.7K Posts
0
March 6th, 2017 19:00
Hi Martin,
The issue you refer to was solved by changing the UNC path for the device access path to use FQDN instead of short name, as I see you currently have.
Have you tried changing it?
Also, have you tried using the client wizard to create/modify the client?
Thank you,
Carlos
martingoh
1 Rookie
•
31 Posts
0
March 8th, 2017 02:00
Hi Carlos,
Yes I used the client wizard to create the client. Let me know if you need to look at any info, I can screenshot it.
Thanks!
l.walid
26 Posts
0
March 22nd, 2017 08:00
Hi,
I had the same issue for a long time, and what we finaly did was the following :
- Make one node of the Exchange DAG a storage Node and create a local AFTD to that storage Node and label it as 'Disk' for your case
- Then when configuring the Exchange DAG, the last screen where you specify the Preferred Order List, choose only the Node with storage Node installed.
This will resolve the client direct issue, please let me know if you need further assistance
Good luck
martingoh
1 Rookie
•
31 Posts
0
March 23rd, 2017 23:00
Hi Largou,
Thanks for the suggestion, I will definitely try it.
Will update whether it works.