| |
|
|
| |
|
|
|
|
|
|
Backup
Regularly
 |
|
|
Of course. No exceptions. And
occasionally verify that the backups are valid. If you're out of the
office, make sure someone else understands and performs the backups.
As your network grows and becomes more
complex, you should reconsider the type of backup you perform. The major
types are:
Full Backup backs up all selected files. Differential Backup backs up
only selected files that have been changed. This is used when only the
latest version of a file is required. Incremental Backup backs up
selected files that have been changed, but keeps a copy of each
incremental version of the document. This is used when each revision of
a file must be maintained.
Consider changing your backup method as
the needs of your business evolve.
|
|
|
Use AntiVirus
Protection
|
|
|
Your job is to keep the server protected,
using server antivirus protection designed to prevent infected files
from being stored and reused by vulnerable client machines. Also keep
the virus definition tables up to date. Since hundreds of new viruses
appear monthly, there are usually monthly updates. Server antivirus
protection acts as a backup to client-based antivirus protection.
For a client-based product, the key
performance metric is the time it takes to scan the hard drives. But for
server-based products, it’s more important to watch real-time scanning
of files as they enter from the network.
Don't forget to add antivirus protection
on each new desktop before you add them to the network, too.
|
|
|
Add Service Packs
|
|
|
Things change. Bugs are discovered,
drivers are added for new products, software is updated. Keeping your
network current goes a long way in fixing the little irritating problems
that can add up to a major network disruption. PC Week runs a column
every issue called NOS Files, Patches and Fixes. Another source is the
manufacturer’s website. Record each pack installed in your Server Log.
|
|
|
Keep a Server Log Book
|
|
|
Is your network suffering from poor
performance or bottlenecks? Why? One of the best ways to diagnose
problems is to check what's been done in the past, looking for a
possible cause and effect relationship. There is a delicate balance to
the art of networking. If you enhance or replace a component in one
area, it could slow or impede the performance of another component.
Check the log and, if possible, undo what you've added step by step till
the performance returns to it's previous level.
|
|
|
Use Baselining to
Evaluate Performance
|
|
|
A baseline is a collection of performance
measurements captured during peak loads. Utilities for baselining are
included with both NetWare and Win NT. With these tools, you can gather
statistics on server utilization, memory use, and disk utilization, plus
the number of errors and collisions. This information (and your Server
Log) will prove invaluable when the LANtek System Engineer comes to
call.
|
|
|
Test New Applications
and Components Before Adding
|
|
|
If you can, test new apps during off-peak
hours to see the affect of each on the network. If you haven't boosted
your server, expect a dip in performance if you add heavy-duty apps such
as videoconferencing or a client-server application. Also, run rdisk any time changes are made
to the system (service packs, etc.) Do this before making the
changes.
|
|
|
Create User Groups
|
|
|
Assign share permissions to groups. Add
users to groups to grant access to shares. Assigning users individually
increases administration tasks. When you add a new user, you can copy an
existing users profile into User Manager to give the new user identical
rights. You can also create templates for creating new users.
|
|
|
|
|
|
Keep a Boot Disk on
Hand
|
|
|
Create an NT boot floppy disk for
emergency use. This will allow you to boot a system if the boot.ini file
is corrupted.
For Win NT: Format a floppy disk on the
NT system. From C drive, copy ntldr, boot.ini and ntdetect.com to the
disk.
|
|
|
Update Your Network
Diagram
|
|
|
Go ahead, get out your original network
diagram. Woefully out of date, is it? You've probably added quick fixes
and temporary work-arounds that aren't recorded in the diagram. This may
seem like a low priority, but a picture's worth 1000 words, especially
to those outside your department responsible for approving funding.
|
|
|
Get Good Advice
|
|
|
OK, here’s where the plug for LANtek
comes in. Networks are complex and ever-changing, and sometimes finding
just the right solution takes a level of expertise best left to the
professionals. Call the LANtek network consultants. It may be more cost
effective to ask for suggestions from experts; our Network System
Engineers. This is where all your hard work gathering performance
statistics will really pay off. The more LANtek knows about your
network, the easier it is for us to diagnose and remedy its problems.
Besides, we love well-prepared customers.
|
|
|
Keep your Skills
Current
|
|
|
After every major upgrade of a network
operating system, get trained on the new features just prior to the
installation. Did we mention LANtek has a training division that offers
network System Administration training? Call the LANtek Learning Center
at 610-683-8757, or visit us at www.pa-lantek.com/training.htm.
Don’t forget to train the users also,
if there are dramatically different login procedures. Change is
inevitable, but always easier to accept if everyone is prepared. |
|
| |
|
|
| |
|
|
|
|
|
| |
|
|
| |
|
|
|
|
|
