--
******************************************************************
* Knut Helleboe | DAMN GOOD COFFEE !! *
* Norsk Hydro a.s | (and hot too) *
* Phone: +47 55 996870, Fax: +47 55 996342 | *
* Pager: +47 96 500718 | *
* E-mail: Knut.Hellebo_at_nho.hydro.com | Dale Cooper, FBI *
******************************************************************
>From Lucien HERCAUD_at_paribas.comTue Feb 13 14:29:38 1996
Date: Thu, 8 Feb 96 14:17:00 PST
From: "Lucien HERCAUD"_at_paribas.com
To: jan_at_nzxray.galen.co.nz
Subject: Re: nsr and indexes
From my own experience:
If you need client initiated scheduling of the backup operation,
better say on the client :
"rsh nsrhost savegroup my_client_group [-c my_client] [-l incr]"
than doing a "save" on the client itself.
The "save" solution has 2 disadvantages:
1. does no imply the saveindex for the client's index on the server -which
savegroup does-.
2. You need to specify the [-T "time"] option as taken from the last time
"save" was done - see the man page. Otherwise you save all the files as if
a full backup is asked, even if "-l incr" is specified.
Try the savegroup, maybe the "incr" will save you some space in the
indexes.
If not, you need to play with the BROWSE policy. The shorter the BROWSE is,
the smaller the online indexes will get. Also, you can manually go in and
PURGE the older versions for each filesystem of each client (see the
"indexes" menu).
Lucien HERCAUD
>From rockwell_at_rch.dec.comTue Feb 13 14:29:49 1996
Date: Mon, 12 Feb 96 11:56:53 -0500
From: "Paul E. Rockwell" <rockwell_at_rch.dec.com>
To: Jason Neil <jan_at_nzxray.galen.co.nz>
Subject: Re: nsr and indexes
On Thu, 8 Feb 1996 12:38:15 -0700 (PDT) jan_at_nzxray.galen.co.nz wrote:
> Hi
>
> We have a alpha running DU3.2c with NSR311, and are having a
> great deal of trouble keeping our online indexes to a managable size.
> The backups are instigated from a shell script using the save command.
> Retention policies have been defined using the GUI software, but I have
> the feeling that the unix commands bypass that somehow.
Is there a special reason that you're using NSR's save as opposed to
letting NSR schedule the backups? For example, are you running
a database that you're shutting down with the script, then making a fileset
clone with AdvFS?
> Is save the best command to use for backing up filesystems using nsr?
> (note: vdumps of the whole system are done monthly)
Depends on what you're doing. You may be doing redundant vdumps if you're
doing the whole system monthly. You should only need to vdump the root,
usr, and wherever the NSR indexes are residing. The rest can be handled
quite nicely with NSR.
> Do you need to specify some option on the unix command to tell networker
> to use a particular retention policy.
Retention policies are controlled via the client definition on the NSR server.
You set that with the browse and retention policies for the client.
>
> Basically, how would I keep the on-line on-line index's down to say a
> week or month?
What's your backup schedule look like? Are you doing a full backup each time?
That's a quick way to bloat the size of the NSR indicies.
To keep the size of the on-line indexes down:
1) Choose an appropriate browse time. Once all save sets in a backup cycle (the backup
cycle is a full, followed by all incrementals/level n backups until the next full)
have passed the browse time as defined to your client, then the entries will be
removed from the client index (but the save sets will still be in the media
index, and recoverable via scanner). So, if your backup cycle is one week, and
your browse policy is 1 week, then you can have up to 2 weeks of data in the on-line
indexes. See the "addendum.ps" file that's released with NSR (this is the Networker
Addendum manual" for a more in-depth discussion of the interrelationships among
browse, retention, and backup cycles.
2) Relating to 1), create an appropriate backup schedule.
3) Relating to 2): Use incremental backups liberally.
--------
+---------------------------+tm Paul E. Rockwell
| | | | | | | | Northeast Region SBU Technical Support
| d | i | g | i | t | a | l | Digital Equipment Corporation
| | | | | | | | 500 Enterprise Drive
+---------------------------+ Rocky Hill, CT 06067
Internet: rockwell_at_rch.dec.com Phone: (860)258-5022
-------------------------------------------------------------------
< Jason Neil Contact Details >
< Technical Co-ordinator Phone: 0064 9 3771780 >
< Galen Group Ltd Fax: 0064 9 3771787 >
< Auckland, New Zealand email: jan_at_nzxray.galen.co.nz >
-------------------------------------------------------------------
Received on Tue Feb 13 1996 - 03:20:55 NZDT
This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:46 NZDT