|
|
|
|
|
How to Back Up Your Network, Part 1
By: Walter Metcalf
Date: 07/26/00
This is the first article in a loose series on applications of the LAN we constructed in an earlier series on
Peer Networking. If you aren't
currently using a peer LAN similar to that one or have forgotten a lot of that
series, I suggest you review the series before proceding further with this
article. To assist you here are the important highlights of the series
important to this article:
- Each computer in your network must have Warp 4 Networking installed, specifically
TCP/IP along with File and Print Services (aka NetBios). See the article
Building Your Network, Part 1 for a good
review of this process.
- If yours is an ethernet network like our example in the series, be sure that each PC is
properly connected to the central hub using at least Category-3 or preferably Category-5 twisted
pair cable. If you are using Token Ring, then make sure your PC's are
connected according to the rules for that topology. The article Building Your Network, Part 2 gives a good summary of the requirements of each topology.
- Be sure the "TCP/IP Configuration (LAN) notebook for each PC is configured exactly as shown
in the article Connecting your LAN to the Internet .
- While always recommended, the Firewall is not actually used during network backup.
Set-Up Procedure
For the purposes of this article, I will be using BackAgain/2000 Workstation made by Computer Data Strategies.1 I chose this product for the
simple reason that it is the
one I use in my daily work, and have found it eminently qualified for backing up peer networks.
2 If you don't have a copy of BackAgain/2000 and wish to follow the
procedures in this article, you can download a time-limited
demonstration version from the CDS web site.
BackAgain/2000 provides backup functionality using many different modes, involving the command-line,
drag-and-drop, and point-and-click. My suggestion is that you try the different modes, find which ones
are most comfortable and effective for you, and stick with them. This will minimize the confusion that can
arise from switching back and forth between the different methods. In this article I will
primarily use point-and-click, augmented with other methods on occasion.
- Set Up Your Network
- Make sure each PC on your network has share access to each OS/2 (and DOS if desired) drive
that you want to back up. You can use either of the following procedures to accomplish this:
- Command Line
- NET SHARE C_DRIVE=C:\ /REMARK:SYSTEM_DRIVE
Notes:
- "NET", "SHARE", "=", and "/REMARK:" are keywords. The rest are placeholders
and may be replaced with any appropriate value.
- The "/REMARK:" parameter is recommended, but not required.
- The NET SHARE command requires administrative access to the workstation.
- TIP: Put the NET SHARE commands and LOGON command for each workstation
into an OS/2 CMD file for safe keeping.
- For a complete description of the NET command, please see the OS/2 Warp
Command Reference Online Manual, Part 2 .
- Point-and-Click
- Open the "Connections" folder, and then open the "Network Services" folder.
- TIP: Drag a shadow of "Lan Services File and Print" to the WarpCenter or the
ObjectDesk ControlCenter. This will save you a lot of time manipulating the
File and Print objects.
- Make sure you have administrative access to the workstation, and start the
"Shared Resources and Network Connections" object by double-clicking it.
- Click on the "Shares" tab, and click on the "Create a share" button at the bottom.
- Enter the drive to be backed up followed by a ":\" in the "Directory" window,
and click on "OK".
- Enter a name in the window entitled "Share name". (Note: this corresponds to
C_DRIVE in the NET SHARE command line.)
- Enter a comment (=Remark) in the description field, and click on "Manage Access...".
- Click on "Read/Write" (even if already selected), and click on the "OK" button.
- When the "Create Access Permissions" box appears, click on "OK" to clear it.
- When the "Create Share" window reappears, you are finished with that drive.
- TIP: Make sure each PC is always ready for a backup by including the
command "LOGON GUEST" in your STARTUP.CMD file, where GUEST is a username
that doesn't require a password. You can set up this user name on the "Users" tab
of the "Shared Resources and Network Connections" object. (Administrative access
is required to access this function.)
Next week we'll conclude this article by examining how to set
up and run BackAgain/2000 to actually back up the network. Stay tuned!
Walter Metcalf
For Further Reading: Setting Up a Peer Network on Warp 4, Part 1 First in a series of articles describing in detail how to construct a peer network. Backup: Why and How? Complete description of system backup process using BackAgain/2, the predecessor of BackAgain/2000. Home and Office Networking Collection of links on SOHO windows networking.
Notes
1 The term "Workstation" in this version of BackAgain/2000 refers to the fact that it is intended to be installed on a workstation, as opposed to the Server versions that are designed to be run on servers equipped with Warp Server or Warp Server for e-Business. Thus using the workstation edition is not inconsistent with its being used to back up a peer network. Indeed there are many features of this edition specifically designed for use on such networks.
2 This article should not, however, be contsrued as a full review of this product. For example, I will not be evaluating, mentioning all of BackAgain/2000's features, nor comparing it with other back up products.
Unless otherwise noted, all content on this site is Copyright © 2004, VOICE
|
|
|
|
|
|
|