Closed amhaats1 closed 3 months ago
Executing /udb_backup/cohesity/TESTcluster/reg_testing/restoreUDA.py \ -v "{{ clustername }}" \ -u "{{ generic_username }}" \ -d corp.mutualofomaha.com \ -pwd "{{ genericpassword }}" \ -s "{{ sourceserver}}""{{ instance }}"_"{{ dbname }}" \ -n "{{ dbname }}" \ -a 'logtarget-path=/log1/restore --new-log-path=/log1/{{ instance }}/{{ dbname }} --new-data-path="'/data1/{{ instance }}/{{ dbname }}/data1' dbpath on '/data1/{{ instance }}/{{ dbname }}/'"' \ -cc 16 \ -o \ -w
The restore is going back to the oldest INC or FULL backup versus the most recent
The notes say by leaving out the
I have made an update to the script. Please try the updated version: https://github.com/cohesity/community-automation-samples/tree/main/python/restoreUDA
Thank you, tested and it worked!!
Executing /udb_backup/cohesity/TESTcluster/reg_testing/restoreUDA.py \ -v "{{ clustername }}" \ -u "{{ generic_username }}" \ -d corp.mutualofomaha.com \ -pwd "{{ genericpassword }}" \ -s "{{ sourceserver}}""{{ instance }}"_"{{ dbname }}" \ -n "{{ dbname }}" \ -a 'logtarget-path=/log1/restore --new-log-path=/log1/{{ instance }}/{{ dbname }} --new-data-path="'/data1/{{ instance }}/{{ dbname }}/data1' dbpath on '/data1/{{ instance }}/{{ dbname }}/'"' \ -cc 16 \ -o \ -w
The restore is going back to the oldest INC or FULL backup versus the most recent
The notes say by leaving out the
By default (if both --latest and --logtime are omitted), the latest full/incremental snapshot time will be used for the restore.