Siebel Remote and Replication Manager Administration Guide > Administering Siebel Remote > Handling Failure and Recovery >

Siebel Client Database Failure

It is not necessary to perform laptop backups, because the information contained on the local database is a subset of the information stored on the server database. Therefore, in the case of a laptop or local database failure, the procedure is to reextract and reinitialize the local database for this Mobile Web Client. Any change made on the local database since the last docking will be lost. It is strongly recommended that the synchronization with the server be executed regularly.

If the client machine loses power during a merger process, then the Local database may be corrupted. To avoid this, make sure the client machine has sufficient power before synchronization.

If a client database becomes unusable because of a media failure or other event, you must refresh the client database. This requires that you run Database Extract for the client. Siebel Systems does not support restoration of local databases because it may result in inconsistency between the local and server databases. For information on running Database Extract, see Creating Mobile Web Client User Accounts and Privileges.

NOTE:  Depending on the kind of failure, database changes and file attachments that were awaiting upload during the next synchronization session may also be lost. In this case, the user must reenter them.


 Siebel Remote and Replication Manager Administration Guide 
 Published: 19 November 2003