| Data Stripes |
Use this option to specify the number of data stripes to use
in a backup or restore operation. The numstripes variable
can be in the range 1 - 64. The default value is 1.
When you
use a multiple stripes number for legacy backups, and set the Verify
Only parameter to Yes to restore
the legacy backup, the number of stripes for legacy restore must be
equal or greater than the number of stripes for the legacy backup.
|
| Estimated Database % Change |
Use this option to specify the estimated percentage of the
database that changed since its last full database backup. The default
value is 20. This estimate is useful because SQL Server does not
provide a way to determine the size of a differential backup, and
because the Tivoli Storage
Manager server requires
an accurate size estimate to efficiently allocate space and place
objects. The Tivoli Storage
Manager server uses
this value to determine whether there is enough space in the primary
storage pool to contain the backup.
|
| Estimated Log % Change |
Use this option to specify the estimated percentage of an SQL
Server database that changed due to non-logged operations since the
last log backup. The default value is 0. |
| Truncate Logs |
Use this option to specify whether to dispose of entries that
you no longer need in the SQL Server database transaction log after
you back up the log. The default value is Yes. In
general, you do not want to truncate the log when you rebuild a corrupted
database. This option enables the server to back up the transaction
log but does not affect the data. All transaction log entries are
written from the time of the last log backup to the point of database
corruption. If you do not truncate the transaction log, you might
be able to back up the transaction log of a damaged, suspect, or unrecoverable
SQL Server database.
|
| Back Up Tail-Log |
Use this option to store log records that are not backed up. By
storing these records, also known as the tail of the log,
the log chain is kept intact. Before you can recover an SQL Server
database to the last point in time, you must back up the tail of the
transaction log. The tail-log backup is the last backup of interest
for the database recovery plan.
|
| SQL Server Checksum |
Use this option to verify the integrity of a legacy database
backup. Integrity checking is a process that validates the values
in a file or configuration for unexpected changes. Values are verified
between the current state and the baseline state. In the Performance
Properties window of MMC, you can enable or disable the
checksum option for all your legacy databases at once. You can override
the global setting, and temporarily enable or disable the checksum
option for a database backup, by setting this SQL Checksum option
to Yes or No.
|