License for company backup software is expired. Meanwhile, the disaster recovery simulation schedule is approaching. So, this time, we have to make it done manually. We need to define steps on this agenda. Let see…
- Define components that need to be backuped:
- Database. We need to create database backup job that will run every day. The backup result file is in .bak format. Later we will convert to zip file for saving space. Currently we have about 10 database to backup.
- Intranet, executable inhouse software and the source code, including all third party compnonent since the source code wouldn’t compile without them.
- System backup, consist of php folder, configuration, and also all used third party component. It will save an amount of time since php and third party configuration are potential in creating system error.
- Set folder permission for remote server backup destination, since there is a scheduler from source server copying and writing backup file (.zip format) to the remote destination server. We will use 7z for the compressing routing, since its free, can uncompress wide range compressing file, and support for batch instruction.
- We need a batch job for compressing all backup file, and copying it to remote destination server.
- Database backup file run every day. Inhouse software backup run every two weeks to capture any modification of the program. While system backup run once a month. Routine is done by batch file.
- Deleting backup file for expired/out of date backup file, for freeing space. For database backup, we only keep five job days for daily backup, one backup for weekly backup, one monthly, and one yearly. While other backup we only reserve 2 last backup.
- Prepare documentation, such as how to configure system, configure php, database restoration, inhouse application and intranet configuration, etc.
We will discuss those backup more technically on later article.
0 comments:
Post a Comment