Kalau pengalaman saya pilih server yang paling powerfull dan punya HD space yang banyak, tetang tipe backup ada banyak macam. Mohon dibaca artikel berikut.
The following sections examine a few of the many strategies in use today. Many strategies are based on these sample schemes; one of them can serve as a foundation for the strategy you construct for your own system. Simple Strategy If you need to back up just a few configuration files and some small data files, copy them to a USB stick, engage the write-protect tab, and keep it someplace safe. If you need just a bit more backup storage capacity, you can copy the important files to a Zip disk (100,250 and 750MB in size), CD-RW disk (up to 700MB in size), or DVD-RW disk (up to 8GB for data). In addition to configuration and data files, you should archive each user's home directory, as well as the entire /etc directory. Between the two, that backup would contain most of the important files for a small system. Then you can easily restore this data from the backup media device you have chosen, after a complete reinstall of Fedora, if necessary. Experts believe that if you have more data than can fit on a floppy disk, you really need a formal backup strategy. Some of those strategies are discussed in the following sections. We use a tape media backup as an example. Full Backup on a Periodic Basis This backup strategy involves a backup of the complete file system on a weekly, biweekly, or other periodic basis. The frequency of the backup depends on the amount of data being backed up, the frequency of changes to the data, and the cost of losing those changes. This backup strategy is not complicated to perform, and it can be accomplished with the swappable disk drives discussed later in the chapter. If you are connected to a network, it is possible to mirror the data on another machine (preferably offsite); the rsync tool is particularly well suited to this task. Recognize that this does not address the need for archives of the recent state of files; it only presents a snapshot of the system at the time the update is done. Full Backups with Incremental Backups This scheme involves performing a full backup of the entire system once a week, along with a daily incremental backup of only those files that have changed in the previous day, and it begins to resemble what a sysadmin of a medium to large system would traditionally use. This backup scheme can be advanced in two ways. In one way, each incremental backup can be made with reference to the original full backup. In other words, a level 0 backup is followed by a series of level 1 backups. The benefit of this backup scheme is that a restoration requires only two tapes (the full backup and the most recent incremental backup). But because it references the full backup, each incremental backup might be large (and grow ever larger) on a heavily used system. Alternatively, each incremental backup could reference the previous incremental backup. This would be a level 0 backup followed by a level 1, followed by a level 2, and so on. Incremental backups are quicker (less data each time), but require every tape to restore a full system. Again, it is a classic trade-off decision. Modern commercial backup applications such as Amanda and BRU assist in organizing the process of managing complex backup schedules and tracking backup media. Doing it yourself using the classic dump or employing shell scripts to run tar requires that the system administrator handle all the organization herself. For this reason, complex backup situations are typically handled with commercial software and specialized hardware that are packaged, sold, and supported by vendors. Mirroring Data or RAID Arrays Given adequate (and often expensive) hardware resources, you can always mirror the data somewhere else, essentially maintaining a real-time copy of your data on hand. This is often a cheap, workable solution if no large amounts of data are involved. The use of RAID arrays (in some of their incarnationsrefer to Chapter 38, "Managing the File System," for more information on RAID) provides for a recovery if a disk fails. Note that RAID arrays and mirroring systems will just as happily write corrupt data as valid data. Moreover, if a file is deleted, a RAID array will not save it. RAID arrays are best suited for protecting the current state of a running system, not for backup needs. Making the Choice Only you can decide what is best for your situation. After reading about the backup options in this book, put together some sample backup plans; run through a few likely scenarios and assess the effectiveness of your choice. In addition to all the other information you have learned about backup strategies, here are a couple of good rules of thumb to remember when making your choice: If the backup strategy and policy is too complicated (and this holds true for most security issues), it will eventually be disregarded and fall into disuse. The best scheme is often a combination of strategies; use what works. Kalau kami menggunakan http://www.nongnu.org/rdiff-backup/. Semoga membantu. Salam Fatur On Jan 2, 2008 1:35 PM, pwt linux <[EMAIL PROTECTED]> wrote: > bagusnya sih kalo kita tentukan terlebih dahulu server mana yg akan > jadi tempat menampung data2 backup, saran saya: pilih server yg os nya > stabil dan reliable sehingga tidak ada keluhan dari pc client > dikemudian hari. > > > On 1/2/08, n1x nux <[EMAIL PROTECTED]> wrote: > > at first, Happy nU year! > > > > Saya admin pemula, mau tanya klo untuk skema backup yg baik bagaimana > > dengan kondisi setiap client menggunakan Os yg berbeda, satu linux dan > > yang lainnya windows. Server nya pun ada yang menggunakan Linux & > > Windows. > > > > Apakah kita harus mengingatkan setiap user untuk melakukan backup > > manual dengan memindahkan datanya ke Hardisk server yang telah dimount > > misalnya? > > > > Tolong Pencerahannya. > > > > > > Thanks. > > > > Regards. > > junk3r?? > > > > -- > > FAQ milis di http://wiki.linux.or.id/FAQ_milis_tanya-jawab > > Unsubscribe: kirim email ke [EMAIL PROTECTED] > > Arsip dan info milis selengkapnya di http://linux.or.id/milis > > > > > > -- > FAQ milis di http://wiki.linux.or.id/FAQ_milis_tanya-jawab > Unsubscribe: kirim email ke [EMAIL PROTECTED] > Arsip dan info milis selengkapnya di http://linux.or.id/milis > > -- Salam Fatur YIM = tiens_fatur -- FAQ milis di http://wiki.linux.or.id/FAQ_milis_tanya-jawab Unsubscribe: kirim email ke [EMAIL PROTECTED] Arsip dan info milis selengkapnya di http://linux.or.id/milis
