- Select "Backup" Option and click next.
- Create or Edit Backup Set
DBBackup uses a Backup Set to process backup. At the first time you
have to Create a New Backup Set and later you can use it
for further backups:
- Create a New Backup Set.
Enter a brief description of the Backup Set and select a database instance to backup.
DBBackup finds all instances automatically.
MS Exchange Server backups work in 2 modes: backup of an entire store(s) and
backup of individual messages. To backup individual messages you have to create
a new MAPI profile that has administrator privileges and use it as a database
instance for your Backup Set. To backup an entire store, you have to select a MS Exchange Server instance.
If you do not see the instance, please, be sure that esebcli2.dl is available and DBBackup can load it.
Press the Next button to enter other properties.
- Use existing Backup Set
Double click on a Backup Set to check its properties.
At this point you might want to proceed backup without accessing to
other properties of Backup Set. To do this, just click right button of mouse
on selected Backup Set and choose one of following commands:
- Delete Backup Set
- Run backup of changes that were made since previous backup...
- Run backup of entire datafiles...
- Show Backup Logs
- Create Wondows shortcut for Backup Set
- Login properties
- Enter Username and Password to connect to instance as SYSDBA.
You can leave them blank if Windows NT user has OSDBA privileges (Oracle) or
MS SQL Server requires only Windows authentication.
- Select backup mode for Oracle database only:
- In ONLINE mode via ALTER TABLESPACE ... BACKUP statement, users
will be able to connect and work with database. We recommend start
this type of online backup in moments with minimum user's activity, because Oracle
writes entire data blocks in the redo logs during backup.
- In OFFLINE mode Software will shutdown database (with immediate option) before
backup and will open it after backup.
- In ONLINE mode via Recovery Manager API. Software users native backup
capabilities of Oracle8 database to perform backups. It connect to separate Oracle thread
that sends data to Software. This type of backup does not reflect to
size of redo logs.
NOTE: You have to have Windows NT privileges to install, start, stop and
remove kernel drivers.
NOTE: This mode available only for Oracle8 and higher.
Press "Next" button. Software automatically will try to login to server
to check properties that you have entered. Also DBBackup
checks restrictions and tells you if some of them are violated.
- Select databases to backup (MS SQL Server and MS Exchange Server only)
Here you can select which databases you want to backup. You can
backup All databases of selected instance or Only selected (with red tick).
When you select Only selected databases you can add a new database, but it won't
be backed up. If you select All databases a new database will be backed up
at the next backup sessions.
- Backup storage
In this page you have to specify backup storage (i.e. Where backup files will be stored) and
a key to encrypt backup archives. Go to Program Options to generate a new encryption key.
- Backup options
You can setup a number of options to control backup process:
- Backup N datafiles or databases simultaneously: - To increase backup speed
DBBackup can start a few backup threads (each of them will backup
one file or database). NOTE: Oracle ONLINE backup mode can't backup datafiles from different
tablespaces at the same moment. That's why it waits until all datafiles of one
tablespace will be backed up before start backup of next tablespace.
- Compress level (0-9): - Here you can set compress level that will be used for
backups. Small values take less time, but more space. Big values take more time, but less space.
We recommend use level 4 or 5.
- Make separate copy of datafile and backup it - Sometimes this option
can minimize backup time of real datafile by making temporary copy of it. When copy is ready
Software returns datafile to normal mode and continues work with copy that will be
deleted after backup. As you understand this option require MANY free space on your HDDs.
- Redo logs options (Oracle only)
Read screen instructions for more info.
- External commands
You can start external commands before
and after backup process. Also you can execute SQL statement
or SQL script as external command. To do that use
$(ExecSQL) and
$(ExecSQLScript) variables instead of name of executable file
and type SQL statement or path to SQL script in the Parameters
field. NOTE: SQL statement or SQL script cannot require user's input.
If they do, backup will wait for it forever, because Software starts SQL tool in
hidden mode without user's interaction.
- Scheduling
This page allows you to select 2 options:
- Run this type of Backup immediately - You can backup whole datafiles or only
changes that were made within datafiles since previous backup. NOTE: At the first
time Software will backup whole datafile in any case. Also you can save Backup
Set without backup.
- Run backup of this Backup Set periodically (Scheduler properties) -
You needn't run backup every time manually and can set period between
backups. DBBackup Scheduler will automatically perform incremental backups.
Select how often you want perform backups (every day/week/month and time to perform it).
Press "Next" button to start backup process.