Restriction: This topic applies to Windows environments only.
The BACKUP LOCATION command will not archive off log files. Log files
must be archived manually, after which location logging must be manually reset.
To backup a location using the BACKUP LOCATION command and reset location logging:
- Ensure that nobody is currently accessing the location you are backing up, and ensure that no incomplete transactions are
in progress. You must be running in Isolation Level EU (exclusive use).
- Log into a location other than the one you are backing up (for example, SYSTEM location).
- Enter the BACKUP LOCATION command from
the SQL Wizard (Windows) or
Interactive SQL (UNIX).
- If you use removable storage media for your backups, carefully record vital information on the backup media's labels, including:
- Location Name
- Database Name
- Stogroup and log file path names
- Names of special paths that are defined in the server machine's
xdb.ini file such as paths for indexes
- Logging system information
- Backup time and date
- Bring the server down.
- Archive the current series of log files. This series of files should be clearly marked and archived in a separate directory.
They may be needed for playing against an older backup, in the event the latest location backup is corrupted or unavailable.
Serial numbers can be used to ensure that the correct series of log files are applied to the correct backup copy of the location.
- Once Step 6 is complete, delete the current series log files from the location logging directory.
- Bring the server back up. Next time the location is accessed, a new set of log files is automatically created in the location
logging directory.