From owner-networker@LISTSERV.TEMPLE.EDU Sun Sep 10 16:34:44 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 e8AMYcv11932 for ; Sun, 10 Sep 2000 16:34:39 -0600 Received: (qmail 24333 invoked by uid 0); 10 Sep 2000 22:35:09 -0000 Received: from listserv.temple.edu (155.247.166.105) by listserv.temple.edu with SMTP; 10 Sep 2000 22:35:09 -0000 Received: from LISTSERV.TEMPLE.EDU by LISTSERV.TEMPLE.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 731541 for NETWORKER@LISTSERV.TEMPLE.EDU; Sun, 10 Sep 2000 18:35:06 -0400 Delivered-To: NETWORKER@LISTSERV.TEMPLE.EDU Received: (qmail 23978 invoked by uid 0); 10 Sep 2000 22:34:47 -0000 Received: from agora.rdrop.com (0@199.2.210.241) by listserv.temple.edu with SMTP; 10 Sep 2000 22:34:47 -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 PAA00384 for ; Sun, 10 Sep 2000 15:32:45 -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 MAA08503 for ; Sun, 10 Sep 2000 12:00:08 -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 12:00:08 -0700 Reply-To: Geoff Burling Sender: Legato NetWorker discussion From: Geoff Burling Subject: [Networker] Networker FAQ -- Part 5 of 7 To: NETWORKER@LISTSERV.TEMPLE.EDU Status: RO Content-Length: 12699 Lines: 237 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 =============================================================== A: There are at least three different logo programs currently promoted by Microsoft. BackOffice 4.5 - Promotes Windows NT 4 and Windows BackOffice Application family (SQL, Exchange, etc) interoperability and exploitation. For a technical reading of the spec, see: www.microsoft.com/backoffice/designed Application Specification for Windows 2000 for Server Applications - Promotes platform exploitation of newest Windows 2000 Server technologies such as Active Directory, Security Services, etc. For a technical reading of the spec, see: http://msdn.Microsoft.com/library/specs/w2kserve.htm Application Specification for Windows 2000 Client, promotes client side acceptance of server technologies listed above as well as general Windows look and feel issues: For a technical reading of the spec, see: http://msdn.Microsoft.com/library/specs/w2kcli.htm NetWorker, as a heterogeneous (cross Platform) product, has significant technical challenges to meet these marketing requirements. It is a fundamental requirement to attain core backup & recover competency before extending the product feature set to meet additional requirements in logo programs. While some Logo requirements have been met, with 5.7 there was insufficient time to meet both NetWorker fundamental storage management requirements as well as all logo program market requirements. Over time, NetWorker will endeavor to attain all logo program goals, however it is currently unclear how long this will take, and how quickly we can respond to changes by Microsoft in these specifications. Q: What is RSM (Removable Storage Manager)? Does NetWorker 5.7 support it? A: RSM is a service included with Microsoft Windows 2000 and Microsoft Windows 2000 that facilitates communication among applications, robotic changers, and media libraries. It enables multiple applications to share local robotic media libraries and tape or disk drives, and manage removable media within a single-server system. A group of libraries, drives, and media that are managed by RSM is called an RSM system. RSM can help you create an application that makes effective use of the media resources in an RSM system. NetWorker 5.7 does not currently utilize RSM for media resources. If a system uses RSM, NetWorker cannot share this autochanger resource, and that that if the system does not intend on using RSM, that the autochanger be manually disabled from RSM's use in order to co-exist with NetWorker. We are well underway to providing integration between NetWorker and Microsoft RSM, in a future release, "post NW 6.0". Q: How do we position against RSM? A: RSM provides application level sharing of an autochanger on a single Windows 2000 system. In contrast NetWorker Smartmedia enables application sharing to connect dissimilar systems, on potentially dissimilar platforms to share libraries. Tape Library sharing, shipping with 6.0 will only allow for application sharing within NetWorker. Additionally, plans are underway for integration between Smartmedia and RSM, in a future release, "post NW 6.0". Q: What about SmartMedia on Windows 2000? Does it work with NetWorker 5.7? A: No, Not yet, SmartMedia version 1.4 is required to support 5.7, and it is targeted for release in May. Q: What is RSS (Remote Storage Service)? Does NetWorker 5.7 support it? A: "Remote Storage is a two-tiered remote storage solution. Third-party software developers are able to develop multitiered remote storage solutions that make use of the new system infrastructure such as the high-latency file attribute. The Windows 2000 operating system provides an efficient and user-friendly platform for hierarchical storage management-by running Remote Storage on the Windows 2000-based computer, and by supporting the development of ISV products." Legato HSM for NT 4 is not supported on Windows 2000. We expect to have a better understand of our HSM roadmap, and possible options such as continuing with OTG solution to provide HSM technology, or other alternatives, in the coming quarters. It is unlikely we will be able to deliver an HSM solution feature before 1H'01. Q: Does NetWorker 5.7 support Windows "Thin Clients" (Terminal Server/Services/Citrix)? When? A: Not in 5.7, target is NW 6.0, 2H'00 Q: Have Disaster Recovery procedures been tested and updated for 5.7? A: Yes, the new procedures are documented in the Disaster Recovery Guide. Q: Can we do a "Bare Metal" Recovery on Windows 2000 with NetWorker 5.7? A: No, During the development of NetWorker 5.7, Microsoft is positioning ASR (Automatic System Recovery) as the Windows 2000 bare metal solution, and NW 5.7 had support for ASR. With Beta 3-RC0, MS dropped this feature, so we had to as well. ASR will likely be re-introduced by and we will re-evaluate the work required to provide NW ASR support. Q: What kind of licensing changes for clustering does NetWorker 5.7 introduce? A: Clustered NetWorker Server (NT 4 EE Only) requires Power Edition. Clustered NetWorker Clients do not require PE, and can be backed up with NetWorker Network Edition Q: When is Service Pack 1 expected for Windows 2000? Will NW 5.7 support it? A: Microsoft has announced Service Pack 1 for Windows 2000 as becoming available in June. We will of course support SP1, however official support may lag by a quarter while test resources are brought to bear. It is not expected to be a significant test effort or risk. Q: When will Microsoft ship Data Center Edition? Will NetWorker 5.7 support Data Center Edition? A: Microsoft estimates availability within 120 days of the Feb. 17 release of Windows 2000. We are working with Microsoft and selected hardware partners to beta test our solutions against the Data Center Edition. Support for some DCE features, such as 4 node clustering, may not be initially available, but are being evaluated and planned for subsequent releases. Q: I've heard that Microsoft is working on a 64-bit version Windows 2000? A: Yes, Microsoft has announced this strategic direction. NetWorker is well underway to becoming a fully 64 bit application and positioned to exploit this environment in the second half of 2000. Q: How can I get a copy of W2K? A: Legato IT controls what OS versions are sanctioned and officially supported, so until they officially bless Windows 2000, each department is on their own to obtain and support Windows 2000 to meet individual product support and training needs. Q: Where do I get additional technical information on NetWorker 5.7? A: Check out the updated 5.7 Product manuals: Release Supplement: www.legato.com/infodev/publications/NetWorker/WINDOWS/5.7/cd_docs/winrs.pdf Installation Guide: www.legato.com/infodev/publications/NetWorker/WINDOWS/5.7/cd_docs/winig.pdf Disaster Recovery Guide: www.legato.com/infodev/publications/DisRecov/5.7/cd_docs/disrec.pdf Additionally, as part of the Q2 Release Train, there will be an electronic training made available to the field, and technical support has received beta level product training. Q: Will NW 5.7 be given as a customer training? A: No, Customer training classes will be designed around NW 6.0 and therefore will cover NW for Windows 2000 concepts. For more information please contact training@legato.com Q: Does NetWorker 5.7 backup individual records in AD? A: No, currently Microsoft only recommends a monolithic approach to AD backup and recovery. Q: On Windows 2000 what happened to the Repairdisk: and Registry: savesets? A: The rdisk.exe program has been eliminated, as its meaning has been changed see http://support.Microsoft.com/support/kb/articles/Q216/3/37.ASP. The registry saveset is now included within the "system state:" saveset on both NT 4 and Windows 2000. Please see NW 5.7 Release Notes for more information Q: When will NetWorker 5.7 SAN Ready or SAN Certified? A: Legato certifies in a SAN environment with some form of library sharing. Built-in NetWorker Library Sharing for NT 4 was provided with 5.5.2, and as SmartMedia version 1.4 is required for NetWorker 5.7, today, we are not yet SAN certified. We intend on having NetWorker for Windows 2000 SAN certified in Q3'00. Q: What is a Reparse Point? Does NetWorker 5.7 support Reparse points? A: See: http://msdn.microsoft.com/isapi/msdnlib.idc?theURL=/library/psdk/winbase/fsys_2nsj.htm NetWorker 5.7 does support reparse points. Q: What is DFS? Does NetWorker 5.7 support DFS? A: See http://msdn.microsoft.com/isapi/msdnlib.idc?theURL=/library/psdk/network/ntlmapi_0i9f.htm No, NetWorker 5.7 does not support backing up data across the DFS mount point. Q: What are Volume Mount Points? Does NetWorker 5.7 support Volume Mount Points? A: See http://msdn.microsoft.com/isapi/msdnlib.idc?theURL=/library/psdk/winbase/fsys_0rhv.htm. Yes, NetWorker 5.7 supports volume mount points Q: The Installer looks different? Why is there a new installer? A: Yes, we implemented the new MS installer, an MSI (Microsoft Installer) compliant installer for Windows 2000 Logo certification efforts. This installer offers improved ease of use and some degree of fault tolerance over previous Microsoft approved install methodologies. Q: I've just installed NetWorker and noticed the default path for install is "Program Files. What happened to \win32app? A: To meet logo specified path all application directories should be offered within "Program Files". Please consult NetWorker 5.7 and Application Module Release Notes for any caveats relating to directory paths. Q. On my Windows 95 client, Networker is backing up files that have not changed or even been accessed for months during both full & incremental backups. What is causing this? A. Dennis Peterson posted the following (19 Nov 1999): A file with a reported unknown creation date in the properties screen is always backed up even if the last modification date/time was before the last full backup. The archive flag also has no effect on the backup status. I have only been able to see the creation date on files or folders using the properties selection on a individual file or folder so it is difficult to check many files but this problem seems to be consistent with the several systems I have checked. I tested this by using some freeware (Properties Plus) that allows me to set the creation date without changing the file modification date/time. After setting any creation date the files were handled correctly. I was not able to find any software to set the folder/directory creation date but it was backup as an empty folder. I have no idea how these files are created with a valid modification date but unknown creation date. I have found them on many different systems at my site when I started looking for them. The files are everything from autoexec.bat to application files. Legato is pointing fingers at Microsoft but if the last modification dates (the only thing you see in explorer or directory listings) were used the creation date should not be an issue. I have used the freeware to reset the creation dates on all files on all my systems to a known early date (1/1/1986) and everything seems to work properly. What I don't know is if any unknown date files will be created in the future or if is an artifact of the software installation process. -- 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. =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=