![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Instead of taking full or partial system backups at regular intervals, use the following continuous backup process and journals to update the latest backup:The checkpoint process automatically submits spin01 and spin02 as required. When spin01 and spin02 are customized, they invoke spin03 when the spin limit is reached. The remaining steps are not started automatically and must be scheduled to run as required.For the full procedure to customize the spin files, refer to Chapter 5, Understanding Journal Processing.
2. Merge your journal accumulation files into a master accumulation file (spin03.bat in Windows, spin03 in Solaris).Spin03.bat in Windows and spin03 in Solaris are provided to perform this step. The output from this step is a master accumulation file called spinout.000. The next time the merge process runs, the spinout.000 file is merged with the existing journal accumulation files.
For Windows, the merge is automatically performed by spinctrl when the number of journal accumulation files reaches the value of the SPINLIM variable set in spin01 and spin02.
3. Merge your master accumulation file with your latest complete backup (sample process in spin05.bat in Windows, spin05 in Solaris).You can merge your master accumulation file with your latest complete backup as frequently as required. In most cases, we recommend a daily refresh of your complete backup. The spin05 batch file/script is provided as a sample to perform this merge. Alternatively, you can use the method described in Alternate Method to Refresh the Latest Backup.
4. Run the hrnbrptr (Batch Pointer Check) utility against any complete backup you produce to validate the integrity of all pages.Use the hrntlmrg (Journal Merge) utility to read in your journal accumulation file (or files) and your latest complete backup. The output is a new and complete backup that includes all page updates recorded in the journal accumulation files. For example, the following command creates a new backup file (backup.new) from the old backup file (backup.old) and the journal accumulation files (SPINOUT.001 and SPINOUT.002):Since no segment is specified, all pages from all segments in the journal accumulation files are included in the new backup file. You must manually delete the old files.
• Make sure your master accumulation file (spinout.000) is not in use by the automatic merge process spin03.bat when you run this step. This process should be scheduled to run at a time when the system is not busy running frequent spins.
• There is a limit to the number of bytes that can be passed as a parameter on the command line: approximately 200 bytes or 16 filenames that are each 12 bytes in length. If your SPINLIM variable is set higher than 14, ensure your procedure merges only 14 journal accumulation files at a time.
• Continuous backup and recovery works on completed (committed) transactions. Transactions in the contingency log are not complete and are not part of the backup process. For more information on the contingency log, refer to Chapter 1, Introducing TIBCO Object Service Broker Backup and Recovery Components.TIBCO Object Service Broker for Open Systems Utilities for information on using the hrnbrptr and hrntlmrg utilities.
Some utilities can modify the contents of the database but do not write journal records. After running such utilities, you must recommence your continuous backup.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |