Veritas Backup Installation Manual

[Charise Zelnick]

Forthose interested: I've successfully managed to configure Konnected to read the status of the alarm using an Texecom Veritas R8+. We can use the Communicator terminals for this purpose, when setup the status of the alarm is read regardless of how it has been set.

You will need to open the manual at page 9, we are concerned with section '12: Communicator Interface'. Terminal 4, labelled "Set/Unset", is used to report whether the alarm is set/unset rather than arm/disarm it, this is the terminal we will connect to Konnected to read this status.

3. Advance through the setup and configure this binary sensor as something appropriate, I use 'Lock', and give it a name (you may need to come back here if you need to invert the state of this sensor).

Next you will need to configure your platform to synchronise the relay with the state of the alarm using a custom button, you wont be able to use the switch created by the Konnected integration as this just toggles the relay irrespective of the state of the alarm. This means that you could easily toggle the alarm off accidentally if you've set the alarm using a panel but lets say you have a backup automation to arm the alarm when you leave home in case you forgot.

For a quick backup of only the monitoring configuration (for example, groups, devices, sensors, users, maps, reports), back up the file PRTG Configuration.dat in the PRTG data directory.

It is also a good idea to back up older configurations in the folder \Configuration Auto-Backups. These files are not kept open while the PRTG core server is running and can be backed up at any time.

To get a complete and consistent backup of the databases (for example, log database, monitoring database, Toplist database, ticket database), stop the PRTG core server while running the actual backup process.

Note: Probes continue to monitor their sensors for a few minutes and deliver monitoring results to the PRTG core server as soon as it is back online. However, alerts are not available during this period.

Once the configurations have been saved (groups, devices, sensors...), can they be copied to a second device with another installation of PRTG so that they can be imported from the second PRTG Core? (I am not interested in Clustering)

Hello all,I'm working on a concept for a active / passive cluter for a PRTG environment with >7000 sensors.I'm copying all Data from the Database folder (excluding Report PDFs, Logs and Autobackup configurations) and everything important from PRTG DIR (webroot, snmplibs, lookups, notifications, devicetemplates and Custom Sensors).For an automated failover I need to move the license to the 2nd Standby Core Server and tell the remote probes to connect to another Core Server. Is there a way to do this via script?

Hi Sebastian,thanks for your reply. Unfortunatelly the cluster is not favored by the customer and we estimate a sensor count of >8000.So there is no way to update the core-server entry via API on the remote probes?

About PRTG Configuration.dat in the data folder \Configuration Auto-Backups. If i use cluster mode with two nodes every node has it's own PRTG Configuration.dat file? Or Master Node has backup for both nodes? If i need to restore this config to cluster if it's fail, first i need to restore both nodes cfg and then make a cluster, or this backup has cluster info inside?

Hello Vasiliy,

The master node is the primary cluster node. Every setting will be changed within the configuration file of the master node and the configuration will be automatically synchronized with the failover nodes.

To restore a failover node please set-up a new client that should be the future failover node and proceed with the regular step by step guide to whoop this machine into the PRTG cluster. The configuration file will be automatically pushed to it.

If you still own the /Monitoring Database directory of the old failover node, you can also restore it on the new failover node to restore the historic data.

Best regards,

Sebastian

Hi Vasiliy,

It does not really matter where you stop the services. You can either stop the services from the Service Start/Stop tab within the PRTG Administration Tool on the PRTG Core Server or you can stop them via Windows Services MMC.

The second option would allow you to stop the services using a script, but this is not mandatory.

Best regards,

Sebastian

Good, but what if i use "Veritas Backup exec" and make Full Backup of all Master Node Server include System State and all other server content, need i stop this service? As far as i understand Veritas can backup all content without service interruption. Can be some trouble with server restore after this?

Hi Mohamed,

You can't use any backup data from the Core Server on a Remote Probe, since the configuration is only cached on the Remote Probes and saved on the Core Server. What do you want to do with these backup data?

I know you can copy the configuration.dat file but why hasn't PRTG added a backup and restore command in the interface? This question dates back to 2010. We shouldn't have to come to the forum to figure out how to backup the system. Also, copying the .dat file only works for the exact same version, I followed the directions and it didn't work and I later realized that the version I reinstalled was different then the version I previously had. The online notes should indicate that you should backup the installer along with the .dat file so they match. I only figured this out after re-entering, re-mapping, and re-layout all my sensors. PC's crash, or we move to larger systems, etc.. Considering you have to stop PRTG services to copy the .dat file it makes auto backups a little more difficult. Why not just add a backup scheduler in PRTG to save the configuration to a destination and a restore option that understands previous version formats? From what I read some people have very large systems, a crash could be a disaster.

Sorry for the delayed response on this. PRTG does a backup before every update so you can downgrade with the least amount of effort. Could you perhaps post the issue you've had in more detail so we can see where our process is not really applicable? That'd be great :)

Remember that a GUI for it (apart from creating a config snapshot in the admin tool) is somewhat unfeasible given that PRTG, in 90% of the cases where a configuration restoration is required, won't start properly anymore, hence the GUI would be kind of inaccessible :/

Data managed by Tableau Server: consists of the Tableau PostgreSQL database or repository, and File Store, which contains workbook and user metadata, data extract files, and site configuration data. When you use TSM to create a backup, all of this data is saved in a single file with a .tsbak extension. This data is backed up with the tsm maintenance backup command.

You can only restore from a backup that has the same type of identity store as the running server.For example, a backup from a server using local authentication can be restored to a Tableau Server initialized with local authentication, but a backup from a server using Active Directory authentication cannot be restored to a server initialized with local authentication.

Configuration and Topology data: includes most of the server configuration information required to fully recover a server. SMTP, alerting, some authentication assets, are all examples of configuration data that are exportable for backup. Topology data defines how your Tableau Server processes are configured in both single-server and multiple node deployments. Configuration and topology data is backed up with the tsm settings export command.

Some configuration data is not included in the tsm settings export command and must therefore be documented and restored manually. The following configuration data is excluded from the tsm settings export operation. Your backup maintenance process should include documenting the following Tableau Server configuration data:

System user accounts. Tableau Server setup uses an unprivileged user account, NetworkService. This account is used to access Tableau Server resources. If you have not changed this account, then you do not need to document it.

Coordination Service deployment configuration. If you are running a multinode cluster, document which nodes are running the Coordination Services process. To view process configuration on your nodes, run tsm topology list-nodes -v.

Customization settings. If your organization uses custom header or sign-in logos for Tableau Server web pages, you should include a copy of those assets with your back up portfolio. See tsm customize.

Most authentication assets. While the locations for files may be included in an exported settings.json file, most certificate files, key files, keytab files or other authentication-related assets are not backed up by TSM. Verify that any of these assets you are trying to move won't need to be recreated.

3a8082e126