LiveNX BACKUP GUIDE. LiveAction, Inc. LIVEACTION, INC.

Transcription

1 LIVEACTION, INC. LiveNX BACKUP GUIDE LiveAction, Inc Copyright WEST BAYSHORE ROAD LiveAction, Inc. All rights reserved. LiveAction, LiveNX, LiveUX, the LiveAction Logo and PALO LiveAction ALTO, CA Software are trademarks of LiveAction, Inc. Information subject to change without notice.

2 1. LiveNX Backup Guide This guide will show how to back up a LiveNX deployment in several ways. The importance of backup is critical to monitoring tools. This helps ensure that users have a way for disaster recovery with minimal or no loss of data, depending on the situation. Always test this in a lab environment before putting these steps in place for production. This will minimize issues and a secure plan can be put in place to ensure maximum efficiency. Backup Methods: Snapshot of VM deployment Backup of LiveNX configuration only Backup of LiveNX configuration and storage Snapshot of VM Deployment This is one of the easier methods of backing up LiveNX, the only tradeoff is that the snapshot will be controlled outside of the LiveNX deployment and requires knowledge of VMware ESXi. Caveat: make sure that the user that will be performing the snapshot has enough privileges to create the vm snapshot. 1. Log into ESXi and locate your LiveNX deployment 2. Right Click the Virtual Machine 3. Click Snapshot > Take Snapshot 2 LiveNX

3 4. In the pop-up: Type in the name for the new snapshot 5. Type a description for the new snapshot a. Recommends: Adding a date + Time description b. Example: Apr 1 st, 2016 / 15:34 / Before 5.4 Upgrade 6. Check Box > Snapshot the virtual Machine s memory 7. Click OK. This will quickly snapshot your VM and backup the current state. It s recommended that a consistent schedule be utilized when backing up so that recovery may not result in a larger loss of data. The more frequent the snapshot, the more data can be retained. If the more infrequent the snapshots, the more data loss can incur when performing the disaster recovery. Find a happy medium if storage becomes a problem. if you delete the VM deployment, you will lose all your snapshots. Recovering from VM snapshot With the snapshots being created on Vcenter, this recovery may be the fastest way to retain as much data as possible without much effort. 1. Log into ESXi and locate your LiveNX deployment 2. Right Click the Virtual Machine 3. Click Snapshot > Snapshot Manager 3 LiveNX

4 4. Select the snapshot you will revert to 5. Click > Go To 6. Click > Yes on the pop-up The VM snapshot will begin to apply and the machine will go back to the last state in the snapshot. Backing up LiveNX Configuration Only There are times where LiveNX s historical data is not needed and can be dumped. Having a consistent backup of the configuration is what is mainly necessary to get things up and running again. Having the convenience of just backing up the LiveNX configuration is great Recommend to perform this during off hours due to users being disconnected when configuration is being performed. 1. Log into the LiveNX LAN Management Console 2. Click > Manage 3. Click > Export Configuration 4 LiveNX

5 4. Click > Yes [Warning about logging off users] a. Create a password to protect the file 5. Click > Browse 6. Select the location of where to save the configuration file 7. Save the file 5 LiveNX

6 Backing up LiveNX Data store LiveNX and its nodes have their own data store. If the historical data is useful to keep, there are options to save them at a remote location if storage becomes an issue. Because LiveNX Data store truncates oldest date out when the disk fills up, it s wise to backup and maybe even sync the data across to a remote repository. For both nodes and server, it s best to make sure that both are backed up separately. Directories that are associated with Data Store on both nodes and LiveNX Server: Path and Folders Windows o Server 6 LiveNX

7 o Node Linux o Server 7 LiveNX

8 o Node All-In-One o Server 8 LiveNX

9 o Snmpstore Node The directories store all the historical data associated with the discovered devices in the infrastructure. Extract the backup and configuration to a remote backup The location of the backup and configuration is local to the VM deployment, the best thing to perform next is to move the file to a remote location in order to ensure that you can pull the backup at any time and load it into another LiveNX instance. The basic guideline is to be able to relocate the config to a secure remote repository for reference in the future. Options: NFS mount and Rsync periodically Rsync the files to a remote repository without NFS mount Manually copy into a remote repository 9 LiveNX