Seeing this in daemon since last night...any idea what is this? Looks like its complaining about sessions more than 10 in that device which is set min 10 and max 60 on write device and 1 to 10 for read only device..
Auth. session limit greater than 10 for mmd# 4 on device rd=SN:DDB_dev15/_AF_readonly.
We have noticed it during cloning when you get single session reads, but perhaps when multiple reads are going we get the same - I never paid attention to that. I do not think we are in the same bus because we started using DD with SP4 which supports multiple reads (tested) for DD dev type devices and during those tests no issue has been seen.
I'm surprised to read that multiple reads are working in SP4+. I'm running SP5 and it still won't allow more than 1 read.
If a clone is running on a DD device and then I launch a recover from the same DD, it will still say "busy" until the clone is killed off or finishes. Oh and it will also throw those "auth session limit greater than ..".
^ Interesting. I have the same setup as you. I wish it worked.
As for DD Boost DFA, it only works with specific modules like NMDA or NMO, from what I understand. In my case, all the oracle RMAN backups go directly to the DD instead of going through the storage node using DFA. Everything else (standard FS backups for example) needs to go through the storage node.
Networker 8.0 adds support for simple NW clients (filesystem) to dedup directly to DD:
From NW 8.0 release notes:
The EMC NetWorker 8.0 releases provide significant functional enhancements, including
support for the following:
Direct File Access (DFA) enhancements, including support for DD Boost and standard AFTD devices, and the ability to bypass the NetWorker storage node and send data directly to a Data Domain system.
From the data domain integration guide (7.6), see table 2 on page 17. It states that DFA backup is not supported for filesystem backups in earlier version than 8.0.
UPDATE: I just re-read the table and your post.. it indicates that recovers support DFA. Oops. I will try multiple recovers at the same time then, I only tried with clones running, and that fails. Maybe if there's no clones, multiple recovers would work..
For me, it happens every time more than one recover and/or clone session is trying to read from an AFTD device, which is a limitation of NW 7.x (only one recover/clone session on AFTP at a time).
pn1lDbv3G612259
105 Posts
1109
1
Posted August 2nd, 2012 22:00
Hi,
Please take a look of this link where similar issue is been reported
https://community.emc.com/thread/116265
Thanks
Shivakiran