- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
12-10-2018 10:24 PM
Hi, i am looking for some help regarding the configuration backup solution. Imaging someone changes platform setting, LDAP integration, or other types of configuration by mistake and he doesn't remember what the original value is. Is there a way to quickly roll back?
we use PAReplicate perform weekly backup and daily incremental backup, but i am not intend to restore safes. How do i just restore platforms, policies, etc. ?
12-10-2018 11:59 PM
@Phil Yu Yes. PARestore only restores to a new safe. But you can use the versioning feature of the safe instead.
Platform configuration is scattered in two safes:
All these files are saved along with previous versions, so you can revert by right-clicking a file, choosing Versions and selecting a previous version to go back to. You can increase retention period to keep old versions for longer in the properties of these two safes (History tab).
For the Vault, it keeps its configuration file in the System safe, where you can also increase History if needed. Something specific though is that it also keeps the last working version in the "PrivateArk\Server" directory: you have the DBParm.ini, but the last working version of this file, which allowed the vault to start successfully, is also stored as DBParm.ini.good. It's handy when you modify Vault's files, forget about it, and that some time later it is not starting up anymore. Of course you can debug the DBParm.file but having a failsafe .good file is pretty cool I think.
12-10-2018 10:53 PM
Well technically platforms and such configuration are files in safes as well. Depending on what you need PVWAConfig and PasswordManager are what you need.
12-10-2018 11:42 PM
wow~good to know~
i tried following:
PARestore vault.ini /RestoreSafe PVWAConfig /TargetSafe PVWAConfig /logonfromfile operator.cred
it error-ed out due to duplicate PVWAConfig safe names. Does it mean i have restore the config files in a different new safe, and copy the xml files back to to PVWAConfig manually?
12-10-2018 11:59 PM
@Phil Yu Yes. PARestore only restores to a new safe. But you can use the versioning feature of the safe instead.
Platform configuration is scattered in two safes:
All these files are saved along with previous versions, so you can revert by right-clicking a file, choosing Versions and selecting a previous version to go back to. You can increase retention period to keep old versions for longer in the properties of these two safes (History tab).
For the Vault, it keeps its configuration file in the System safe, where you can also increase History if needed. Something specific though is that it also keeps the last working version in the "PrivateArk\Server" directory: you have the DBParm.ini, but the last working version of this file, which allowed the vault to start successfully, is also stored as DBParm.ini.good. It's handy when you modify Vault's files, forget about it, and that some time later it is not starting up anymore. Of course you can debug the DBParm.file but having a failsafe .good file is pretty cool I think.
12-11-2018 12:25 AM
you are so brilliant. this is exactly what i am looking for.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

