FASTBCP_BACKUP_RESTORE_POINT
Overview
FastBCP reads the latest version the backup files hold:
--connectiontype backup_mssql(since FastBCP 1.6.7): the newest full backup, and the newest differential backup taken from it.--connectiontype backup_rman(since FastBCP 1.6.8): for each datafile, the newest full or level 0 backup, and the incremental backups taken on it.
The FASTBCP_BACKUP_RESTORE_POINT environment variable changes that without touching the command. Set it to full to ignore the differential or incremental backups and read the full backup.
Syntax
- Windows
- Linux
$env:FASTBCP_BACKUP_RESTORE_POINT = "full"
export FASTBCP_BACKUP_RESTORE_POINT=full
Configuration
| Property | Value |
|---|---|
| Values | latest or full, in any case. Any other value stops the run at startup with a message naming the variable |
| Default | Not set: latest |
| Applies to | --connectiontype backup_mssql (since 1.6.7), --connectiontype backup_rman (since 1.6.8) |
| Since | FastBCP 1.6.7 |
| Value | backup_mssql | backup_rman |
|---|---|---|
latest | The newest full backup among the files, and the newest differential taken from it | For each datafile, the newest full or level 0 backup, and the incremental backups taken on it |
full | The last full backup of one backup, as up to FastBCP 1.6.6. Its later differentials are ignored, and several backups in --database are refused | For each datafile, the most recent full or level 0 backup. The incremental backups are ignored |
warning
With full, an export does not read the differential or incremental backups, and so gets older rows, without any message saying so. Use it when that is what you want.
With --sourceconnectstring
An adbc.arpemsbackup.restore_point option (backup_mssql) or adbc.arpeorabackup.restore_point option (backup_rman) in --sourceconnectstring wins over the variable.
See Also
FASTBCP_BACKUP_RESTORE_MODE, what happens when a backup cannot be used- Upgrading to 1.6.7 (
backup_mssql) - Upgrading to 1.6.8 (
backup_rman)