I did a quick checklist - it is not exhaustive but it is enough to start
backing up.
Legato Networker brief checklist
OK, so you've installed Networker from the options panel, what's next?
Before you can start doing real work with Networker there are several
customizing steps to go through. If you have an Exchange server there
are another set of customizing steps. If you have an SQL server, yet
another lot, etc.
For all of the configurations the setup stages will be similar.
* Setup devices
* Label templates
* Schedule
* Policy
* Directive
* Group
* Client
* Pool
Most of the stages are dependent on some of the previous stages (i.e. to
create a pool you will need to specify selection criteria, this is
usually by client or group so these have to be created first).
Setup devices
Whether you have a stand alone tape drive or a multi-drive library, the
device(s) will have to be set up.
* At a command prompt on the Networker server type inquire - the
result shows you which devices that Networker can see.
* For a stand alone tape drive right click devices in the
Networker GUI and select create
o Enter the name of the device (this is what will appear on the
display)
o Enter the address of the device (from the inquire command)
o Select the device type
o Select the default capacity (if you don't do this then Networker
will show % used incorrectly)
* For jukebox/autochanger run JBCONFIG from a command prompt on
the Networker server. Follow prompts and set up each drive as prompted
Label template
This seems like a strange one to be doing so early but it is one of the
settings that can be done without dependencies. The label template is
used to form the tape label for various groups. You may have daily,
weekly and monthly pools with yet another pool for Exchange.
If you prefix the template name by the site code then the function then
the range - so for Exchange in Site1 we would have
Site1Exch
000 - 999
Delimiter .
This will create tape name SiteExch.000 and will increment the number by
1 each time (will roll round from 999 to 000)
Daily SiteDaily
Weekly SiteWeekly
Monthly SiteMonthly
Schedule
Schedules affect how much is backed up and when. You use a schedule to
specify whether it is a full backup, an incremental, one of 9 levels or
to skip backups for that day. Schedules are usually weekly based.
Exchange backups uses two schedules, one for full database backups and
one for incremental log backups (the OS uses yet another schedule -
default will generally do for that one)
Exchange schedules, then (once again use the site as a prefix)
Site_Exch_DB has full on Monday Wednesday and Friday, skip all other
days
Site_Exch_log has incr on Sunday, Tuesday, Thursday and Saturday with
skip on other days
This has the effect of doing a full Exchange backup every other working
day with log backups on other days.
Policy
There are to places where policy is used, browse policy and retention
policy. Browse policy is the length of time that the indexes will be
browsable (restores are easier if the index is browsable but it makes
the client indexes larger the longer they are kept). Retention policy is
the length of time that the tape is kept from when it is written to when
it is marked recyclable. (Note there are other factors as to whether a
tape can be marked recyclable such as another backup being dependent on
a saveset that is on that tape. When setting up a client the browse and
retention policies are selected from a drop down list - there are many
existing policies, create one to suite if not already available.
Directive
Directives are used to exclude specific files from the backup. Exchange
OS backup (the one with saveset all, see later) uses a directive to
exclude Exchange database and log files (these are backed up separately)
The exchange directive looks like this
Exchange_2003
<< "E:" >>
+ skip *.log *.edb *.stm
Do the same for each drive that the Exchange server has.
Group
Groups are used to set the start time of the backup, they can also be
used in pool selection to direct backups to a particular pool and can be
used to logically group clients. To allow the schedule setting of the
client to be used leave schedule and level fields blank (these will
override any client setting). When the group has been created and
populated with clients, test it the set it to autostart and select the
required time. For sites with autochanger and one drive try to set it so
that backups to different pools do not run at the same time.
Client
This is the main unit for backup, the client refers to the server that
is being backed up. Always have one instance of the client with saveset
All in an active group) even if that group doesn't run very often) this
will catch any drive additions, etc. that may have happened without your
knowledge. If you need to specify certain savesets then create another
instance of the client and specify the savesets (this instance of the
client will have to be in a separate group to the one with saveset all).
Ensure, after you have created a client and before you back it up, that
the long and short names appear in the alias field of the client setup.
For Exchange clients the settings should be
Saveset MSEXCH:
Note, it is possible to specify the specific storage groups but, by
doing it this way, if a storage group is added it will automatically get
backed up)
Remote access administrators@* and root@* (initially to get
things going then change to a more suitable id/machine combo)
Backup command nsrxchsv.exe
Pool
For sites with no autochanger try to keep the number of pools as low as
possible (preferably just the one) For sites with an autochanger but
only 1 drive, try to keep pool count low as well). Pools are generally
used where the media (or the data on the media) requires separate
handling. For instance, if standard file servers data is retained for 90
days and Exchange data for 30 then they would need to be saved to
different pools (can't delete some data off tape and leave rest)
Pool naming - use site function
SiteDaily
SiteExchange
Etc.
That was, if a tape has to be used in another backup server there will
not be a pool conflict.
There are many other settings within Networker, for the most part they
can be left at default setting. It is the intention that support
meetings will take a specific resource and explain all of the setting
fields, what they are for and a recommended setting.
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of David Mingia
Sent: 16 March 2006 15:09
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Networker Manual
Yea yea....
One of the things on my "to do list" is to document the simple task. An
instruction manual would be great !
David Mingia
Networks and Server Specialist
dmingia AT guilford DOT edu
Guilford College
5800 W. Friendly Ave.
Greensboro, NC 27410
336-316-2424
"Scalise,
Kathleen
(NSTS.JAX)"
To
<kathleen_scalise NETWORKER AT LISTSERV.TEMPLE DOT EDU
@ML.COM>
cc
Sent by: Legato
NetWorker
Subject
discussion Re: [Networker] Networker Manual
<NETWORKER@LISTSE
RV.TEMPLE.EDU>
03/16/2006 09:52
AM
Please respond to
Legato NetWorker
discussion
<NETWORKER@LISTSE
RV.TEMPLE.EDU>;
Please respond to
"Scalise,
Kathleen
(NSTS.JAX)"
<kathleen_scalise
@ML.COM>
I would be interested in that also, if there is something like that
available!
Kathleen Scalise
Asst. Vice President
Network Services and Technology Support
Merrill Lynch - Jacksonville, Florida
Phone: 904.218.5139
Fax: 904.218.5445
kathleen_scalise AT ml DOT com
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Reed, Jason
Sent: Wednesday, March 15, 2006 3:14 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Networker Manual
Has anyone created or know where I can download a quick reference guide
or manual that walks users step by step through the basic procedures.
This would be for incase I was not at work anyone could go through the
manual and restore backups, create clients, groups, and start backups
and so on.
Jason Reed
Network Administrator
MIMA
321-725-4500 ex.230
-----------------------------------------
This email, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this email is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution, or copying of this email is
prohibited. If you receive this email in error, please notify the sender
by replying to this message and delete this email immediately. At this
time, MIMA does not use email as an official means of healthcare
communication. If you email your physician there is no guarantee your
email will be responded to in a timely manner.
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 wit 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
--------------------------------------------------------
If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy,
retain or redistribute it. Click here for important additional terms
relating to
this e-mail. http://www.ml.com/email_terms/
--------------------------------------------------------
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 wit 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 wit 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
wit 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
|
