About Data Purging in Vocera Platform

In the Vocera Platform, data purging occurs when transactional data, such as alarms, assignments, and messages, are removed from the system after they have been saved by the automatic daily backup. Purge conditions are included in the EMDAN solution.

By default, this version of the Vocera Platform automatically enables local daily backup and implements data purging after 90 days. Data purging improves system performance, as daily backups become smaller and database queries are responded to more quickly. Data purging is automatically performed at a time when your system is not heavily loaded to ensure it does not impact system performance.

If necessary, you can configure your system to purge data after a time period other than 90 days. However, less than 90 days is not recommended, as mobile conversations may still be active.

You can choose to disable data purging, but system performance will then degrade over time as your server’s disk space begins to fill up with transactional data. New virtual or physical machines may be required when the active environment can no longer be used, which requires additional effort to implement.

For troubleshooting when data purging is implemented, you can use Vocera Analytics. You can also access the audit log page, which retains audit data for seven days, or access data using the admin workflow pages.

If you require data retention for longer than 90 days (or the length of time that you have specified for data purging), you can configure your daily backup to be sent to an external location using FTP, SFTP, or SMB. Maintaining this external backup location then becomes your responsibility.