#!/bin/bash #============================================================================== # Copyright and license info is available in the LICENSE file included with # the Server Deployment Package (SDP), and also available online: # https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/LICENSE #------------------------------------------------------------------------------ # Intended to be run on a replica machine to sync replica from its corresponding master # Like sync_replica.sh but for use in a regular crontab export SDP_INSTANCE=${SDP_INSTANCE:-Undefined} export SDP_INSTANCE=${1:-$SDP_INSTANCE} if [[ $SDP_INSTANCE == Undefined ]]; then echo "Instance parameter not supplied." echo "You must supply the Perforce instance as a parameter to this script." exit 1 fi . /p4/common/bin/p4_vars $SDP_INSTANCE . /p4/common/bin/backup_functions.sh LOGFILE=$LOGS/sync_replica.log ######### Start of Script ########## check_vars set_vars rotate_last_run_logs log "Starting weekly_sync_replica.sh" if [[ "${P4REPLICA}" == "FALSE" ]]; then die "Error: recreate_db_sync_replica can only be run a read only or forwarding replica." fi check_uid $P4CBIN/p4login -p $P4MASTERPORT MASTERJOURNALNUM=$($P4BIN -u $P4USER -p ${P4MASTERPORT} counter journal) if [[ "$MASTERJOURNALNUM" == "" ]]; then die "Error: Couldn't get journal number from master. Aborting." fi # We set JOURNALNUM to one less than the master since we are not truncating the journal # and replay_journals_to_offline_db assumes that truncate_journal has been run. JOURNALNUM=$(($MASTERJOURNALNUM-1)) # You must set up a public keypair using "ssh-keygen -t rsa" in order for this to work. # You need to paste your CLIENT ~/.ssh/id_rsa.pub contents into the REMOTE ~/ssh/authorized_keys file. if [[ "$SHAREDDATA" == "FALSE" ]]; then rsync -avz --delete ${OSUSER}@${P4MASTER}:$CHECKPOINTS/ $CHECKPOINTS > $LOGFILE 2>&1 rsync_exit_code=$? if [[ $rsync_exit_code -ne 0 ]]; then die "Error: Failed to pull $CHECKPOINTS from host $P4MASTER. The rsync exit code was: $rsync_exit_code. Aborting." fi fi recreate_offline_db_files get_offline_journal_num replay_journals_to_offline_db /p4/${SDP_INSTANCE}/bin/p4d_${SDP_INSTANCE}_init stop >> $LOGFILE 2>&1 exit_code=$? if [[ $exit_code -ne 0 ]]; then die "Error: Server failed to shut down. Aborting." fi log "Server should be down now." log "Moving offline db into root." switch_db_files log "Remove replication files to reset replication to beginning of current master journal." rm -f ${OFFLINE_DB}/state* >> $LOGFILE 2>&1 rm -f ${OFFLINE_DB}/rdb.lbr >> $LOGFILE 2>&1 rm -f ${P4ROOT}/state* >> $LOGFILE 2>&1 rm -f ${P4ROOT}/rdb.lbr >> $LOGFILE 2>&1 rm -f ${P4HOME}/logs/journal >> $LOGFILE 2>&1 rm -f ${P4HOME}/journals.rep/* >> $LOGFILE 2>&1 ${P4HOME}/bin/p4d_${SDP_INSTANCE}_init start >> $LOGFILE 2>&1 $P4CBIN/p4login -service log "Server should be back up now." $P4BIN pull -lj >> $LOGFILE rm -f ${OFFLINE_DB}/save/db.* >> $LOGFILE 2>&1 rm -f ${P4ROOT}/save/db.* >> $LOGFILE 2>&1 recreate_offline_db_files get_offline_journal_num replay_journals_to_offline_db check_disk_space remove_old_logs export CHECKPOINTS=${P4HOME}/journals.rep remove_old_checkpoints_and_journals $P4BIN pull -lj >> $LOGFILE if [[ $? -ne 0 ]]; then die "Error: Replica not responding to pull. Check $P4SERVER replication." fi log "End $P4SERVER weekly sync replica log." mail_log_file "$HOSTNAME $P4SERVER Weekly sync replica log."
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#8 | 25051 | C. Thomas Tyler |
Released SDP 2018.1.23583.p2 (2019/01/23). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev', with selective removal of work-in-progress files. |
||
#7 | 23331 | C. Thomas Tyler |
Released SDP 2017.4.23329 (2017/12/05). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
#6 | 21723 | C. Thomas Tyler |
Released SDP 2017.1.21720 (2017/02/17). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
#5 | 21193 | Russell C. Jackson (Rusty) | Update main from dev. | ||
#4 | 20974 | C. Thomas Tyler |
Released SDP 2016.2.20972 (2016/11/01). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
#3 | 20767 | C. Thomas Tyler |
Released SDP 2016.2.20755 (2016/09/29). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
#2 | 20353 | C. Thomas Tyler |
Released SDP 2016.1.20348. Copy Up using 'p4 copy -r -b perforce_software-sdp-dev', with selective removal of changes related to work-in-progress changes. |
||
#1 | 19694 | C. Thomas Tyler |
Released SDP/MultiArch/2016.1/19661 (2016/06/08). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/bin/recreate_db_sync_replica.sh | |||||
#1 | 19466 | Russell C. Jackson (Rusty) |
Renamed weekly_sync_replica.sh to recreate_db_sync_replica to be consistent with early rename of weekly_checkpoint.sh. Changed crontab.replica to only run recreate_db_sync_replica when the master runs recreate_db_checkpoint.sh Use the switch_db files function in the sync_replica script and added additional logging and error checking. #review Sorry Tom, I was wrong about being done. I just found this stuff while reviewing my prior changes to recreate_db_checkpoint.sh and backup_functions.sh |
||
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/bin/weekly_sync_replica.sh | |||||
#12 | 18587 | Russell C. Jackson (Rusty) |
Reworked the log rotation stuff in backup_functions.sh to make it cleaner and handle the new log from recreate_offline_db.sh. Modified recreate_offline_db.sh to add comments about a bad checkpoint. Also made it create its own log file since it isn't doing a checkpoint. Removed the log rotation for the same reason. Moved the LOGFILE setting out to all of scripts to make it more obvious for future scripts that you need to set that variable in your script so that it doesn't just default to checkpoint.log. Moved the functions in weekly_backup.sh and recreate_offline_db.sh into backup_functions.sh where they belong for consistency. Modified backup_functions.sh to use a consistent naming convention for all the rotated log files rather than checkpoint.log being unique. Replaced all back ticks with the newer bash $() method. Removed all of the line wrapping since I am pretty sure that none of us are working on an 80 character terminal these days and it is easier to read this way. |
||
#11 | 16335 | C. Thomas Tyler |
Routine Merge Down to dev from main using: p4 merge -b perforce_software-sdp-dev |
||
#10 | 16029 | C. Thomas Tyler |
Routine merge to dev from main using: p4 merge -b perforce_software-sdp-dev |
||
#9 | 15778 | C. Thomas Tyler | Routine Merge Down to dev from main. | ||
#8 | 15701 | C. Thomas Tyler | Routine merge down using 'p4 merge -b perforce_software-sdp-dev'. | ||
#7 | 15374 | adrian_waters |
- Ensure backup scripts are run as the OSUSER (to prevent accidental running as root); - in scripts where LOGFILE value is changed from the 'checkpoint.log' set by set_vars, ensure the new assignment is before check_dirs is called, otherwise errors could be written to the 'wrong' log - in 'die()' - detect if running from terminal & also send output to stderr |
||
#6 | 13906 | C. Thomas Tyler |
Normalized P4INSTANCE to SDP_INSTANCE to get Unix/Windows implementations in sync. Reasons: 1. Things that interact with SDP in both Unix and Windows environments shoudn't have to account for this obscure SDP difference between Unix and Windows. (I came across this doing CBD work). 2. The Windows and Unix scripts have different variable names for defining the same concept, the SDP instance. Unix uses P4INSTANCE, while Windows uses SDP_INSTANCE. 3. This instance tag, a data set identifier, is an SDP concept. I prefer the SDP_INSTANCE name over P4INSTANCE, so I prpose to normalize to SDP_INSTANCE. 4. The P4INSTANCE name makes it look like a setting that might be recognized by the p4d itself, which it is not. (There are other such things such as P4SERVER that could perhaps be renamed as a separate task; but I'm not sure we want to totally disallow the P4 prefix for variable names. It looks too right to be wrong in same cases, like P4BIN and P4DBIN. That's a discussion for another day, outside the scope of this task). Meanwhile: * Fixed a bug in the Windows 2013.3 upgrade script that was referencing undefined P4INSTANCE, as the Windows environment defined only SDP_INSTANCE. * Had P4INSTANCE been removed completely, this change would likely cause trouble for users doing updates for existing SDP installations. So, though it involves slight technical debt, I opted to keep a redundant definition of P4INSTANCE in p4_vars.template, with comments indicating SDP_INSTANCE should be used in favor of P4INSTANCE, with a warning that P4INSTANCE may go away in a future release. This should avoid unnecessary upgrade pain. * In mkdirs.sh, the varialbe name was INSTANCE rather than SDP_INSTANCE. I changed that as well. That required manual change rather than sub/replace to avoid corrupting other similar varialbe names (e.g. MASTERINSTANCE). This is a trivial change technically (a substitute/replace, plus tweaks in p4_vars.template), but impacts many files. |
||
#5 | 13904 | C. Thomas Tyler | Routine merge down to dev from main. | ||
#4 | 12169 | Russell C. Jackson (Rusty) |
Updated copyright date to 2015 Updated shell scripts to require an instance parameter to eliminate the need for calling p4master_run. Python and Perl still need it since you have to set the environment for them to run in. Incorporated comments from reviewers. Left the . instead of source as that seems more common in the field and has the same functionality. |
||
#3 | 12107 | C. Thomas Tyler |
Routine merge down from 'main' to 'dev', resolved with 'p4 resolve -as'. |
||
#2 | 12028 | C. Thomas Tyler | Refreshed SDP dev branch, merging down from main. | ||
#1 | 10638 | C. Thomas Tyler | Populate perforce_software-sdp-dev. | ||
//guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/weekly_sync_replica.sh | |||||
#1 | 10148 | C. Thomas Tyler | Promoted the Perforce Server Deployment Package to The Workshop. |