Based on my understanding from the user’s guide. The attribute above will not survive db backup and restore.
Is there a workaround? Thanks.
From User’s Guide:
–cdb-backup File Save a snapshot of the CDB database into a GZipp:ed tar archive
file (given by the File argument). If the File argument is a relative
path, the file will be saved relative the ConfD daemon’s current working directory . Only configuration data stored in CDB is saved
(persistent CDB operational data is not). Note: if the database is
locked for writing, the command will fail.
This would create a XML file consisting only of operational data under /oper-data-root, but it would include also those that are handled by a callpoint, not just CDB-stored. Can you use such approach?
…
The confd_load command is a command line interface to the functions maapi_save_config(), maapi_load_config(), and maapi_load_config_stream() respectively.
…
From the confd_lib_maapi(3) man page under maapi_save_config():
…
The provided path indicates which part(s) of the configuration to save. By default it is interpreted as a keypath as for other MAAPI functions, and thus identifies the root of a subtree to save.
…
See the respective man page, the examples.confd/dp/generic_perf/src/maapi-save.c example, and source code for the confd_load tool src/confd/tools/confd_load.c for more details.