PM - Example of Data Repository database restore using restore points

book

Article ID: 223312

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

Example of Data Repository database restore using restore points (single node)

Environment

DX Performance Management 20.2.x

Resolution

1.- Navigate to “Performance -> Operations Displays -> Interface Trends” in Dx NetOps Portal and take a screenshot for the last 7 days to verify later on whether the restore has been performed successfully: 

Note there is data the 6th of September

2.- Stop the DCs services:
[[email protected] ~]# service dcmd stop
Redirecting to /bin/systemctl stop dcmd.service

[[email protected] ~]# service dcmd stop
Redirecting to /bin/systemctl stop dcmd.service

3.- Stop the DA services:
[[email protected] ~]# service dadaemon stop
Redirecting to /bin/systemctl stop dadaemon.service

4.- Log in to the DR server as the database administrator user (not as the root user) and run below command:
[[email protected] ~]# su dradmin
[[email protected] root]$

[[email protected] ~]# /opt/vertica/bin/adminTools

 


5.- Stop the Database (option 4 in the Menu):

 

6.- Exit from AdminTools:

 


7.- Check the available DR backups:
[[email protected] roo]$ /opt/vertica/bin/vbr.py --task listbackup --config-file /opt/vertica/config/backup_restore_full_local_TEST2.ini
backup                                                    backup_type   epoch       objects   i_p   e_p   nodes(hosts)                                       version     filesystem_type
backup_snapshot_20210906_060004   full                   5603494                                  v_drdata_node0001(10.74.161.134)   v9.1.1-5   [Linux]
backup_snapshot_20210905_060004   full                   5567781                                  v_drdata_node0001(10.74.161.134)   v9.1.1-5   [Linux]
backup_snapshot_20210904_060004   full                   5532452                                  v_drdata_node0001(10.74.161.134)   v9.1.1-5   [Linux]

8.- Restore to the desired restore point by running below command (eg: 4th Sep backup):
/opt/vertica/bin/vbr.py --task restore --config-file <configuration_directory_path_filename>  --archive <archive_name> 

[[email protected] root]$ /opt/vertica/bin/vbr.py --task restore --config-file /opt/vertica/config/backup_restore_full_local_TEST2.ini  --archive 20210904_060004
Starting full restore of database drdata.
Participating nodes: v_drdata_node0001.
Restoring from restore point: backup_snapshot_20210904_060004
Determining what data to restore from backup.
[==================================================] 100%
Approximate bytes to copy: 588956901 of 2302778891 total.
Syncing data from backup to cluster nodes.
[==================================================] 100%
Restoring catalog.
Restore complete!

 

9.- Restart the DR via AdminTools:


 


10.- Exit from AdminTools:


 

11.- Start the DA services:
[[email protected] ~]# service dadaemon start
Redirecting to /bin/systemctl start dadaemon.service

12.- Start the DCs services:
[[email protected] ~]# service dcmd stop
Redirecting to /bin/systemctl start dcmd.service

[[email protected] ~]# service dcmd stop
Redirecting to /bin/systemctl start dcmd.service

13.- Verify the backup has been performed successfully by navigating to “Performance -> Operations Displays -> Interface Trends” in Dx NetOps Portal and checking the data for the last 7 days.

 

Note there is data until the 4th of September

 

Additional Information

Restore the Data Repository
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/performance-management/20-2/administrating/data-repository-administration/restore-data-repository.html

Attachments