Networker

Re: [Networker] Data Domain in mixed BOOST/VTL mode?

2013-04-08 11:22:17
Subject: Re: [Networker] Data Domain in mixed BOOST/VTL mode?
From: Chester Martin <cmartin AT SPP DOT ORG>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 8 Apr 2013 10:16:13 -0500
We came from a edl environment, at first I wanted to use vtl with data domain 
just because I was used to the edl mimic'ing a tape library.  I am glad that I 
didn't and am using boost.  VTL just adds another layer of complexity to the 
environment.

However if you do decide to use vtl and you currently clone your data, you'll 
have to use data domain replication to move the data to the dd you want to 
clone it to.   If you use internal dd replication and not networker "clone 
controlled replication" networker won't know anything about the data you 
cloned.  The catch is that if you use vtl "clone controlled replication" isn't 
supported, or at least it wasn't with 7.6.2.  Not sure about 8.0, but it's 
worth checking into...


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of bingo
Sent: Saturday, April 06, 2013 7:18 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Data Domain in mixed BOOST/VTL mode?

Why do you really want to use VTL at all?

Using a DD you are talking to very fast network-attached AFTDs where NW 8 
clients can even use new technologies like Flexible Blocksize & Direct File 
Access. The data rates which you achieve here are amazing, especially when you 
stream data from various clients to multiple AFTDs and - at the same time - 
simulteanously clone data from these devices to tape (if needed at all). Only 
in rare cases, the clients must have faster NICs than 1GbE but of course that 
also depends on the data rate you must achieve.

My opinion is to avoid VTLs whenever possible. Yes, you have fast SAN access 
but IMHO this is the the only benefit. You really force a disk to behave like a 
tape and in general, you add an additional, unnecessary 'layer' which limits 
the flexibility B2D would offer. And of course it is a an additional component 
which potentially might cause trouble. Just avoid it!

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------