{"id":30583355,"url":"https://github.com/synergex/files_for_synbackup_for_unix","last_synced_at":"2025-08-29T08:33:45.319Z","repository":{"id":149574572,"uuid":"397318548","full_name":"Synergex/Files_for_synbackup_for_UNIX","owner":"Synergex","description":"Using synbackup on Unix or Linux","archived":false,"fork":false,"pushed_at":"2022-07-25T17:59:20.000Z","size":25,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":5,"default_branch":"main","last_synced_at":"2024-03-26T20:17:16.408Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Synergex.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.md","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null}},"created_at":"2021-08-17T16:12:32.000Z","updated_at":"2022-08-04T15:52:10.000Z","dependencies_parsed_at":null,"dependency_job_id":"ef4480b2-d77a-4703-9f51-ae4d23f30ddf","html_url":"https://github.com/Synergex/Files_for_synbackup_for_UNIX","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/Synergex/Files_for_synbackup_for_UNIX","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Synergex%2FFiles_for_synbackup_for_UNIX","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Synergex%2FFiles_for_synbackup_for_UNIX/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Synergex%2FFiles_for_synbackup_for_UNIX/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Synergex%2FFiles_for_synbackup_for_UNIX/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Synergex","download_url":"https://codeload.github.com/Synergex/Files_for_synbackup_for_UNIX/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Synergex%2FFiles_for_synbackup_for_UNIX/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":272655952,"owners_count":24971219,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-08-29T02:00:10.610Z","response_time":87,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-08-29T08:33:44.577Z","updated_at":"2025-08-29T08:33:45.313Z","avatar_url":"https://github.com/Synergex.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Files_for_synbackup_for_UNIX\u003cbr /\u003e\n**Created Date:** 3/14/2018\u003cbr /\u003e\n**Last Updated:** 3/14/2018\u003cbr /\u003e\n**Description:** See README.md for complete details. This contains the files corresponding to KB #2357 which are used as an example of using the synbackup utility.\u003cbr /\u003e\n**Platforms:** Unix\u003cbr /\u003e\n**Products:** Synergy DBL; Synergy DBMS\u003cbr /\u003e\n**Minimum Version:** 10.1.1\u003cbr /\u003e\n**Author:** Galen Carpenter\n\u003chr\u003e\n\n**Additional Information:**\n\t\t\tUsing synbackup on Unix or Linux\n\nWhen backing up Synergy databases, problems can arise if a file is in the\nprocess of being updated when a backup occurs, which may result in a corrupted\nfile.  To help solve this problem, you can use the Synergy/DE synbackup utility\nto freeze the updating of the files, allowing them to be backed up without\ncorruption.  After the backup is completed, the synbackup utility can thaw\nthe I/O and allow updates to the files again.  This freeze/thaw process is\ncalled quiesce.\n\nThis CodeExchange entry contains several script files to help you automate the\nuse of synbackup on UNIX.  These files should work with a variety of backup\napplications.\n\n\tstop_APP.sh and start_APP.sh.  The *_APP scripts do the actual freezing\n\tand thawing of the Synergy I/O by calling the synbackup utility.\n\tThe *_APP.sh scripts need to be modified to specify the location of\n\tthe setsde script in your Synergy distribution directory.  They\n\tgenerate log files (stop_APP.log and start_APP.log) that show the time\n\tthey were run and the output from the synbackup command.\n\n\tsynbackup (or K30synbackup and S30synbackup for AIX).  These scripts\n\texecute the synbackup -c command to create the shared memory that\n\tinforms all Synergy programs that I/O is enabled or disabled.  Look at\n\tthe script(s) to verify that DBLDIR is set correctly and the path for\n\tsynbackup is correct.  If you have multiple installations of Synergy on\n\tthe machine, see \"If you have multiple installations of Synergy\" below.\n\tThe synbackup (or S30synbackup) script should be run automatically\n\tevery time the system starts up.  (K30synbackup is run on shutdown to\n\tdo synbackup -d.)  See \"Running the synbackup script at startup\" below\n\tfor instructions on the various platforms.\n\nThe other script file you need to be concerned with is setsde, which is\nincluded in your Synergy distribution.  To initialize the use of the synbackup\nutility, uncomment the setting of the SYNBACKUP environment variable in setsde.\n(SYNBACKUP must be set before the synbackup -c command is run.)\n\nHow it works:\n\nWhen the system is booted, the synbackup (or S30synbackup on AIX) script is\nrun to set the SYNBACKUP environment variable \"on\" and run the synbackup -c\ncommand, which creates the shared memory.\n\nWhen a backup is requested, the backup software calls stop_APP.sh, which runs\nsynbackup -b and then sleeps 10 seconds (to allow the program time to finish\nup what it is doing).  Then stop_APP calls synbackup -s to freeze the I/O.\n\nWhen the backup finished, the backup software calls start_APP.sh to run\nsynbackup -x to unfreeze the I/O.\n\nIf you have multiple installations of Synergy:\n\nWhen the SYNBACKUP environment variable is set, the runtime looks for the file\nDBLDIR:synbackup.cfg, which is created by the synbackup -c command.  If there\nare multiple installations of Synergy on the system, each will have DBLDIR set\nto its own installation area.  To have all of the installations use the same\nshared memory, you need to create a symbolic link to synbackup.cfg in the\nDBLDIR directory of each additional installation location.  For example:\n\"ln -s /usr2/test_1033_32/synergyde/dbl/synbackup.cfg /usr2/test_1033d_32/synergyde/dbl/synbackup.cfg\".\nBe sure to enable the SYNBACKUP environment variable in the setsde script for\neach synergy installation area.\n\nRunning the synbackup script at startup:\n\n\tUbuntu: Copy the synbackup script file to /etc/initd and make sure it\n\tis owned by root with permissions of 777.  Then do\n\t\"/usr/lib/insserv/insserv synbackup\" to have the system create the\n\tappropriate links to the /etc/rc.d/rcN.d files.\n\n\tRedhat: Copy the synbackup script file to /etc/initd and make sure it\n\tis owned by root with permissions of 777.  Then do\n\t\"chkconfig --add synbackup\" (that is, dash dash add) and\n\t\"chkconfig --level 2345 synbackup on\" (that is, dash dash level).\n\tThe chkconfig command may be located in /sbin.\n\n\tAIX: Copy the K30synbackup and S30synbackup scripts to the\n\t/etc/rc.d/rc2.d directory and modify them for the location of your\n\tSynergy installation.  The S30synbackup script is for startup and the\n\tK30synbackup script is for shutdown.  Both have the same contents.  Be\n\tsure they are owned by root/system with file permissions of 640.\n\nBackup software specific instructions:\n\nThese three commonly used backup applications can be modified to work with the\nstop_APP.sh and start_APP.sh scripts.\n\n\tSemantec NetBackup:\n\tNetBackup looks for two files, bpstart_notify and bpend_notify, in the\n\t/usr/openv/netbackup/bin directory.  If it finds them, it executes\n\tbpstart_notify before the backup starts and bpend_notify after the\n\tbackup has completed.  The CodeExchange zip file includes versions of\n\tthese scripts that we downloaded from\n\thttps://vox.veritas.com/t5/NetBackup/Pre-Post-script-commands-for-backup/td-p/762844.\n\tThe bpstart_notify script calls stop_APP.sh and the bpend_notify scipt\n\tcalls start_APP.sh.  Set APP_SCRIPT_LOCATION in the bp*_notify scripts\n\tto point to the location of start_APP.sh and stop_APP.sh.  (Because\n\tsynbackup must be run as root, the *_APP scripts are started directly\n\tby the bash command rather than going through another account.)\n\tDOLOGGING is set to 1 in the scripts and should be turned off once you\n\tare done testing and everything is running successfully.  We recommend\n\tyou read through these scripts to see what else they do.\n\n\tVeeam Backup \u0026 Replication:\n\tIn the \"Processing Settings\", on the \"Scripts\" tab for\n\t\"Guest Processing\", the location and name of the Pre-freeze and\n\tPost-thaw scripts need to be filled in with the location of the\n\tstop_APP.sh and start_APP.sh scripts, respectively.\n\n\tMicrolite's BackupEdge:\n\tIn the \"Backup Domain\" under \"Advanced Properties\" there is a place to\n\tspecify a \"Start/Stop Script\".  The default is\n\t/usr/lib/edge/bin/edge.bscript, which is run before and after the\n\tbackup is performed as well as before and after verification of the\n\tbackup.  Microlite does not recommend modifying this script.  At the\n\tstart of a backup, edge.bscript runs the /etc/edge.start script and at\n\tthe conclusion of a successful backup and verify, it runs the\n\t/etc/edge.passed script.  If the backup or verify fails, the\n\t/etc/edge.failed script is run.  These three scripts are user\n\tmodifiable.  You can modify /etc/edge.start to run the stop_APP.sh\n\tscript, and then modify /etc/edge.passed and /etc/edge.failed to run\n\tthe start_APP.sh script.  (New releases of BackupEdge replace these\n\tthree scripts and rename the existing files by appending 00 to the\n\tname, so you won't lose your changes.)\n\nIf you are using other backup software you may still be able to use the *_APP\nscripts.  Most backup software has a way to specify freezing and thawing of I/O.\nSearch your backup software's documentation for \"quiesce\" or \"freeze\" or \"thaw\"\nto find out how it is specified.  Then configure it to call the stop_APP.sh\nscript to freeze the file writes and the start_APP.sh script to thaw the file\nwrites.\n\n(This information is included in KB article 2357.)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsynergex%2Ffiles_for_synbackup_for_unix","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsynergex%2Ffiles_for_synbackup_for_unix","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsynergex%2Ffiles_for_synbackup_for_unix/lists"}