DataDomain VTL / NetWorker - best architecture
Posted on 2011-09-23
Does anyone have any experience of using EMC DataDomain (DD) units (DD670s especially) as VTLs with EMC NetWorker for their backup solution?
I'm looking at using the same but have been presented with two potential architectures; the first I have been 'expecting' as it was discussed a while ago, but the second (and latest) has raised some questions and I can't find enough information I need to either back it up (no pun intended!) or dismiss it.
Environment: Two DCs, less than 30km apart with 30Mb link between the two. DD670s and RP units talk over the link (Production <=> DR). Predominantly HP-UX systems, some Windows. EMC VNX SAN.
The first architecture mentioned above involves a top-level NetWorker Server (NS) and two Networker Storage Nodes (NSNs); pretty standard stuff, NS controlling the jobs and dedicated NSNs shifting the data (from the backup clients) to the DDs. I haven't had detailed sight of the connecitivity but assumed the NSNs were multi-homed, with GbE to a Backup VLAN (for backup client connecitivity) and fibre to a multi-Gbps fabric which also connects the DDs (for throughput).
The second architecture has two main differences; the NSNs role is no longer on dedicated servers, the role moved to each backup 'client', i.e. the app and db servers themselves. Secondly, the DD670s are both GbE-connected, no fibre connectivity.
This has raised more questions that I could really post here, so my main ones are:
1) Has anyone implemented their solution the second way and did it have any negative effects, e.g. poor server performance, incompletion within backup windows, incompatibilities, etc.
2) Does the DD670 need fibre-connections if used as a VTL? GbE just seems as though it might be more than a little stretched with a large client base/lots of data. Also, the standard DD config seems to be only two GbE NICs, which would be taken up for other purposes than the dedicated Backup VLAN here.