To do so, define your SQL client more than once, listing
SQLDbs in saveset list differently.
Add instance 1 of SQL Client in group1,
Add instance 2 of SQL Client in group2,
LAbel AFD1 in Pool1, AFD2 in Pool2
and setup POOL1 to allow Group1, Pool2 to allow group2 and so on.
HTH
TH
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of MIchael Leone
Sent: jeudi 22 octobre 2009 17:01
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] How to use multiple AFTD devices
Another clarification - I am speaking of a dedicated storage node - it
only backs up itself. It's a SQL server, so what I am backing up are SQL
DBs. So how do I get NetWorker to write to both devices at the same time?
And would I have to enumerate exactly what DBs I want to save, to each
device?
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
10/22/2009 10:55:47 AM:
> Thierry FAIDHERBE <thierry.faidherbe AT forem DOT be> wrote on 10/22/2009
> 09:54:39 AM:
>
> > Yes and no : AFD are NOT like tape : When 1 is full, the Session
> > is suspended until AFD space is recovered and does NOT continue
> > to another dev even if it is labelled in same pool.
> >
> > So, best is to create 2 AFDs, in 2 separate pools. Do load balancing
> > of your backups, some to AFD1's pool, the others to AFD2's pool.
> >
> > I have 6 AFDs devices defined as E:\AFD, F:\AFD, G:\AFD,
> > H:\AFD, I:\AFD and J:\AFD each one labelled in its own pool and I do
> > load balancing of my backups using groups. (define groups in AFD pool
> > authorized group list)
>
> You've lost me. You have 1 server, with 6 AFTD devices attached. And you
> have 6 pools, one each for each AFTD device. And so you have .. what,
the
> same client, defined 6 times, each with a different backup selection?
And
> each of these 6 clients is in a separate group? And you run all 6 groups
> every night?
>
> I'm still confused, sorry. :-)
>
> >
> > Works like a charm. E and F are 2TB Luns I stage in parallel.
> > Then stage as you need. Do not forget, 1 read (recover/stage/clone)
> > operation a time per device :-)
> >
> > Cheers
> >
> > Th
> >
> > -----Original Message-----
> > From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT
> > EDU]
On
> > Behalf Of MIchael Leone
> > Sent: jeudi 22 octobre 2009 15:41
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: [Networker] How to use multiple AFTD devices
> >
> > I have a question. I have a Windows NW 7.4.2 storage node that I use
as
> an
> > AFTD device. The disk space in question is presented from my SAN. So I
> > define the device as "FQDN:drive letter\file path", and this all works
> > wonderfully - I back up to disk, then clone to tape.
> >
> > Problem: I need enough space to total 2.5 TB in size, and my SAN only
> > allows me to present at most a 2 TB disk (it's an HP EVA 8000). So
what
> I
> > was thinking - present 2 disks on 1.2TB each (the daily backup size is
> 1.1
> > TB, so 2 drives would allow me to keep 2 days backup on disk).
> >
> > What kind of config do I need to tell NetWorker? Do I just define 2
> > devices, and as long as they are both in the same media pool, things
> will
> > Just Work? Will NetWorker treat it the same way it treats tapes -
i.e.,
> > will it fill up drive X: first, then start using drive Y:? Will it use
> > parallelism, and write to X: and Y: at the same time? I'm guessing
that
> I
> > can define multiple AFTDs this way, right?
> >
> > Has anyone done this? Is there something I am not taking into account?
> >
> > Thanks
> > --
> > Michael Leone
> > Network Administrator, ISM
> > Philadelphia Housing Authority
> > 2500 Jackson St
> > Philadelphia, PA 19145
> > Tel: 215-684-4180
> > Cell: 215-252-0143
> > <mailto:michael.leone AT pha.phila DOT gov>
> >
> > 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
|