Forums » Interstage BPM Server

• admin admin

  
   

  June 29, 2011 3:33:11 AM PDT

  Anyone have recommendations as to disaster recovery planning for an Interstage BPM Server and the underlying database?  Would Daily backups be our recommendation?

  Author: Leslie Swan
  Attachment:

• C.Y. Chen

  

  • 33 posts
   

  June 29, 2011 3:40:04 AM PDT

  Leslie:
  
  I used to host the software distribution app in a VM with SQL Server 2000.
  I'd configured SQL Server to be backed up every evening.  The database is the key.  As for the installation files, you don't need to back up as frequently.
  

  Author: C.Y. Chen
  Attachment:

• Ivar Alexander

  
   

  June 29, 2011 3:40:54 AM PDT

  For DR, you would likely consider a replicated or clustered database. The replication should be to databases that are physically far apart (1000's of miles apart). The Interstage BPM folders file system would also need to be replicated on a SAN or similar if they are using custom actions/agents/forms/smart pages/other things stored on the file system. For the Interstage BPM server itself, having a cold standby server around the replicated database might be good to ensure the server can continue running.

  Author: Ivar Alexander
  Attachment:

• admin admin

  
   

  June 29, 2011 5:13:56 PM PDT

  One of our client is following below strategy.

   

  On DB front, client is using DATA GUARD technology. It archive log files generated on primary which are transferred to standby site. The standby is in recovery mode, archive log files will get applied to standby and standby gets in sync with primary.

   

  Similarly on IBPM front, they have created replica of Production environment pointing to standby DB. In case of disaster they will up the standby DB, do some small changes in ibpm.properties table on standby DB and can start the IBPM server with very small down time.
   
  Please see lbelow link for steps to configure Interstage BPM Contingency setup
   
  http://forum.interstagebpm.com/post?id=5335451&highlight=contingency
  

  Author: Rajeev Kumar Singh
  Attachment: