Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property determines how many key store backups can be retained, with a default limit of three backups. |
| What area does it affect? |
MID Server backup management |
| What does the default mean? |
No default value is stated in the ServiceNow documentation. |
| When should you review it? |
Review this property when configuring backup strategies for key stores. |
Property record
Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.
| Property name |
mid.keystore.max_backups |
| Type |
Not stated |
| Application |
Not stated |
| Default value |
Not stated |
| Description |
Not stated |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... names, product names, and logos may be trademarks of the respective companies with which they are associated. 2316 The key store backups can be modified with the MID Server properties mid.keystore.max_backups, mid.keystore.max_live_backups, and mid.keystore.backup_overwrite_timespan. See MID Server properties for more information. Procedure 1. Stop MID Server. 2. Navigate to the security_backup and view the keystore_backup_audit_trail.log to choose which backup to restore. ...
More in mid
Other properties in the same namespace.
mid.hla.itom_gateway_streaming.enabled
This property enables MID Servers to stream log data directly to the ITOM Gateway, facilitating real-time log
mid.inactivity.timeout.enabled
It enables governance checks on MID Servers by enforcing an inactivity timeout, reducing the risk of unauthori
mid.install_server.base_uri
This property sets the Base URI used by the mid server to download packages, allowing for customization of the
mid.jdbc.datastream.max.record.size
This property limits the size of records processed by the MID Server's JDBC data stream, with a default maximu
mid.local.run_on_startup
This property configures the local MID server to run automatically at system startup, facilitating continuous
mid.log.command_audit.enable
This property enables logging of commands run by the MID Server, capturing details such as command names, hash
mid.log.level
It configures the logging level of the MID Server, with options including debug, info, warn, and error, affect
mid.max_down_days
It defines the threshold in days for how long a MID Server can remain down before it is treated as inactive fo
All 59 properties in mid →