[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | NetWorker |
| Notice: | kits - 12-14, problem reporting - 41.*, basics 1-100 |
| Moderator: | DECWET::RANDALL .com::lenox |
|
| Created: | Thu Oct 10 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 750 |
| Total number of notes: | 3361 |
458.0. "Browsing problem with Unix client" by LUX06::GLOESENER () Tue Mar 04 1997 04:19
I have a browing problem with Networker V4.2A for Digital Unix. I have a server
and a client (Note that for security reasons nsrexecd does not run) on
the client. Both machines are clients to the server machine (i.e. the server is
its own client). Both clients are configured exactely the same way but for
the names and aliases.
Now when I backup the server everything is OK, and the saveset browsable.
The client (backuped by nwbackup or 'save -q -s servername -b poolname -W 80
-x -l full /') creates the index but it is never browsable by nwrecover.
An nsrim -v on the server gives:
client.domain:/, retension policy: Year, Browse policy: Month
26019 3/04/97 f 13630 files 471 MB recycle <--- ????
0 browsable files of 13630 total, 0 KB recovarable of 471 MB total
Why does it become recycle immediatly ? Note that nsrim issued immediataly
after the backup states 'browse -> recover -> recycle' instead of 'recycle' and
the next nsrim states 'recycle'
Any hints are welcome,
Gast
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 458.1 | Solved | LUX06::GLOESENER | | Wed Mar 05 1997 02:03 | 9 |
| I am really sorry for this useless note (.0) since I have detected
today that the date of the server system was exactely one year in
advance thus it must recycle the saveset according to its policy.
client: 5-MAR-1997
server: 5-MAR-1998
Sorry,
Gast
|
| 458.2 | Good Detective work on your part!! | DECWET::EVANS | NSR Engineering | Wed Mar 05 1997 09:52 | 0 |
| 458.3 | | DECWET::ONO | Software doesn't break-it comes broken | Mon Mar 10 1997 13:00 | 4 |
| Actually, this isn't useful. It illustrates the importance of
synchronizing system times.
Wes
|