Personal Folder

• ACTIVITY ON DATABASE, INHOUSE APPLICATION AND INTRANET DISASTER RECOVERY
• STEP ON SITE AND DESKTOP APPLICATION RECOVERY
• INHOUSE APPLICATION INITIALIZATION TRIAL BY IT
• INTRANET INITIALIZATION TRIAL BY IT
• USER TEST ON INHOUSE APPLICATION AND INTRANET
• PLACE FOR DATABASE AND DESKTOP APPLICATION BACKUP
• BATCH FILE FOR BACKUP
• APPENDIX A. Step to Restore Database
• APPENDIX B. PHP and IIS Preparation
• APPENDIX C. TROUBLESHOOT

ACTIVITY ON DATABASE, INHOUSE APPLICATION AND INTRANET DISASTER RECOVERY

No Time Activity
1. 11:37 – 11:38 Unzipping backup20081226.zip, file size 356 Mb.
2. 11:41 – 11:53 Restoring database from .bak file to MSSQL 2000 database server.
3. 11:54 – 11:57 Check database server user and permission for database user.
4. 11:57 – 12:02 Check database server security so it can be access both from sql and windows user.
5. 12:02 – 12:07 Check PHP and IIS configuration.
6. 12:07 – 12:24 Set the configuration for inhouse application (.ini file) and intranet (.php configuration file at conf directory)
7. 14:00 – 17:00 Inhouse application and intranet trial (please see INHOUSE APPLICATION TRIAL and INTRANET TRIAL section).


STEP ON SITE AND DESKTOP APPLICATION RECOVERY

1. Unzip databases on folder C:\[DatabaseBackupPath].

11:37 – 11:38 Unzipping backup20081226.zip, file size 356 Mb.

2. Restore databases from unzipped file created on step 1 (CRDB, EMPLOYEE, ESOFNET, INTRANET, LDSDB, MBS, SERVICES, TITANDNN, TRACKING)

a. Please refer to Appendix A. Step on Restore Database

11:41 – 11:53 Restoring database from .bak file to MSSQL 2000 database server.
11:41 - 11:43 CRDB (242 Mb)
11:43 – 11:46 EMPLOYEE (894 Mb)
11:46 – 11:48 ESOFNET (209 Mb)
11:48 – 11:49 INTRANET (15 Mb)
11:49 – 11:50 LDSDB (13 Mb)
11:50 – 11:50 MBS (1 Mb)
11:51 – 11:51 SERVICES (8 Mb)
11:52 – 11:52 TITANDNN (19 Mb)
11:52 – 11:53 TRACKING (31 Mb)
b. 11:54 – 11:57 Check database server user and permission for database user (check only because its already set on preparation)
c. 11:57 – 12:02 Check database server security so it can be access both from sql and windows user, please refer to Appendix C. Troubleshoot (already set on preparation).
3. 12:02 – 12:07 Check PHP and IIS configuration (already set on preparation).
a. Copy php source from C:\[SystemBackupPath]. This source is equipped with non standard libraries currently used.
b. Please refer to Appendix B. PHP and IIS Preparation.
4. Unzip application on folder C:\[ProgramBackupPath] (already prepared a copy of each inhouse application and intranet)
a. 12:07 – 12:24 Set the configuration file for intranet
b. Set file .ini for each desktop application (Com Test, CRDS, INSURANCE, LDS, LDS CEVA, MBS, PERSONEL, SERVICES, TRACKING)
c. Need to update links on intranet front page (for intranet asp version)
5. Redirecting new intranet web path to intranet.pttitan.com
6. Set un-anonymous access to some web page (annual leave approval, etc).
7. Set client browser, add proxy bypassing for this new backup server.
8. 14:00 – 17:00 Run inhouse application and intranet trial.


INHOUSE APPLICATION INITIALIZATION TRIAL BY IT

INSURANCE, MBS, PERSONEL, SERVICES, TRACKING running well.
Problem found in CRDS. This application use SUNDB database. Since SUN no longer used because had been replaced by SAP, SUNDB is excluded from daily database backup. Attach SUNDB database to BACKUPSERVER database server fix the problem. We maintain a copy of SUNDB at BACKUPSERVER for this purpose.

Another problem is in LDS. At the very first time this LDS launched, this application migrate from old database (LDS) to new database (LDSDB). Old LDS database is excluded from daily backup. Problem fixed by deleting connection to old LDS database at the source code.


INTRANET INITIALIZATION TRIAL BY IT





Intranet frontpage running well. Application link on the right pane need to be changed to the new server name. Phone book, web mail, Electronic Document System, Tracking, MSDS Online, IT Survey, web dictionary run well.

Additional configuration is needed for HR system and IT Helpdesk. Set the configuration at .php file at conf directory of each directory.



USER TEST ON INHOUSE APPLICATION AND INTRANET




User test shown as picture above. Some user experience application on the backup server is slower than usually. This is because backup server hardware specification below the currently running server.

Email notification failed on CRDS. Need to configure xp_sendmail function at the database server.


PLACE FOR DATABASE AND DESKTOP APPLICATION BACKUP

All backup file stored on server called BACKUPSERVER.
1. C:\[DatabaseBackupPath] (database backup file on zip form, yaitu CRDB, EMPLOYEE, ESOFNET, INTRANET, LDSDB,MBS, TITANDNN, SERVICES, TRACKING)
2. C:\[InhouseProgramBackup] (backup currently running desktop application and source program on zip form)
3. C:\[SistemBackupPath] (php engine used, php.ini and phpinfo configuration)


BATCH FILE FOR BACKUP

Backup batch process running on server SOURCESERVER (currently running as database server, and desktop application server).
1. Database backup run daily on 01:00 am as MSSQL job.
2. Batch file run on 01:15 am, compress .bak file created on step 1, and then copy it to local SOURCESERVER and BACKUPSERVER.