Recover from a database failure

When a Connections application experiences a database failure that involves restoring to a backup, without replaying the transaction log to the point of failure, we can perform steps to ensure a consistent data state.

Widgets internal to the Communities application...

• Bookmarks
• Members
• Feeds

Widgets external to Communities...

• Activities
• Blog
• Files
• Forums
• Ideation Blog
• Media Gallery
• Status Update
• Wiki

Communities is tightly integrated with the external widget data. When you perform backups of the databases, you might back up Communities database data on a different schedule than the other applications' database data. If a disaster occurs, for example, if the Activities database fails and restore from a backup of the Activities database that is two days old, after the Activities database restore, the Communities database is now more up-to-date than the Activities database. Any changes that were made to the Activities widgets in Communities in the past two days are lost and the two database are no longer synchronized.

You might also need to remove orphaned community microblog data as part of the community widget life-cycle disaster recovery process. A microblog is a message posted to a community activity stream. Microblogs display in the aggregated list of events, along with other type of events when users select the Recent Updates view. Users can display microblogs exclusively by selecting the Status Updates view.

• Recover remote Connections applications
• Compare remote application data with the Communities database
• Generate a synchronization report
• Assign orphaned remote applications to a community
• Delete orphaned data
• Synchronize remote application data with the Communities database

Parent topic:
Administer widgets and remote applications

Related:
Maintain application databases
Back up and restore data
Delete community microblogs from the News repository