Without doing that, you could also use normal save command
and as soon as backup is done, using nsrmm -o recoverable -S SSID
to flag the ssid as recoverable.
Another way may be to consider using archives ....
HTH
TH
Kind regards - Bien cordialement - Vriendelijke groeten,
Thierry FAIDHERBE
HP Services - Storage Division
Tru64 Unix and Legato Enterprise Backup Solutions Consultant
********* ********* HEWLETT - PACKARD
******* h ******* - 1 Rue de l'aeronef/Luchtschipstraat
****** h ****** 1140 Bruxelles/Brussel/Brussels
***** hhhh pppp ***** - 102 Blv de la Woluwe/Woluwedal
***** h h p p ***** 1200 Bruxelles/Brussel/Brussels
***** h h pppp ***** -> HP moves as from 20 August 2007
****** p ****** Hermeslaan 1a - B-1831 Diegem
******* p ******* BELGIUM
********* *********
Phone : +32 (0)2 / 729.85.42
I N V E N T Mobile : +32 (0)498/ 94.60.85
Fax : +32 (0)2 / 729.88.30
Enterprise number 0402.220.594 Email/MSN : thierry.faidherbe(at)hp.com
RPM/RPR Brussels Internet : http://www.hp.com/
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of George Sinclair
Sent: mardi 31 juillet 2007 23:36
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] What's the difference between these two save
command options?
I was looking at the man page for the save command. I'm unclear on the
difference between the '-K' and '-S' options.
-K Does not build connecting directory index entries.
-S Allows only save set recovery. This performs the save
without creating any index entries. This means that
the save set will not be browsable, although save set
recovery may be used to recover the data.
For example, suppose I want to back up a save set to a given pool (has
indexing turned on), but I don't want the index to get updated because
I'm willing to live with having only a recoverable save set and not a
browsable one, and maybe I'm planning to shut that path off the backups
anyway, and I don't want those index entries from the full to just get
carried along indefinitely - which it would do since I'm never gonna run
another full - then I see two options: 1. turn indexing off for the
pool, run the backup (either from server or client) and then turn
indexing back on for the pool. This is slightly dangerous, though,
because it may not complete before other groups that write to that same
pool start. 2. Simply run the save command from the client like 'save -s
server -S -b pool -l full /path'. But not sure about this '-K' option?
Do I want that, too?
--
George Sinclair - NOAA/NESDIS/National Oceanographic Data Center
SSMC3 4th Floor Rm 4145 | Voice: (301) 713-3284 x210
1315 East West Highway | Fax: (301) 713-3301
Silver Spring, MD 20910-3282 | Web Site: http://www.nodc.noaa.gov/
- Any opinions expressed in this message are NOT those of the US Govt. -
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
|
