[Networker] SV: [Networker] Networker DDboost replication - MTREE Vs directory
2013-09-18 02:35:07
I suppose MTree replication is what you're looking for if you want it to happen
automagically, without NW knowing about it.
/tony
-----Oprindelig meddelelse-----
Fra: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] På
vegne af Chester Martin
Sendt: 17. september 2013 23:47
Til: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Emne: Re: [Networker] Networker DDboost replication - MTREE Vs directory
Hello,
Clone controlled replication would be the way to go using ddboost. This would
be the only way that networker would know about the data that's been copied to
the other dd.
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of SZ
Sent: Tuesday, September 17, 2013 2:01 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Networker DDboost replication - MTREE Vs directory
Hello Networkers,
We are looking into switching our Networker backups from Datadomain VTL to
DDBoost. Currently we backup our data to a Datadomain DD890 VTL which
replicates to another DD890 at a remote location. In our current setup the
backup starts to replicate at block level as soon as it starts writing to the
directory in datadomain which is hardware based and near-real-time with no
additional effort from application or administration. Looks like starting from
DDOS 5.1 DDBoost uses MTree storage units and cannot replicate directly unless
an application initiates a cloning (replication) job manually or from a
schedule eg. in Networker "Clone Controlled Replication" .
In other words:
1. If cloning is not scheduled for few hours, replication will be behind few
hours so we need to keep clones going all the time which may lead to other
issues like multiple clone jobs running into each other.
2. If Networker is being upgraded, replication will not run until networker is
back online and clone is manually restarted.
3. Admin will have to frequently run reports to make sure the data is cloned
(replicated).
4. If you need tape cloning for longer retention, you need to run another
clone job afterwards
DDBoost/Mtree replication is totally depending on the application while
directory replication is:
1. automatic
2. hardware level
3. near real time
4. No dependency on application
5. no administration/scheduling needed
6. Replicates even when Networker is down for upgrade etc 7. tape cloning and
replication both can run simultaneously
The only benefit I can see is that Networker will be aware of replicated data.
It's almost like DDBoost is taking away a very desirable feature and replacing
with a less efficient process.
I am interested to know if and how you have configured DDBoost with replication
and your thoughts as this seems to be the future direction for DD replication.
Thanks
|
|
|