Use the backup command to run Exchange
Server database backups from the Exchange Server to Tivoli® Storage Manager server storage.
Microsoft Exchange Server considers
the wildcard character (
*) to be an invalid character
when used in database names. Databases that contain the wildcard character
(
*) in their name are not backed up. When a full
VSS snapshot backup (created for back up to
local shadow volumes)
is run, the backup remains active until the backup version is expired
on the
Tivoli Storage Manager server according
to the defined server policy. As a result, different active backups
can exist at the same time:
- VSS local (full)
- VSS local (copy)
- VSS Tivoli Storage Manager server (full)
- VSS Tivoli Storage Manager server (copy)
The Exchange database file size might increase resulting from
increase database commitments that are triggered by backup operations.
This behavior is standard for
the Microsoft Exchange server.
For SAN Volume Controller and Storwize® V7000 storage
subsystems, only one backup is allowed to occur while the background
copy process is pending. A new backup is not started until the background
copy process for the previous backup completes. As a result, local
backups for SAN Volume Controller and Storwize V7000 storage
subsystems are to be initiated at a frequency greater than the time
required for the background copy process to complete.
See Backup strategies for
more information that is related to the backup command.
Data Protection for Microsoft Exchange supports
the following types of backup:
- Full
- Back up the entire database and transaction logs. If a successful
integrity check and backup are obtained, the Exchange Server truncates
the committed log files.
- Incremental
- Back up the transaction logs. If a successful integrity check
and backup are obtained, the Exchange Server deletes the committed
log files.
- Differential
- Back up the transaction logs but do not delete them.
- Copy
- Back up the entire database and transaction logs. Do not delete
the transaction logs.