Computer Associates BABWBR1151S40 User Guide - Page 37

Database Level Backup and Restore for Exchange Server 2000 and 2003, Performing Database Level Backups and Restores

Page 37 highlights

Database Level Backup and Restore for Exchange Server 2000 and 2003 The Agent Options dialog opens. The advantage of selecting a backup method at the storage group level is that it gives you the flexibility to use a different method for different storage groups. You can select from the following backup methods: Use globally scheduled backup method Enabled by default. You must disable this option if you want to set a backup method at the storage group level. If you do not disable this, you must select a backup method on the Schedule tab. Note: If you do not disable this and select Custom Schedule on the Schedule tab, there is no difference between the full (Keep Archive Bit) and full (Clear Archive Bit) backup methods; they both function as full. 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. While the backup is taking place, new database changes can occur, so a patch file (.pat) is created to log these late changes. The patch file is backed up at the end of the process along with the log files. These backed up .pat files are restored automatically with the log files. Note: 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. Chapter 3: Performing Database Level Backups and Restores 37

  • 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 2000 and 2003
The Agent Options dialog opens.
The advantage of selecting a backup method at the storage group level is that
it gives you the flexibility to use a different method for different storage
groups. You can select from the following backup methods:
Use globally scheduled backup method
Enabled by default. You must disable this option if you want to set a
backup method at the storage group level. If you do not disable this, you
must select a backup method on the Schedule tab.
Note:
If you do not disable this and select Custom Schedule on the
Schedule tab, there is no difference between the full (Keep Archive Bit)
and full (Clear Archive Bit) backup methods; they both function as full.
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. While the
backup is taking place, new database changes can occur, so a patch file
(.pat) is created to log these late changes. The patch file is backed up at
the end of the process along with the log files. These backed up .pat files
are restored automatically with the log files.
Note:
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.
Chapter 3: Performing Database Level Backups and Restores
37