From owner-networker@LISTSERV.TEMPLE.EDU Sun Sep 10 16:36:02 2000 Return-Path: Received: from listserv.temple.edu (listserv.temple.edu [155.247.166.105]) by mailhost.nmt.edu (8.10.2/8.10.2) with SMTP id e8AMZwv12051 for ; Sun, 10 Sep 2000 16:35:59 -0600 Received: (qmail 23557 invoked by uid 0); 10 Sep 2000 22:35:25 -0000 Received: from listserv.temple.edu (155.247.166.105) by listserv.temple.edu with SMTP; 10 Sep 2000 22:35:25 -0000 Received: from LISTSERV.TEMPLE.EDU by LISTSERV.TEMPLE.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 731578 for NETWORKER@LISTSERV.TEMPLE.EDU; Sun, 10 Sep 2000 18:35:23 -0400 Delivered-To: NETWORKER@LISTSERV.TEMPLE.EDU Received: (qmail 24351 invoked by uid 0); 10 Sep 2000 22:35:19 -0000 Received: from agora.rdrop.com (0@199.2.210.241) by listserv.temple.edu with SMTP; 10 Sep 2000 22:35:18 -0000 Received: from joan.burling.com (root@ppp-d7.rdrop.com [199.2.212.40]) by agora.rdrop.com (8.8.7/8.8.7) with ESMTP id PAA00606 for ; Sun, 10 Sep 2000 15:33:06 -0700 (PDT) (envelope-from llywrch@agora.rdrop.com) Received: from joan (IDENT:geoff@joan [127.0.0.1]) by joan.burling.com (8.9.3/8.9.3) with ESMTP id LAA08478 for ; Sun, 10 Sep 2000 11:53:03 -0700 X-Sender: geoff@joan.burling.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-ID: Date: Sun, 10 Sep 2000 11:53:02 -0700 Reply-To: Geoff Burling Sender: Legato NetWorker discussion From: Geoff Burling Subject: [Networker] Networker FAQ -- Part 1 of 7 To: NETWORKER@LISTSERV.TEMPLE.EDU Status: RO Content-Length: 18811 Lines: 468 I've been lurking here for the last couple of months, & have noticed quite a few questions that should be answered in the FAQ. I checked with the folks who said they'd carry this chore on, & since they had no objection, & although I'm no longer responsible for it, I'm reposting the FAQ one more time. I hope this answers a few questions & save a little bandwidth. Geoff Burling =============================================================== Legato Networker Frequently Asked Questions - Version 0.91 (9 July 2000) ----------------------------------------------------------------------- Table of Contents 1. FAQ Administrivia 2. Mailing List Administrivia & Netiquette 3. Networker Resources 4. Common Error Messages 5. Care & maintenance of indices 6. Directives and Savepnpc 7. Networks and firewalls 8. Tape drives, backup performance 9. Weirdnesses unique to platforms, modules, versions, etc 9.1 Macintosh 9.2 MS Windows (95, 98, NT, 2000) 9.3 Netware/Novell 9.4 UNIX 9.5 Networker BSMs ----------------------------------------------------------------------- 1. FAQ Administrivia. 1.1 Legal Weasellings and Maintainer's Comments. This FAQ may not be distributed for financial gain. No warranties, no guarrantees. The information below is believed to be correct, but I have included statements that I have not rigorously verified. If something in this document trashes your server, I'm not responsible, nor are any of my employers, present past or future, nor anyone quoted in this document. Since this is written in the hope of being useful information, corrections are welcome. Unfortunately, the current maintainer is handing this duty over to other capable hands, and does not know what terms under which they will accept submissions. The goal of this FAQ is to cover issues involving Legato Networker, BSMs, or OEM versions of this product. Unless otherwise stated, everything written here is the opinion of the FAQ maintainer. 1.2 Availablity Starting with this version, this FAQ will be reposted at the beginning of the month. Hopefully, an HTML version will also be available within the month. 1.3 Version Notes. This is version 0.91, dated 9 July 2000. In other words, it's still beta, & still incomplete. Changes made from version 0.90 include: Added Rodney Wines' & W. Curtis Preston's discussion on savepnpc. Expanded the section on network issues. Added Keith Clay's description of troubleshooting slow backups. Added information on Legato Support for Win 2000. Added information to the Solaris and Oracle sections. Changes made from version 0.05 include: Jumped the revision level to 0.90, reflecting the maintainer's increased confidence in this document. Made some major reorganizations in the format -- compare the table of contents against the earlier FAQ for details. Added URL for a copy on the Web of the comp.arch.storage FAQ. Expanded the section on Directives to cover savepnpc. Created a section to cover network and firewall issues. Added some tips for the Sybase BSM from the maintainer's experience. As a result, he augmented the other BSM sections with information from other posts. Changes made from version 0.04: Netware section rewritten -- and hopefully I haven't made a bigger mess of explaining possible solutions. Added URL for the Kingswell web interface in section 3. Added information about the Digital/Compaq, & Data General OEM versions. Added Paul White's documentation on NetWorker and the archive bit for Windows NT. Added information about lock files. Changes made from version 0.03: Fixed numerous embarassing typos concerning the section on Legato BSM for SQL (NOT Oracle!) Added caveat to Netware section, based on information from J. Oritz. Added description of training from David Gold-news. Added URL for AIT drive configuration. Numerous minor clarifications. Changes made from version 0.02: Incorporated clarifications from Rodney Wines in the directives section. Added the build number for 5.5.2 from Russell Brown. Changes made from version 0.01: Reformatted the text to 80 column width and removed tabbing, in response to several requests. Added a Table of Contents per E P Tinnel's suggestion. Moved file path description of tape devices to section 7, after Ulrich Oldendorf pointed out that this varies greatly between flavors of UNIX. ----------------------------------------------------------------------- 2. Mailing List Administrivia & Netiquette. Stan Horowitz posted, on moving the Networker list to Temple University: Unlike the previous Networker list, this list is managed by Listserv software. A built Web interface is available to subscribers at http://listserv.temple.edu/archives/networker.html which despite what the URL implies, supports reading and sending messages to the list. You can also set various preferences for your individual subscription via this Web site. For example, if you prefer not to receive an acknowledgement and/or a copy of each posting you send to the Networker list, you can turn those options off. You also have the option of receiving the postings to this list via a daily digest. In addition, if you prefer to read postings only via the Web site, you can turn off messages altogether. Listserv provides for much flexibility, but since I have a very slow Internet connection right now, I will not elaborate in great detail. Check the Web site for details. This list's postings are archived on the Web site. Reto has indicated to me that he will move the old archived postings to the new Web site too. We will probably accomplish that in the next week or so. Note that everyone who was subscribed to the old Networker list as of approximately 5:00pm on March 13 is automatically subscribed to the new NetWorker list, however, you might want to subscribe again anyway just so your name gets associated with your email address. I should also say that I ask that a few basic rules be observed here. Most of these are tenents of standard Internet etiquette. 1) Please, do not post messages to the list from root or postmaster accounts. 2) Please identify each new posting you submit to the list with a clear and concise subject tag 3) If you feel the need to flame anyone, please do so privately. 4) If you have any comments or questions about Listserv or the Networker list, please send them to me privately to stan@temple.edu 5) Summaries are nice, but not required now. Feel free to send replies directly to the list if you think others might benefit from your comments. 6) Of course, let's stick to the topic at hand, Legato NetWorker. 7) Do not expect that I will read every message that's sent to this list. 8) Please identify the version of the NetWorker client and server you intend to ask about and the operating systems on which your client and server run. The author of this FAQ also notes that this web site has an option for removing yourself for brief periods from the mailing list. Since he finds vacation or ``out-of-office" notices annoying, he strongly suggests everyone to use this feature of Listserv as a courtesy to others. The practice of snipping irrelevant parts of email when answering may have become a forgotten & quaint custom at this time, but is still appreciated by some of us. Q. How do I unsubscribe? A. Point your web browser to http://listserv.temple.edu/cgi-bin/wa?SUBED1=networker&A=1, enter your email address & name, then click on the ``leave the list" button. Further questions are answered at http://www.temple.edu/Listserv/. You will not remove yourself from this list by sending the command ``unsubscribe" to the list . . . no matter how many times you attempt this. ----------------------------------------------------------------------- 3. Networker Resources. Q. Where do I look for answers for problems with Networker? A. Sources include: Mailing list -- Point your web browser to http://listserv.temple.edu/cgi-bin/wa?SUBED1=networker&A=1, enter your email address & name, then click on the ``leave the list" button. Further questions are answered at http://www.temple.edu/Listserv/. Mailing List archives -- www.wildheart.org (for the time being), listserv.temple.edu/archives/networker.html (eventually). The login/password pair for the wildheart.org site is networker/member. For temple.edu, each user must set her/his own pair of tokens. There is also a web interface to the list at http://www.kingswell.co.uk/nwug/. This may be preferable to users who wish to avoid trans-Atlantic latency. Script archive -- ftp.meitca.com/pub/networker/Scripts+Tools/ (for the time being.) Frequently Asked Question List (FAQ) -- if you are reading this, you know how to get it. But if you'd like a more current copy, here are places to look: * Mailing list. Starting with this version (0.90), I will reposting this on a monthly basis to the list. * WWW. I have some offers to post this to the web. This version (0.90) is the first one I feel that will be good enough to be worth the effort of hypertexting. www.legato.com -- Useful information at this site include manuals in PDF format, White Papers & Tech Notes, & the schedule for Legato training. This is also the location of their Tech Dialog database, which is a subset of their own internal support database. It requires a password, which is included in the price of support. www.backupcentral.com -- Deals with backing up & restoring data in general. Articles, links to resources, maintained by W. Curtis Preston, the author to _UNIX_Backup_&_Recovery_ (O'Reilly, 1999). One of the best web sites about data backup & recovery despite the fact there aren't many sites covering this topic. comp.arch.storage -- It may be my newsfeed, but I have found this to be a very low-volume newsgroup. Less than 10 posts a day. The FAQ for this group -- which was last updated in 1998 -- can be found on Deja.com at http://www.deja.com/[ST_rn=ps]/getdoc.xp?AN=316722147&CONTEXT=953588547.688717851&hitnum=3 and http://www.deja.com/[ST_rn=ps]/getdoc.xp?AN=316722170&CONTEXT=953588547.688717851&hitnum=25 (Note, with the older postings on Deja being unavailable at this writing, you may wish to refer to the HTML versions archived at http://www.cs.ruu.nl/wais/html/na-dir/arch-storage/part1.html and www.cs.ruu.nl/wais/html/na-dir/arch-storage/part2.html) ftp.legato.com -- Secured. This security also seems not to play nice with some firewalls: to upload files to the /incoming directory, I had to go to a site outside our corporate firewall & do the upload from there. Q. What training is available for Legato? A. David Gold-news contributed the following (29 March 2000): The best way to learn NetWorker is to work with it. But training can compensate for the fact that most people don't have a lot of spare time to figure out the things that manuals don't make clear. Legato currently (3-2000) has four authorized classes. (See below for availability): Admin-I/NT, and Admin-I/Unix: These classes are very similar, the difference being the operating system of the server. The Unix one tends to be a little bit more "hard core," as the materials go slightly more in depth. They concentrate on the server side; other client OS's are not an official part of the course. Take one of the two, but not both, and take it after having worked with NetWorker for 3-4 weeks (if just starting). Admin-II: This is the higher level administrator course. It is a newer course and delves into more advanced topics, like Firewall support, staging, pools and storage nodes. Take this after you are comfortable with the Admin-I material. Install&Config: This is a higher level course than the Admin-I, and delves into the actual install and configuration of NetWorker. I found much information that took a lot of time to find: Irix device types, for instance, are clearly laid out in this material. A very well designed course, and quite useful for doing installs and upgrades. This can be taken at the same time as the Admin-I. These course are available from Legato, as well as Legato training centers. See http://www.legato.com/Support/html/education_services.html (or www.legato.com --> services --> educational). Make sure to check both the Legato sites and authorized partners. In terms of operations courses (as opposed to administrative courses), Legato doesn't currently have an official one. We have one (yes, this is a plug, but brief), including course materials, etc and it is designed as a one day hands-on class. (See www.camcom.com or call 617-787-1230 for more info). I'm not sure if others have developed one. Q. I can't find NW for X on the ftp site. A. Joseph Ortiz wrote (7 Dec 1999): I've answered this one a time or two before but it never seems to make it into a SUMMARY so I'll post it this way in the hopes it will save someone else the time to ask for this information again. You will not normally be able to access any new versions of Legato software from the regular ftp site like you could back in the "old days". That has all been moved over to a password protected site as eval or trial software downloads. You have to go through Legato sales to get the password to download any specific new Legato software version. The only thing on the public ftp site now are versions considered patches/fixes, even if they are an update like 5.5.1. That is why you can find the 5.5.1 Networker server/client software for the major platforms (Solaris, HPUX, AIX, NT) but not the latest client software for Linux, Win98, etc. ----------------------------------------------------------------------- 4. Common Error Messages. (These are grouped here for ease of quick access. Suggestions for other common error messages are welcome.) 4.1 Authentication errors. Christopher Ho posted (5 April 2000): Q. What is "not a registered client" error? A. Wan-hsuan Wu has a very good method to solve this problem: Do you have a separate interface name assigned for the private IP for this client other than "regwww.domain.com.sg"? Or is this the hostname that corresponds to the private IP? If you would let me know what's in the client's /etc/nodename (or output of 'hostname') and what's in the client's /etc/hosts (only the portions about this client), I might be able to pinpoint to the cause. Basically, if the client has a primary interface name (like regwww.domain.com.sg) and a backup interface name (like regwww-bkup.domain.com.sg), this is how you would set up the client on Networker: 1. Set up the client using the the primary name (regwww.domain.com.sg). 2. Add all interface names that this client has (as seen in the client's /etc/hosts) to the Aliases field in the Client Setup. 3. In the View Details of Client Setup, enter the backup interface name of the server (for example, serverx-bkup.xxx.xxx) to the Server Network Interface field. 4. If you could not do reverse lookup on the client backup interface name from your backup server, then add the client's backup interface name (e.g. regwww-bkup.domain.com.sg) to the server's /etc/hosts. Other solutions that Christopher Ho reported in his post: Kai Valjakka talked about old clients, which could be taking up a license unknowingly. (not in this case) Jeffrey S. Jewett , Alain BADER said to include the FQDN of the client in the hosts file, and to add it into the client resource. Thawipong said to check the /etc/hosts on both the client and server. Stan Horwitz mentioned that the operating system should be the same, otherwise a ClientPak would be required. (not in this case) Matthew Russo postulated that "Sounds like a name alias problem to me. You need to edit the client resource and add all the names this client is known by in the alias field." (YES!!!!!) 4.2 Byte size errors. Q. On random new and re-used tapes, I infrequently get a message that looks like this: [date] [time] nsrd: media notice : volume "TMX017" on device "/dev/rmt/3cbn": read 4 bytes, expected block size of 131072, check system device configuration, disabling forward space record A. This appears to be a strictly Solaris issue, and requires modifying the st.conf file. Information on . Arthur Darren Dunhan posted (26 April 2000): Every, every time I've seen this, it's been a bad st.conf file. I could absolutely reproduce it by restoring from a tape. The error *persists* even after you've fixed the st.conf for reading older tapes saved under the previous version. After the tapes get recycled, the problems go away. While this is usually reported for servers running under Solaris, and points to settings in the st.conf file (information on how to do this can be found in section 8), a similar error message was reported involving Networker running on NT with a Netware client: The error message that I am getting is: device "\\.\Tape0" read 32768 bytes, expected block size 65536, check system device configuration. The backup has completed successfully. Joe posted (15 April 2000) the following solution: As the message suggested, I believe you have device configuration problem, or the tape you used for recovery was originally labeled as 32kb block. Your device is currently configured as 64kb, that's why recovery's stopped from the server side. If you set the device's inactivity time to shorter period of time, you may see the cussor back in the set time preriod (no guarantee). To fix your original problem and prevent it from happening, relabel -- Note: To sign off this list, send a "signoff" command via email to listserv@listserv.temple.edu or visit the list's Web site at http://listserv.temple.edu/archives/networker.html where you can also view and post messages to the list. =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=