Re: Directive to exclude MSSQL db

Directives don't apply to database modules.
I reviewed the NMM SQL VDI guide, and you can modify the nsrsqlsv command
with the -h option to exclude databases. Page 71 of the NMM 18.1 SQL VDI
User guide.

Dave
----------------------------------------------------------------------

Date: Wed, 7 Nov 2018 12:04:28 -0500
From: Michael Leone <Michael.Leone@PHA.PHILA.GOV>
Subject: Directive to exclude certain MS SQL DBs when using Networker Module
for Microsoft Applications?

I think I know the answer to this, but I'd like to verify. I have a MS SQL
2012 server, and it's got a lot of databases. One is over 600G, another is
479G, etc. Having just one backup job (specifying MSSQL: as the selection
criteria) gives me over 2TB to clone to tape.

What I want is to break up that backup group into multiple groups, each with
different client entries with different directives For example, I can
specify MSSQL:Big600GDB, and it will get just that DB.
But I then need to make another client entry that specifies a directive to
exclude just that DB.

And how do you do that? I know how to exclude regular filesystem entries,
but how do you make a directive to exclude SQL DBs?

Is it as simple as

<< "S:\" >>
+skip: Big600GDB.*

like any regular filesystem skip? Most importantly, does that work with the
Networker Module for Microsoft Applications (which is how I backup my SQL
DBs)?

--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
1800 South 32nd Street
Phila, PA 19145
Hours: 8AM - 4PM EST
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone@pha.phila.gov>


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module

> Directives don't apply to database modules.

Yeah, I tested it after sending the email, and saw no effect.

> I reviewed the NMM SQL VDI guide, and you can modify the nsrsqlsv
command
> with the -h option to exclude databases. Page 71 of the NMM 18.1 SQL VDI
> User guide.

Great! Thanks so much.

So this is what I am thinking:

1 client entry that explicitly lists the 2 (or 3) biggest DBs
1 client entry that excludes those same DBs

1 group that has the first client entry, starting at 7PM (for example)
1 group that has the second client entry, starting at 10PM (for example)

My next question: if the first group is still running a backup by 10PM,
will the second backup group just wait until the first group ends, then
start up?
I'm guessing that both groups can't run at the same time, because of the
type of connection into the SQL server that such a backup entails.

Or can both run at the same time, can they overlap?

Thanks


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module

In regard to: Re: [EMC-DataProtection-L] Directive to exclude MSSQL db,...:

> 1 group that has the first client entry, starting at 7PM (for example)
> 1 group that has the second client entry, starting at 10PM (for example)
>
> My next question: if the first group is still running a backup by 10PM,
> will the second backup group just wait until the first group ends, then
> start up?

Nope. In general, there's no "inter-group" logic, so the second group
will start as scheduled. It's possible that individual clients will not
run right away because of your server settings, but the group will start
and clients will be started as sessions are available.

> I'm guessing that both groups can't run at the same time, because of the
> type of connection into the SQL server that such a backup entails.

No idea about that, but the groups themselves will start as scheduled. If
the module can't handle multiple distinct connections, you'll probably
get failures, not delays.

Tim
--
Tim Mooney Tim.Mooney@ndsu.edu
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module