There is anyway to backup the hub configurations (tunnnel,queue config,etc)In case there is any issue there is any restoration process handled here.
Well, there are a bunch of ways to go about this.
Probably the easiest is to copy the hub.cfg and the contents of the cert directory somewhere. Once set up, the config shouldn't change much. Or better yet, establish a configureation procedure so that rebuilding from scratch is a matter of following a process.
There are a handful of scripts that you could search for here to copy the config contents.
There's a controller callback to copy the contents of a file which you could use to get the certificates.
There's nothing native in the product (yet) to do this for you.
Thanks Garin!! Expected this from tool itself..
Does the Hub store the data of the robots for some time period or it will send the data frequently to primary hub.Confirm
Information about passive robots is stored in the hub.cfg file itself.
Information that the hub discovers about the robots connecting to it and security goes into the files with the .sds extension. There's also a security.cfg file but that's pulled down from a hub with a newer version when the hub starts up. This information is all discovered at runtime so there's really no need to restore it after a failure.
There is also the niscache directory that stores the device ids for items that are tracked/monitored/alarmed on but again, that is created at runtime and maintained so there's little to no value in saving that.
What I've actually found is that backups of nimsoft hubs beyond the .cfg file and certificates is more trouble than it's worth. Seems to be better to just do a clean install and reconfigure based on procedure.
One other option for backups is to drag the specific config to the archive and create a custom package. You can then add extra files to that (certs and whatnot for he hub for instance) so that you can recreate the configuration by dragging the package back to the newly rebuilt hub.
Whether the performance data of the probes are saved here ?Or it will transfer the data immediately to primary UIM
If by performance data you are referring to QoS then that is only stored on the hub long enough to transfer it off.Eventually QoS makes it to your central hub (via get and attach queues) where it is consumed by data_engine and written to your underlying database.
So in the best case situation, you re talking about only seconds worth of storage lost during a catastrophic loss and that would likely not happen conveniently immediately following whatever backup you have in place.
That data though accumulates in structures/files in the q directory under the hub directory.
Retrieving data ...