I removed my .cdb files A.cdb, O.cdb and C.cdb and just placed the xml backup(of current configurations) in the confd directory where aaa_init.xml is present. When I restarted the server back, I could not get the confd services loaded. Is there any possible way to get the confd loaded at the startup with xml configurations rather than .cdb files?
I mean to say how to make confd services to support xml based configuration instead of .cdb file configuration?
There is probably some some issue with your XML file. What does your confd.log / devel.log say?
From the ConfD UG:
/confdConfig/cdb/dbDir (string)
dbDir is the directory on disk which CDB use for its storage and any temporary files being used.
It is also the directory where CDB searches for initialization files.
/confdConfig/cdb/initPath
The initPath can contain any number of <dir> items, which should be directories. When CDB first starts it will first look in these directories for initialization files.
The directories will be searched in the order they are listed, lastly the dbDir is searched.
My logs indicate that I can’t put the XML in to CDB dbDir. Is there any procedure that makes the confd to support the XML configurations rather than CDB? confd_load is just one case of loading it explicitly.
Is there any configuration that can make it implicitly load the initial configuration of xml at the startup?
You can initialize CDB from an XML document that is read from the dBDir / initPath at startup. See ConfD 6.4 UG Chapter 5.8. “Loading initial data into CDB”.
I copied the xml backup in directory specified by initPath.
I restarted the server.
I got the database initialized with the backup.
It will work if I remove all the data or configurations i saved in database and then reboot.
During start up I am using confd_load: