Backup Recommendations

This site no longer maintained and here for archival purposes.

When running a Dataworks system it is important to backup the software and configurations, the database, and data files. Because the local environment is a major consideration when doing backups, the current ducmentation provides some hints for backup. In the future UNAVCO may develop additional modules to aid in backup management.

The following is a partial description of good practices to follow.

The critical information to backup is the FTP data directories and the MySQL database. Keep in mind, if your organization is a mirroring data and metadata from another data center, all the site metadata and data will be available from the remote data center for rebuilding the mirror. Your local additions cannot be recovered that way, so backup is essential. UNAVCO also recommends you backup any changes to GSAC code, database schemas, python code and support scripts. If your organization already has experience and procedures for backing up file systems and MySQL databases, we recommend you follow those procedures.

If your organization has an operational data center or server facility, and you want additional recommendations for securing a back up of the FTP data directories and MySQL database, we recommend you use a network based backup utility, e.g., http://www.emc.com/data-protection/networker.htm, and backup the critical file systems for the FTP data and MySQL data directories.

The FTP data directory is

/data

The MySQL data directory is

/var/lib/mysql

If your organization does not have a server facility and not much experience with network based backup and recovery, you will need to setup a couple of scripts to dump the MySQL database and rsync the output and the FTP data directories to another server.

An example mysqldump command (see http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html) looks like the following:

$> mysqldump -h localhost -u dataworks -p --add-drop-database

--add-droptable --single-transaction --add-locks --triggers name_of_database   

./name_of_database_dump_file-date.sql 

An example rsync command (see http://www.comentum.com/rsync.html) looks like the following:

$> rsync –arv /data user@192.168.0.10:/backups

Last modified: 2019-12-24  02:29:49  America/Denver