From now on the backups of the server are fully functional. <\/p>\n
Hardware failures<\/strong><\/p>\n To guard against hardware failures, I use mirroring on the server now Accidents\/software failures<\/strong><\/p>\n To guard against software failures and ‘accidents’ (accidentally <\/p>\n","protected":false},"excerpt":{"rendered":" From now on the backups of the server are fully functional. Hardware failures To guard against hardware failures, I use mirroring on the server now with two disks and have third disk for backup. Every week or so one disk … Continue reading
\nwith two disks and have third disk for backup. Every week or so one
\ndisk is removed from the array and replaced by the free disk. This way,
\nI have a complete server backup. <\/p>\n
\nremoving files e.g.) I have implemented backups of the server of
\nparts of the directory structure. I use the ‘dar’ program for that.
\nEvery month, a full backup is made, and then every day of the month, an
\nincremental backup is made (if no full backup was made). The backups
\nare stored on the hard disk of the server. Of course, the mambo
\ninstallation, configuration, and mysql databases for mambo are backed
\nup. Mysql is backed up by first creating a database dump using
\nmysqldump and then backing up the snapshot using the regular procedure.<\/p>\n