Re: [Networker] AW: [Networker] Indexes do not appear in Networker Administrator
2004-11-09 10:42:19
Look at the output to the mminfo command you issues under the flags field.
If the second character is "b" you have indexes and they are not displayed.
If the second field is "r" it means the saveset is recoverable - does not have
information in the index database.
If mminfo reports the saveset as browsable but you still do not see the disks,
try to change the browse time to a few minutes after the savesets save time.
If now you will get the missing indexes, you problem might be a problem with
multiple client instances using different backup directives.
Itzik
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Grohal Klaus
Sent: Tuesday, November 09, 2004 17:07
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] AW: [Networker] Indexes do not appear in Networker
Administrator
It seems that there is a problem with the clientid. Is the Networker server
running on a cluster?
What shows the command "mminfo -va -c <yourserver> -r clientid |sort|uniq" ? Is
there more than one entry?
regards
Klaus
> -----Ursprüngliche Nachricht-----
> Von: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] Im Auftrag von Gerald Orban
> Gesendet: Dienstag, 9. November 2004 15:48
> An: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Betreff: [Networker] Indexes do not appear in Networker Administrator
>
>
> Recently we upgraded one of our Networker servers to V7.1.2.
> This server is
> in a remote site and is only backing up itself. Within a week or so of
> doing this we noticed that the indexes for the C:\ and E:\ partition
> were not being displayed under the Networker Administrator Index tab.
> However indexes for two other partitions on the same server are still
> being displayed.
>
> We can still recover files from the partitions with "missing"
> indexes using
> Networker User and running mminfo -AVOT indicates that the missing
> indexes
> (savesets) are in fact still available.
>
> We have tried running nsrck -L3 as well as nsrim -X. Neither resolved
> the issue.
>
> Has anyone come across a similar issue or possibly suggest some other
> troubleshooting approaches.
>
> Thanks
>
> --
> Note: To sign off this list, send a "signoff networker"
> command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can also
> view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
--
Note: To sign off this list, send a "signoff networker" command via email to
listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also view and
post messages to the list. Questions regarding this list should be sent to stan
AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
**************************************************************************************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or
the
sender immediately and do not disclose the contents to any one or make copies.
MBI - System Team
**************************************************************************************************
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
|
|