Sybase's backup

If the hardware media fails (such as disk corruption), the database can be recovered only if the database and its transaction log have been backed up in advance.

Note: Never use the operating system's copy database device, and loading such a copy into SQL Server will result in a large number of database damage.

Type of Backup:

Full Backup ()

Incremental backup--Backup transaction log

Description

(1) Only the transaction log on a separate device, in order to carry out incremental backup;

(2) Backing up the transaction log truncates the log, so the contents of the backup are transactions that have been transacted since the last backup.

(3) Start the backup server before backing up and preferably create a dump device.

Command syntax:

Dump DATABASE name

To dump device name/physical file name

Dump TRANSACTION Database name

{with {Truncate_only|no_log}

To dump device name/physical file name

[With No_truncate]

The TRUNCATE_ONLY and NO_LOG options are used to delete transactions without copying them. Truncate_only truncate the log, and no_log the transaction log when it is fully full, and does not establish checkpoints for the database. Two options will lose the log. When these two parameters are used, the entire database should be backed up in a timely manner.

No_truncate copies the log but does not truncate the log, using this option when media errors occur.

The corresponding relationship between the options of the graphical interface and the command parameters:

(1) Dump TRANSACTION (2) DUMP transaction ... with No_truncate

(3) Dump transaction ... with TRUNCATE_ONLY

(4) Dump transaction ... with NO_LOG