Configuring a backup schedule
For deployments with hundreds of connections or OAuth clients, or both, administrators can configure PingFederate to create configuration archives periodically.
Steps
-
Edit the
<pf_install>/pingfederate/server/default/data/config-store/org.sourceid.saml20.domain.mgmt.impl.DataArchiveBackup.xmlfile. See the following table for each property.Property Description ScheduledBackupEnabledWhen set to
true, PingFederate creates a configuration archive daily if configuration has changed since the creation of the last archive. This is true regardless of the backup method used.The default value is
false.BackupTimeThe local time at which PingFederate creates a configuration archive when the
ScheduledBackupEnabledproperty is set totrue.Ignored when the
ScheduledBackupEnabledis set tofalse.The default value is
00:00:00, which represents midnight.NumTriesWithIntegrityFailureUpon the creation of the scheduled configuration archive, if PingFederate detects a configuration change during the scheduled backup process, it retries immediately. The
NumTriesWithIntegrityFailureproperty indicates the maximum number of attempts.Ignored when the
ScheduledBackupEnabledis set tofalse.The default value is
3.BackupOnAdminLoginWhen set to
false, PingFederate does not create a configuration archive when an administrator signs on. Regardless of the value of this property, PingFederate always creates a configuration archive before an archive is imported.The default value is
true.MaxOldArchiveFilesThe number of older configuration archives that PingFederate keeps. When the limit is reached, the oldest file is removed.
The default value is
25files.The
ScheduledBackupEnabledandBackupOnAdminLoginproperties are not mutually exclusive. For example, if your deployment has 50 connections, you can enable both automatic and scheduled backup processes.If you have a clustered PingFederate environment, edit the
org.sourceid.saml20.domain.mgmt.impl.DataArchiveBackup.xmlfile on the console node.