Chapter 15:Network Integrity

Chapter Outline

  1. On the Test
  2. 3.4: Identify the main characteristics of network attached storage.
  3. 3.5: Identify the purpose and characteristics of fault tolerance.
  4. 3.6: Identify the purpose and characteristics of disaster recovery.
  1. Network Integrity
  2. The definition of network integrity is maintaining the state of the network such that all parts function as a whole in a sound and unimpaired state.
  3. The areas that must be included in a plan to maintain network integrity are:
  4. Documentation
  5. Disaster Planning/Recovery
  6. Fault Tolerance
  7. System Backup
  1. Documentation
  2. Documentation for the network includes information on the following:
  3. LAN/WAN topology
  4. Hardware inventory
  5. Software inventory
  6. Change logs
  7. Server information
  8. Router and switch configurations
  9. User policies and profiles
  10. Baseline documents
  11. Mission-critical applications and hardware
  12. Network service configuration
  13. Procedures
  14. Good network documentation aids in troubleshooting problems that occur within the network such as failed connections, failed servers, hung applications, WAN connection failure, and user resource access failure.
  15. Documentation can be formalized using custom forms or informally kept using inexpensive notebooks to record change and repair events.
  1. Disaster Planning
  2. A disaster is an event that causes widespread destruction or distress, or total failure.
  3. Planning for the worst-case scenario allows the network administrator, planning team, and technicians to anticipate the consequences of both natural and man-made disasters.
  4. Disaster planning may be as simple as writing a procedure to backup all data, or as complex as contracting for remote hot-sites with 100% uptime so that a network could sustain a disaster without loss of service.
  1. The Disaster Recovery Plan
  2. A disaster recovery (DR) plan follows a set of well-defined steps:
  3. Creation of the disaster recovery (DR) team
  4. Identifying the risks and vulnerabilities that threaten the network.
  5. Business Impact Assessment (BIA)
  6. Definition of needs
  7. Detailed plan development
  8. Testing
  9. Maintenance of the plan
  10. A disaster recovery plan is a living document that may take many weeks or months to develop and implement, and this plan must be consistently updated as changes are made to the network.
  1. Mirrored Servers (Failover Clustering)
  2. Mirrored servers provide 99.9% uptime for mission-critical applications and data.
  3. To build mirrored servers, both servers must be configured with identical equipment and software, and both must be attached to the network.
  4. The “primary” mirrored server answers requests from the network, and issues a “heartbeat” to its twin to let the secondary mirrored server know that the primary is servicing the network.
  5. When the secondary server does not hear a heartbeat in a predetermined time frame, it will begin answering requests from the network. The window between failure of the primary server and “cutover” to the secondary is usually 30 to 45 seconds.
  1. Clustered Servers
  2. Clustered servers represent two or more servers that are configured with identical applications and file structures, all attached to the network, and all answering requests from the network. All servers are acting as one very large server.
  3. Clustered servers can make use of replication services. Several servers may be located off-site and participate in replication to assure that data is identical on all boxes in the event of failure within the network or disaster.
  4. Clustering is very expensive to implement and is a complex implementation. For this reason, small- to medium-sized businesses usually do not choose this option for disaster planning and recovery.
  1. Power Protection
  2. Power loss is one of the small disasters that an administrator can mitigate without undo expense or complex configurations.
  3. Several types of power protection can be used in the network. The choice will depend on the nature of the operations and the stability of the geographical location of the business.
  1. Surge Protectors
  2. Surge protectors are designed to minimize the effects of power spikes, surges, and brownouts.
  3. Surge protectors do not protect equipment from “dirty power,” noise on the line, or power failure.
  4. Over time, the circuit breaker in a surge protector loses its sensitivity to power fluctuations and can allow great variation in power to pass through to components. This weakens the components and may contribute to premature failure.
  5. Surge protectors should be replaced at least yearly on equipment to reduce the likelihood of component damage.
  1. Online Uninterruptible Power Supplies (UPS)
  2. The purpose of a UPS is to provide enough power for enough time to allow a server or other critical machine the ability to shut down gracefully.
  3. An online UPS provides protection for equipment by conditioning the power before it reaches the equipment.
  4. Inside the UPS is a battery that stores power coming from a wall outlet. That power is then sent to the equipment. All noise and fluctuation is minimized, thus making the power used by the server “clean” again, and providing a power source should there be a loss of power.
  5. The size of the UPS depends on the wattage of the attached equipment. 1 watt = 1.4 VA. Calculate the wattage of the equipment, multiply it by 1.4, and determine the length of time necessary to complete the shutdown process and any other routines that must be done while the machine is still running. Most UPSs will provide 15-20 minutes worth of power by default, but if longer times are needed, then the total wattage must be multiplied by the amount of time (above 15-20 minutes) to determine the size of the UPS.
  1. Standby UPS
  2. A standby UPS allows power to go directly to the equipment while charging a battery in the UPS. When a power failure occurs, the UPS detects a reduction in power and cuts over to battery power.
  3. Some devices, such as servers, may reboot or shut down during a short gap between loss of power and cut-over to battery backup.
  1. Fault Tolerance

Fault tolerance is the system’s capacity to continue functioning given a “fault” or malfunction of one or more components.

  1. Disk Fault Tolerance
  2. Disk fault tolerance provides the network with the ability to recover from loss of function of a hard disk storage device, and to prevent loss of data stored on that device.
  3. One of several disk fault tolerance strategies can be implemented in the servers to protect the data. The most common is some form of Redundant Array of Inexpensive Disks (RAID).
  1. RAID Level 0
  2. RAID level 0 is commonly called disk striping without parity.
  3. This form of RAID allows data to be written across multiple disks, but does not provide any fault tolerance.
  4. RAID 0 requires at least two hard disks to implement.
  5. With RAID 0, both read and write performance will improve over single-disk usage.
  6. RAID 0 uses all available disk space for storage.
  7. This form of RAID is useful for noncritical data that is routinely backed up.
  1. RAID Level 1
  2. RAID level 1 is commonly referred to as disk mirroring (or disk duplexing when two controllers are used).
  3. With RAID 1, data is written to both disks at the same time. Should one disk fail, the other disk takes over servicing requests from the network.
  4. RAID level 1 requires two disks to implement.
  5. Mirroring/duplexing will provide good read and write access to data on the disk.
  6. Only 50% of the total disk space can be used for storage.
  7. This form of RAID is used where fault tolerance is needed, but cost is of a concern.
  1. RAID Level 2
  2. RAID level 2 is known as bit-level striping with Hamming code ECC.
  3. This level of RAID is not used in modern systems.
  1. RAID Level 3
  2. RAID level 3 uses byte-level striping with dedicated parity.
  3. Data is striped across multiple drives and a parity bit is written to a dedicated hard disk for recovery of lost data.
  4. Read performance with RAID 3 is good, but write performance is only poor to fair.
  5. This type of RAID is costly to implement and is not as efficient as other implementations.
  1. RAID Level 4
  2. RAID level 4 uses a method called block-level striping with dedicated parity.
  3. The difference between RAID 3 and RAID 4 is simply that 4 uses blocks of a size determined by the administrator and 3 uses a stripe at the bit level.
  4. Read performance is good and write performance is fair.
  5. This type of RAID is a midline between 3 and 5, but is not frequently implemented.
  1. RAID Level 5
  2. RAID level 5 is commonly known as striping with parity.
  3. This form of raid requires at least three disks. Data is striped across the disks, and a parity bit is written to the disk as well. This is not a dedicated parity disk system.
  4. Read performance is very good, while write performance is fair.
  5. When figuring available storage space, add the amount of disk space on all drives and subtract the amount of space on one drive.
  6. RAID 5 is considered to be the best choice for fault tolerance and performance.
  1. RAID Level 6
  2. RAID level 6 uses block-level striping with dual distributed parity.
  3. This form of RAID requires a minimum of four disks to implement. The equivalent of two disks is lost to parity.
  4. The read performance is good and the write performance is poor to fair due to the parity bits written to the drives.
  1. RAID Level 7
  2. RAID Level 7 is a proprietary form of RAID that uses an asynchronous cached striping mechanism with dedicated parity storage.
  3. Although a defined RAID level, consult the vendor for more information.
  1. Backups
  2. When determining a backup strategy, the first two considerations are how you want to accomplish the backup (the hardware) and what software you will use to complete this task.
  3. Some of the options for backup include:
  4. Small- and large-capacity removable disks
  5. Optical disks
  6. Magnetic tape (the most commonly used medium)
  7. Once the medium is identified, the administrator will determine a schedule of backups using one or more of the following methods:
  8. Full backups
  9. Incremental backups
  10. Differential backups
  1. Full Backups
  2. A full backup takes all data and commits it to tape.
  3. During a full backup, the archive bit (attribute) is reset to off to notify the backup software that the file has been saved to tape.
  4. Full backups done on a daily basis allow quick restore because only one tape will be used to complete the restore.
  1. Incremental Backups
  2. During an incremental backup, only files that have changed since the last backup are committed to tape. The last backup may have been a full, incremental, or differential backup.
  3. This method of backup is used in conjunction with weekly full backups.
  4. Incremental backups reduce the amount of time it takes to complete the backup process because of the limited selection of files that are backed up.
  5. When restoring, the administrator or technician must locate the last full backup, and all incremental backup tapes since the last full backup.
  6. Incremental backups reset the archive bit to off.
  1. Differential Backups
  2. A differential backup saves all files that have changed since the last full backup.
  3. To restore, only the tapes from the last full backup and the last (most recent) differential backup will be used.
  4. This method of backing up data is used in conjunction with weekly full backups.
  5. A weekly full backup and daily differential backups are considered the most efficient and safest strategy for maintaining data integrity.
  1. Other Considerations for Backup Strategy
  2. Tape rotation patterns are determined when the backup strategy is designed.
  3. The choices are:
  4. Daily rotation
  5. Weekly rotation
  6. Monthly rotation
  7. Yearly rotation
  8. With each option, the administrator must consider what archive of past data must be maintained for the business, and whether the cost of maintaining a large archive of tapes outweighs the protection of the data.
  9. Most businesses use either a weekly rotation or a monthly rotation to manage archived data.
  10. Tape storage is important to consider as well.
  11. Magnetic tape is susceptible to damage from natural elements including heat, sun, water, and humidity. Proper storage for disaster recovery is necessary.
  12. Tapes should be stored in climate-controlled rooms that are physically protected or at an off-site storage facility. The best option for disaster recovery is to contract with a third party to maintain the tape archive at a remote location. This method allows the tapes to remain safe should there be a disaster at the location of the business. Restoration of the data can then take place at the new location should the old one be rendered unusable.
  1. Network Attached Storage (NAS)
  2. NAS is a relatively new data storage concept that attaches large data storage boxes to the network, but does not require a server to manage.
  3. Access to NAS is controlled through file system permissions.
  4. NAS can use multiple file formats such as CIFS and NFS, allowing the storage facility to be platform (operating system) independent.
  5. When considering NAS, keep in mind that the NAS box is a storage facility, and does not expend any resources providing any other services to the network.
  6. NAS boxes can be brought down for maintenance without causing outages on the network.