System Backup and Disaster RecoverySetting Up the ftServer System 5-25System Backup and Disaster RecoveryYour ftServer system provides many safeguards against losing data due to hardwarefailures. However, it cannot cover all contingencies, so it is still important to performregular backups and enact a good disaster-recovery program.Ethernet DevicesNetwork interface naming on ftServer systems running a supported Linux distributiontogether with Express Builder is different from that on other Linux systems. On ftServersystems, physical devices are given names corresponding to their hardware location.After installing Express Builder, the interfaces associated with the Ethernet adapters areoperational. Multiple interfaces can be bonded together in a channel-bonding interface.This section discusses the following topics:• ‘‘Physical Device Naming”• ‘‘Monitoring and Configuring Channel-Bonding Interfaces”• ‘‘MAC Addresses”Physical Device NamingOn many Linux systems, Ethernet devices are normally assigned names based on theorder of discovery at system startup. The names begin with the letters “eth,” followedby a number starting with 0 and counting up. This is convenient because the first (andoften only) device on a host is predictably named eth0 and can be configured withoutdetailed knowledge of the device type.On an ftServer system, configuration may change dynamically when hardware failuresoccur, repairs are made, or when an administrator adds or removes components.Creating new Ethernet device names when new hardware is installed, tracking thename of an device while it is removed and replaced and matching it up again, ordeleting the name would be difficult and the results confusing.Instead, Express Builder assigns to network devices names that are derived from theirphysical location in the system. Table 5-2 shows the names of the embedded Ethernetdevices in ftServer CPU-I/O enclosures.
