Networker

Re: [Networker] DATADOMAIN AS VTL

2011-01-05 02:50:01
Subject: Re: [Networker] DATADOMAIN AS VTL
From: Freddy Enslin <fenslin AT HOTMAIL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 5 Jan 2011 09:49:23 +0200
Hi Terry / James,

Is it possible that the EMC person meant striping the SQL backup not streaming? 
In that case the database backup can be split into for example 4 streams / 
stripes each writing to a different tape drive at the same time. I have done 
this at multiple clients to physical drives, I have never tried it to a VTL, 
not sure if there would be any benefit.

Regards,
Freddy

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of terry.lemons AT EMC DOT COM
Sent: 04 January 2011 09:59 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] DATADOMAIN AS VTL

Hi James

I don't know the details, and I'm very sorry that it was a 'nightmare'.

But seeing your posting reminded me that, as of NetWorker V7.6 SP1, there are 
three choices when using a Data Domain system in a NetWorker environment:

- virtual tape via Fibre Channel
- AFTD/FTD via CIFS/NFS via Ethernet
- BOOST via Ethernet

BOOST provides some GREAT features that aren't present in the other two 
choices, including clone-controlled replication and “distributed
segment processing".  Please see the "NetWorker Data Domain integration 
features" section of "EMC® NetWorker® Data Domain® Deduplication Devices 
Release 7.6 Service Pack 1 Integration Guide" (available on Powerlink at Home > 
Support > Technical Documentation and Advisories > Software ~ J-O ~ 
Documentation > NetWorker Family > NetWorker > 7.6 & Service Packs) for more 
information.

Hope this helps!
tl

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of James Pratt
Sent: Tuesday, January 04, 2011 1:43 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] DATADOMAIN AS VTL

I have to reply here, only because we started out using our DD box as an AFTD 
device using the network instead of the SAN - Very long story shortened - it 
was a total nightmare, did not meet the expectations that EMC guaranteed us, so 
in the end, they gave us the VTL license so we could use the SAN instead of the 
LAN - it also would have required a lot of custom scripting at the time... Then 
again, I will admit i have not been keeping up with the latest NW and DD 
versions, so things may be different ..  that all happened around the end of 
last summer/autumn.  :\  

cheers,
James

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Norman Owens
Sent: Tuesday, January 04, 2011 1:16 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] DATADOMAIN AS VTL

Thanks Terry.

I have also heard that EMC recommends converting the DataDomain to an NFS 
network-based storage device to get higher throughput from the hardware.   In 
that case the Networker server can write to it as an advanced file type device.

Can you comment on any such conversions?

Sent from my iPad


On Jan 4, 2011, at 8:51 AM, terry.lemons AT EMC DOT COM wrote:

> Agreed.  The deduplicating virtual tape drive 'maximum sessions' attribute 
> should be set to '1', to disable multiplexing (which is the ability to have 
> multiple concurrent streams sent to a single target device).  This is the 
> best practice for most/all deduplicating VTL implementations.
> 
> This is the opposite of a capability provided by some of the database 
> products, which is to support a single stream writing to multiple target 
> devices.  As far as I know, this should work just fine when sent to a 
> deduplicating virtual tape device.
> 
> Hope this helps.
> tl
> 
> Terry Lemons
> Backup Recovery Systems Division
> EMC²
> where information lives
> 
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On Behalf Of James Pratt
> Sent: Monday, January 03, 2011 12:08 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] DATADOMAIN AS VTL
> 
> afaik, DD VTL's cannot use multiple streams - this is because of the 
> target-based de-duplication, and is also why EMC has you add many more 
> VTL drives than normal - in order to compensate for less streams.
> 
> I think to a DD VTL, anything you send to it is just a datastream/data 
> to be de-duped once it gets there , so I'm not seeing how MSSQL could 
> be any different. :\
> 
> cheers,
> James
> 
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On Behalf Of Venkat Tudi
> Sent: Monday, January 03, 2011 11:52 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] DATADOMAIN AS VTL
> 
> Hi All,
> My understanding of Datadomain as VTL is once configured each vitual 
> tape drive can only do single stream. But we had some EMC come in to 
> give us some briefing on SQL module and they mentioned that we can do 
> multistreaming.
> So I double checked my configuration
> SAVEGROUP parallelism is 0 (means write as many stream as the clients
> give) Client Parallelism: 12 Target sessions on the Tape drive is set 4.
> SAVESET is MSSQL:
> 
> But I am still seeing single stream.
> I tested the same conguration to Physical Tape and I am seeing 4 
> streams.
> Am I missing some thing or the guy gave the briefing is talking 
> something incorrect.
> 
> 
> --
> Venkat Tudi
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type "signoff networker" in the body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or via RSS at 
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type "signoff networker" in the body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or via RSS at 
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type "signoff networker" in the body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or via RSS at 
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or via RSS at 
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>