| Technical Information |
The backup files are stored in a folder named BACKUP that is located under the program directory. Each time the Back Up Data Files utilityis run, the information is backed up to a file named STBACK.ARQ found in a folder named in the yyyymmddnn format (i.e., 4 digit year, 2 digit month, 2 digit day, 2 digit number of the backup for that day). Information regarding which files are backed up can be found in Knowledge Base Article R11420 - Troubleshooting the Built-In Backup.
During the backup process, a Failed folder is used until the backup successfully completes. Once complete, the oldest backup folder is deleted and the Failed folder is renamed using the current date and incrementing the last number used that day by 1. If the backup is aborted, the Failed folder is deleted, and the existing backup folders are retained. If the backup fails for any reason, the Failed folder will be retained until the next time a backup is started.
Note: Aborting a backup does not change the existing backup folders.
When restoring a file, the STBACK.ARQ file is the file that is restored. If the Back up the current data before restoring option is selected, the current data files are backed up to the Failed folder. When this backup completes, the oldest backup folder is deleted from the directory, and the Failed folder is renamed using the standard backup naming convention.
File Size Limitations
The maximum compressed file size that can be created using the Back Up Data Files utility is 2 GB. Additional information can be found in our Knowledge Base on the internet in the following articles:
Note: Email attachment files are no longer included in the ARQ backup file, thereby eliminating the cause for most firms to run into the 2 GB file size limitation for the ARQ backup.
Note: All GLS Clients are included in the backup, regardless of which Client is currently selected.
| See also: | Knowledge Base Article R11134 - Large File Size Limitations in Tabs3 Software |
| Knowledge Base Article R11420 - Troubleshooting the Built-In Backup | |
| Knowledge Base Article R11421 - Creating a Built-in Backup Without Overwriting an Existing Backup |