Scribd
Upload
3 views

DBA Backup Types

The document explains different types of database backups: Full Backup captures the entire database, Differential Backup captures changes since the last full backup, and Transaction Log Backup records transactions since the last log backup. It also discusses the use of the `sp_who` command in SQL Server to identify and kill specific processes and describes tail-log backups, which capture transaction logs before a database is restored or taken offline. Tail-log backups are crucial for maintaining data integrity during recovery processes.

Uploaded by

bharathkrishnan154
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
3 views

DBA Backup Types

The document explains different types of database backups: Full Backup captures the entire database, Differential Backup captures changes since the last full backup, and Transaction Log Backup records transactions since the last log backup. It also discusses the use of the `sp_who` command in SQL Server to identify and kill specific processes and describes tail-log backups, which capture transaction logs before a database is restored or taken offline. Tail-log backups are crucial for maintaining data integrity during recovery processes.

Uploaded by

bharathkrishnan154
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

1.

what is meaning of database backup type 1,2,5 for fullbackup


database ,differential database and transaction?

The terminology mentioned, "database backup type 1, 2, 5," is not standard within
the database management field. Instead, different database management systems
(DBMS) use their own terminology and methods for classifying backup types. However,
I can provide a general explanation of common backup types for databases, which
might help you understand the concept better.

1. Full Backup (Type 1):


- A full backup is a comprehensive backup of the entire database.
- It captures all the data and database objects at a specific point in time.
- Full backups are the most complete and provide a good starting point for
database recovery.

2. Differential Backup (Type 2):


- A differential backup captures only the changes made to the database since the
last full backup.
- It reduces the amount of data to be backed up compared to a full backup,
making it faster and requiring less storage.
- Differential backups can be used in conjunction with full backups for
efficient backup strategies.

3. Transaction Log Backup (Type 5 or Log Backup):


- A transaction log backup captures the transaction log records generated since
the last transaction log backup.
- It doesn't include the actual data but rather the sequence of transactions
that occurred.
- Transaction log backups are crucial for point-in-time recovery and are
typically used in combination with full and differential backups.

The numbering system (Type 1, Type 2, Type 5) doesn't have universal significance
and can vary depending on the terminology used by a specific DBMS or backup
software. It's essential to refer to the documentation of the database system or
backup solution you are using to understand how they categorize and implement
backup types.

2.sp_who kill

In SQL Server, the `sp_who` stored procedure is used to retrieve information about
the current user connections to the database. It provides details about active
processes, such as the session ID, login name, database, status, and more.

If you want to "kill" a specific SQL Server process, you can use the `KILL`
command. However, you need to know the process ID (SPID) of the connection you want
to terminate. Here's how you can do it:

1. First, use `sp_who` to identify the SPID of the session you want to kill.
Execute the following query to get a list of active connections:

```sql
sp_who
```
Use the `KILL` command with the identified SPID to terminate the connection. For
example, if the SPID you want to kill is 123, you would run:

```sql
KILL 123
```
Please exercise caution when using the `KILL` command, as terminating a connection
can disrupt an ongoing transaction and potentially lead to data inconsistencies or
loss. It should be used carefully and only when necessary. Make sure you have a
good reason for terminating a session, and be aware of the potential consequences.

3.what is tail log backup?

A tail-log backup is a type of backup operation performed in Microsoft SQL Server


to capture the transaction log records that are generated after the most recent
regular database backup and just before a database is taken offline or restored.
This type of backup is often used when you need to recover a database to a specific
point in time right before a catastrophic event, such as a hardware failure or a
critical database corruption.

Here are some key points to understand about tail-log backups:

1. Purpose: Tail-log backups are essential for maintaining data integrity and
consistency when a database restore is required. They help ensure that no committed
transactions are lost during the restore process.

2. Scenario: Tail-log backups are typically used in emergency situations, such as


when you're preparing to restore a database that has been damaged or is being taken
offline permanently, and you want to recover as much data as possible up to the
last moment.

3. Steps:
a. Before taking a tail-log backup, ensure that you've already taken a full
database backup and possibly some differential backups.
b. Execute a tail-log backup just before the database is taken offline or
restored. This captures the transaction log records that are still in the active
log, including any uncommitted transactions.
c. After the tail-log backup is completed, you can use it in conjunction with
the last full backup and any differential backups to restore the database to a
specific point in time.

4. Recovery: To recover the database, you would restore the last full backup, any
differential backups, and then apply the tail-log backup to bring the database to
the desired point in time.

5. SQL Command: To perform a tail-log backup in SQL Server, you can use the `BACKUP
LOG` statement with the `WITH NORECOVERY` option to keep the database in the
restoring state until you're ready to complete the recovery process. For example:

```sql
BACKUP LOG YourDatabaseName TO DISK = 'C:\Backup\TailLogBackup.trn' WITH
NORECOVERY;
```

Tail-log backups are an important part of disaster recovery planning for SQL Server
databases, as they help ensure that no data is lost during the restore process,
even in the event of unexpected failures.

You might also like