From owner-networker@LISTSERV.TEMPLE.EDU Sun Sep 10 16:33:57 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 e8AMXtv11871 for ; Sun, 10 Sep 2000 16:33:56 -0600 Received: (qmail 24700 invoked by uid 0); 10 Sep 2000 22:34:48 -0000 Received: from listserv.temple.edu (155.247.166.105) by listserv.temple.edu with SMTP; 10 Sep 2000 22:34:48 -0000 Received: from LISTSERV.TEMPLE.EDU by LISTSERV.TEMPLE.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 731473 for NETWORKER@LISTSERV.TEMPLE.EDU; Sun, 10 Sep 2000 18:34:45 -0400 Delivered-To: NETWORKER@LISTSERV.TEMPLE.EDU Received: (qmail 22809 invoked by uid 0); 10 Sep 2000 22:34:41 -0000 Received: from agora.rdrop.com (0@199.2.210.241) by listserv.temple.edu with SMTP; 10 Sep 2000 22:34:41 -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 PAA00324 for ; Sun, 10 Sep 2000 15:32:38 -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 LAA08496 for ; Sun, 10 Sep 2000 11:58:47 -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:58:47 -0700 Reply-To: Geoff Burling Sender: Legato NetWorker discussion From: Geoff Burling Subject: [Networker] Networker FAQ -- Part 4 of 7 To: NETWORKER@LISTSERV.TEMPLE.EDU Status: RO Content-Length: 10587 Lines: 241 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 =============================================================== Keith A. Clay shared with the list (22 June 2000) a very methodical plan of investigation he undertook when his backups ran too slow, & the results he found: After great advice from the list, here is what I have tried: 1. ran uasm -s -n -v /my_partition -- took 1 hour and 40 minutes to run on 18gigs 2. ran save with the '-i' to ignore directive files -- backup time was no better 3. ran save with '-i' and 'E' for estimate -- had to kill, was running more than a day 4. ran find piped to cpio -- took 8 hours to make copies. Then ran save on the directories with the cpio archives. Took 45 minutes to backup 18 gig. After isolating the problem to the partition itself, we found that in updating the mailstore, there were thousands (if not tens of thousands) of links that were unresolvable (this is solaris 7). We are right now assuming that these links are causing the increased save time. Later this evening, we are going to take the server down and remove this links. I am not sure if this will work, but it seems the logical place to begin. Also Mike Myer's contribution (29 Mar 2000), although Solaris specific, suggests some useful tricks: To eliminate your tape drive and cabling you should check your raw tape drive throughput. Under Unix you can do something like the following: dd if=/dev/zero of=/dev/rmt/0cbn bs=128k where bs is set to the value you have tuned the blocking size of your device. Then use the "iostat -x 5" command (the -x is necessary under Solaris to get "extended" stats (eg. stats on ALL devices) -- I'm not sure what the exact command is on other platforms). If you see throughput below the native throughput of your tape device you have a problem. You should see something closer to twice the native throughput because of compression. I have a suspicion that it doesn't go higher than about twice because of the little CPU that's doing the compression on the drive (because a stream of zeros should be HIGHLY compressible). Another trick to mention that's specific to NetWorker -- if you do a "mt -f /dev/rmt/?cbn fsf 2" before doing your testing on a tape it will protect the NetWorker label on the tape so you don't have to either find a "real" scratch tape or relabel when you're done. From experience I would start with changing the cable out (assuming you have your st.conf file tuned properly under Solaris and you're using the right tape device) ----------------------------------------------------------------------- 9. Weirdnesses unique to platforms, modules, versions, etc. Q. What software packages bundle a version of Networker in their distribution? A. As far as the FAQ maintainer knows, they are: Solaris -- brands Networker as ``Solstice Backup", keeping the version number identical to Legato's number. Support is available either thru Sun or Legato. OSF1/Digital/Tru64 UNIX -- Digital/Compaq has OEMed Networker, as described by Lyle Baumgartner (26 April 2000): Compaq went in and out of supporting Networker. I understand that they are back into the game. At the time that MetRo learned it was being dropped we switched our support over to Legato and obtained all of the client and server pieces from Legato. When we switched from DEC (Compaq) it was called Networker Save and Restore (NSR). Data General (DG UX) -- Submitted by Terry Lemons (27 April 2000): [From a Data General colleague] We bundle a restricted version of NetWorker into the DG/UX release. It is called LDBU (Data Backup Utility). It does not accept licenses, saveset choice is only "All", only one backup device is allowed, local backup only, and parallelism is limited to 2. So it is very restricted in its capabilities but it does work. Oracle -- Informix -- [Any help here would be appreciated.] 9.1 Macintosh Stein Bjorndal submitted (27 Mar 2000): I'm not a Mac person myself, but I've been involved in setting up backups for the bleeping things. The thing to make very, very sure of is that your DNS lookups and reverse lookups works correctly. As far as I know there is no such thing as a hosts file on the MacIntosh. There is also no such thing as a shell on the Mac, at least not included in the standard OS and normal employed diagnostic tools like 'ping' and 'nslookup' is either a) very well hidden or b) non-existent. So, the only way I know of to do ip-to-name lookups on a Mac is through DNS. I do believe that reverse (name-to-ip) lookups must also work. The installation of the software itself is pretty straight forward, but you were looking for weirdnesses or what? :) 9.2 MS Windows (95, 98, NT, 2000) Microsoft has a White Paper that discusses preparation for, as well as recovering from, a crash Exchange server crash at http://www.microsoft.com/exchange/55/whpprs/BackupRestore.htm Q. What versions of Networker exist for NT? A. Terry Lemons posted the following information (25 Jan 2000): Looking in Help ... About to determine the NetWorker version won't show the patch release, and knowing that is often as important as knowing the version. So, here's a table showing the Build numbers (which are showing in Help ... About and the Version/Patch they correspond to. Please add to and correct this. NetWorker for Windows NT Build Version 38 5.5 53 5.5 patch 1 75 5.5 patch 2 and 2a 97 5.5 patch 3 115 5.5.1 144 5.5.1 patch 1 165 5.5.2 (This Q may not be FA, but it is useful information that deserves to be preserved.) Q. What is Legato's support for Windows 2000? A. John E. Johnston shared (7 April 2000) the following information from Legato with the list: Frequently Asked Questions about W2K Q: What platforms does NetWorker 5.7 support? A: NW 5.7 is an NT family release. It supports both Windows NT 4.0 (Intel & Alpha) - SP5 & SP6a and Windows 2000 (Intel only) - Build 2195. Q: What NetWorker configurations do 5.7 support? A: Server- Workgroup Edition (2906), Network Edition (2902), and Power Edition (5902), as well as Storage Node (2081 & 5081) and Client Pack (3304 & 3302) Q: Do upgrade customers need a server "Update Enabler Code"? A: No, as long as they are on 5.5x they will not. If upgrading from 5.1 need to apply the 5.5x Update enabler code. Q: Is there a different "ClientPak" required for Windows 2000? A: No, The ClientPak enabler for PC Desktops (3302) supports Windows NT 4 Workstation and Windows 2000 Professional. The ClientPak enabler for Windows NT (3304) supports includes Windows NT 4 (Server, Workstation, and NT 4 Enterprise Edition, as well as Windows 2000 Professional, Server, and Advanced Server support. Q: Are NW 5.7 clients supported to my existing NW 5.x backup server? A: Yes, NW 5.7 supports down-rev servers based on the NW 5.x releases. Q: What about mixing and matching storage nodes? A: Yes, mixing 5.5.x storage nodes and 5.7 storage nodes is supported. Q: What about support for Windows 3.51? A: No, as of Q1'00 & 5.5.1, NW no longer supports Windows 3.51 as a server or a client. Q: Can NW 5.7 backup other NetWorker platform clients, such as NW 5.5.1 on Solaris and NW 4.15 on NetWare 4 & 5? A: Yes. Q. What's the difference between NW 5.7 and NW 5.5.2 running on the Windows platform family? A: NW 5.5.2 on Windows NT 4.0 delivers NetWorker library-sharing feature (within a datazone). NW 5.5.2 does NOT support Windows 2000. The corollary, NW 5.7 supports Windows 2000 but does NOT support library sharing in a datazone. These two features will come together in NW 6.0. Q: Legato announced the availability of Open File Connection (OFC) to replace Open File Manager from St. Bernard Software Software. When can I expect to see Open File Connection? A: The Open File Connection (OFC) is an integrated solution NW 5.7and above, and was scheduled to ship with NW 5.7. We were unable to complete the testing in the required time frame to make the Q2 media kit. Therefore, we had no choice but to ship NW 5.7 without Open File Connection and release Open File Connection on next available release train, with support for NW 6.0. Until then, continue to recommend our Complementary Product Open File Manager until we release Open File Connection. Q: How then do we backup open files on Windows 2000? A: Legato 's OFM (Open File Manager) from St. Bernard Software (as of version 6.2, available on www.legato.com/eval) supports Windows 2000. 6.2 OFM is compatible with version 5.5.2 and 5.7 NetWorker NT. Q: Open File Connection for NW 5.7 was announced as a Windows NT 4.0 product. Will we produce an Open File Connection on Windows 2000 and NetWare platforms? A: Yes, however Open File Connection for Windows 2000 & NetWare will be a "post NW 6.0" release, subject to change. Q: Does Windows 2000 support MS Exchange 5.5? Does our Exchange Application module support this combination? A: Microsoft does support Exchange 5.5. on Windows 2000. Legato NWM for MS Exchange 2.0-002 is currently on the product support patch download area, and is supported on Microsoft Windows NT & Windows 2000 Q: What is the value proposition of the various logo programs to my customer and does NetWorker 5.7 meet the requirements to be Microsoft 'logo' certified? -- 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. =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=