Brian,

I learn all kinds of spiffy things from this list.  I just wanted to say
a big "THANK YOU!" to everyone out there, either those who have answered
my questions, or those that ask questions - I'm learning equally.

The question below gave me reason to check my clients.  I've got two
machines with SQL databases on them, and neither are being backed up.

OUCH!
Good thing you found out, BEFORE the backup was needed for restore purposes.

What are the proper savesets to define to backup SQL machines?  Just
"MSSQL:", or should I define each database?  If defining each database,
what's the proper mask?

It is possible to backup all databases at once, using MSSQL:
However, I advise (if possible) to use
MSSQL:master
MSSQL:db_name1
MSSQL:db_name2

instead. This has the advantage that incremental backups of the databases can
be made ( backups of only the transaction logs ), next to full backups. When not
specifying the database name ( just 'MSSQL:' ), you can only make full backups!



greetings,

Dennis Voetelink

-----Original Message-----
From: Marilyn Schultz [mailto:marilyn.schultz AT MITCHELL DOT COM]
Sent: Thursday, February 06, 2003 11:37 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Masking of MSSQL Backups (Like Directives?)


NetWorker Server = Tru64 4.0D w/NSR 6.0.2
NetWorker Client = Windows NT 4.0
NetWorker Module for SQL = 3.0.1.86
SQL7

I have an SQL server with hundreds of individual SQL databases on it.  I
am currently using scheduled NetWorker backups with "MSSQL:" specified
in the saveset field.  This has worked fine for several months.  My
problem now is that the amount of data here has grown to 140 GB and
takes 10+ hours to backup.  Does anyone know of a way I can split this
up into smaller backup pieces - possibly similar to splitting a standard
disk drive backup using masking in the saveset field to include several
folders?

I tried using "MSSQL:db_prefix*", but got the following message:

* servername.mitchell.com:MSSQL:SF_V* nsrsqlsv: Database SF_V* does not
exist.

Any thoughts would be appreciated.  Thanks.

Marilyn Schultz
Mitchell International, Inc.
San Diego, CA

--
Note: To sign off this list, send a "signoff networker" command via
email to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also
view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
*******************************************************************

D. Voetelink
UNIX Systems Administrator

Netherlands Energy Research Foundation,
Facilities Department

Petten, Netherlands

email : voetelink AT ecn DOT nl
phone : (+31) 224 564738

*******************************************************************

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=