Keep the backup server in an active savegroup (with a smallest saveset in
client definition).
If backup server is not part of any active group, it adds bootstrap saveset to
everygroup automatically.
Sent from BlackBerry® on Airtel
-----Original Message-----
From: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Sender: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
Date: Thu, 2 Dec 2010 12:51:30
To: <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
Reply-To: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>,
Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Subject: [Networker] Saving to storage node always puts "bootstrap" on tape
drive of server
I have a job where I am now directing the clients to save to a storage
drive, rather than the server. This group has always been set to "No index
save". Yet, since changing the clients to save to the storage node, the
job seems insistent on wanting to write a "bootstrap" to a tape in the
corresponding pool on the tape library of the server.
saveset server:server:bootstrap: percentage of inactive files by count:
0.06, by space: 0.02
Why does it want to write a bootstrap, if the group is set to "No index
save"? As it stands, I need to keep a tape of the same pool in the tape
library of the server, to write the bootstrap of this job. Ordinarily, I
save the bootstrap and all client indexes to a different pool using
"savegrp -O".
I know that bootstraps and client indexes can only be written to a tape
drive on the server, and not on a storage node. But I shouldn't be writing
either, with this job, should I? Any ideas why it is doing this, and how
to stop it needing 2 tapes (one in the server for the bootstrap, one in
the storage node for the data)?
--
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
|
