Computer Associates BABWBR1151S40 User Guide - Page 55

Full Backup, Copy Backup, Incremental Backup

Page 55 highlights

Database Level Backup and Restore for Exchange Server 2007 Full Backup This is the default. It backs up the entire database, including the log files, and marks all of the files that have been backed up in preparation for a subsequent incremental or differential backup. The log files are also truncated during a full backup. The backup operation then purges, from the Exchange Server, the committed log files it no longer needs. If you dismount one or more databases in a storage group during the backup operation, the agent does not truncate the transaction logs. The final result will be equivalent to that of a copy backup operation - not a full backup operation. A full backup is required to run incremental or differential backups. Note: You should always perform a full backup when running the agent for the first time, after upgrading to a Service Pack, and after performing a restore. Copy Backup Backs up the entire database, including the log files, but does not mark the files as having been backed up. Use a copy backup if you want to make a full backup of your data but do not want to disrupt any existing incremental or differential backups. Note: The log files are not truncated during a copy backup. Incremental Backup Backs up the log files that have changed since the last full or incremental backup and marks them as backed up. The log files are also truncated. When restored, the log files are applied to recreate the database at the time of backup. Be aware of the following behavior: ■ Microsoft Exchange does not support incremental backups when the Circular Logging option is enabled. If you do not disable the Circular Logging option and submit an incremental backup job, the agent automatically converts the incremental backup to a full backup. For more information about Circular Logging, see the Administration Guide. ■ If you submit an incremental backup job without first performing a full backup of the storage group, the agent automatically converts the incremental backup job to a full backup job. Chapter 3: Performing Database Level Backups and Restores 55

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159

Database Level Backup and Restore for Exchange Server 2007
Full Backup
This is the default. It backs up the entire database, including the log files,
and marks all of the files that have been backed up in preparation for a
subsequent incremental or differential backup. The log files are also
truncated during a full backup. The backup operation then purges, from
the Exchange Server, the committed log files it no longer needs.
If you dismount one or more databases in a storage group during the
backup operation, the agent does not truncate the transaction logs. The
final result will be equivalent to that of a copy backup operation - not a full
backup operation. A full backup is required to run incremental or
differential backups.
Note:
You should always perform a full backup when running the agent for
the first time, after upgrading to a Service Pack, and after performing a
restore.
Copy Backup
Backs up the entire database, including the log files, but does not mark the
files as having been backed up. Use a copy backup if you want to make a
full backup of your data but do not want to disrupt any existing
incremental or differential backups.
Note:
The log files are not truncated during a copy backup.
Incremental Backup
Backs up the log files that have changed since the last full or incremental
backup and marks them as backed up. The log files are also truncated.
When restored, the log files are applied to recreate the database at the
time of backup.
Be aware of the following behavior:
Microsoft Exchange does not support incremental backups when the
Circular Logging option is enabled. If you do not disable the Circular
Logging option and submit an incremental backup job, the agent
automatically converts the incremental backup to a full backup. For
more information about Circular Logging, see the
Administration
Guide
.
If you submit an incremental backup job without first performing a full
backup of the storage group, the agent automatically converts the
incremental backup job to a full backup job.
Chapter 3: Performing Database Level Backups and Restores
55