Remote Backup - How To
Topics |
How To |
Support |
Related Topics
Data Backup
Create a Replication Set
Add or Edit a Replication Pair
Configure Orphan File Processing
Start a Full/Incremental Backup
Schedule a Full/Incremental Backup
Transfer Data When a Full Backup Cannot be Performed
Recovery Points
Configure CDR Recovery Points
Create a Recovery Point Using CDR
Create a Recovery Point Using CDR in a Fan-In
Configuration
Data Recovery
Copy Back File System Data from a Recovery Point or the Live
Copy
Copy Back Exchange Data from a Consistent Recovery Point
Copy Back SQL Data from a Consistent Recovery Point
Copy Back Oracle Data from a Consistent Recovery Point
Application Integration
Configure to Replication Application Data
Throttling
Configure Network Bandwidth Throttling
Others
Switch from Continuous Replication to Remote Backup
Create a Replication Set
You can use the Wizard to create a
Replication Set instead of using the procedure below; to do so, right-click
the ContinuousDataReplicator icon in the CommCell, and select Replication Set
Creation Wizard.
Required Capability:
Capabilities
and Permitted Actions
To create
a Replication Set:
- In the CommCell Browser, right-click the ContinuousDataReplicator icon of
the source machine, select All Tasks, then select Add Replication
Set.
- In the
General tab, specify a name for the Replication Set, and a Destination Host
that has CDR installed. Select the Replication Type.
For CDR on Windows, in
the User Name field, specify a Windows User Account that is part of the
Local Administrator group on the destination, with read/write permissions for
the product installation folders on the destination. If the replication logs
directory on the destination is not in the default location, then the User
Name supplied here must also have read/write permissions for that directory
as well.
For Unix, specify the option to identify the backup data, Use Journaling
or Create Snapshot. See Replication Set
for details.
- In the Pre/Post Process
tab, specify any commands to be run before a Recovery Point is created, and/or
after one has been created, and specify a User Account with permissions to run
the command(s) on the destination machine. For more information, see
Pre/Post Processes.
- In the
Replication Options tab, make any appropriate selections. See the following
for more information:
- In the
Orphan Files tab, specify how to treat data that is found on the destination,
which is not on the source machine. (See Orphan
Files.)
- Optionally, make any appropriate selections in the
Storage Policy tab. For more information about Recovery Points and backups,
see Recovery Points.
- Optionally, filter the content of any Replication Pairs that are created
for this Replication Set in the
Filters tab. For more
information about Filters, see
Replication Filters. To exclude data from data replication operations, do
one of the following:
- Click the Add button and, in the Enter Path window, type
the complete path (including drive letter) of the file/folder/directory
that you want to exclude from data replication. Repeat this step if you
want to add more files/folders/directories to the filter.
- Click the Browse button and expand the file system of the client
computer. Click the file/folder/directory that you want to exclude from
data replication and then click Add. Repeat this step for each additional
entry.
- To configure User Security, select the
Security
tab. For more information, see User Administration
and Security.
- Click OK to save your changes.
![note.gif (292 bytes)](../../images/note.gif) |
- To configure User Security for the Replication Set, after it has been created,
expand the ContinuousDataReplicator icon of the source machine, right-click
the Replication Set and select Properties, then select the Security
tab. For more information, see User Administration
and Security.
- To specify that all Replication Pairs created for this Replication Set are
to use a Common
Base Folder (the same folder on the destination host to contain all destination
paths) see Add or Edit a Replication Pair.
|
Add or Edit a Replication Pair
Before You Begin
- You can only update a Replication
Pair whose state is Stopped, New Pair, or Failed.
Required Capability:
Capabilities
and Permitted Actions
To add or
edit a Replication Pair:
- In the CommCell Browser, right-click a Replication Set in the source machine,
and select All Tasks, then select Manage Pairs.
- To add a Replication Pair, in the
Manage Pairs dialog, perform the following:
- Specify a
Common
Base Folder so that all destination paths for all Replication Pairs
in the Replication Set will be created in the same location on the destination
host.
- For File System data, click Add. In the Add Replication Pair
dialog box, type, or click Browse to navigate to and select, a source
volume or directory for the Source Path and Destination Path fields, then
click OK.
- For application data, click Add App; in the
Add
Applications dialog, select all of the directories associated with the
application data to be replicated, and click OK. For more information
about replicating application data, see
Application Integration.
![note.gif (292 bytes)](../../images/note.gif) |
Add App discovers the location of system databases on the
client, as well as user-defined databases (for example,
.mdf, .ndf,
.ldf), which you can select for data
replication. |
- To edit a Replication Pair, in the Manage Pairs dialog, select the
new Pair or one to edit, click Edit, make any changes in the Replication
Pair dialog box, and click Close.
- To specify that additional Replication Pairs must be created for mount points
that are part of your selected source volume or directory, select Automatically
detect mount points. Mount points will be ignored if this option is not
selected.
- To engage all the VSS writers available in the source path when gathering
backup data, select Engage All VSS Writers option.
- When your changes are complete, click Apply.
Before You Begin
Required Capability:
Capabilities
and Permitted Actions
To
configure orphan file processing for a Replication Set:
- From the CommCell Browser, right-click the Replication Set on a source
computer, and select Properties.
- From the
Replication Set Properties (Orphan Files)
tab, perform the
following selections:
- Select the Log orphan file names option to identify and log
the orphan files. Note that the orphan files are always logged whether
this options is selected or not.
- Select Automatically deleted orphan files to automatically
log and delete all orphan files found on the destination.
- Click OK.
Backup jobs using the Run Immediately option allow you to secure data
immediately without having to wait for the scheduled backup time. This capability
can be useful if:
- you have some particularly valuable data that you need to secure immediately.
- your data is not routinely secured through a backup schedule and you want
to back up your data.
Required Capability: See
Capabilities
and Permitted Actions
To start an immediate backup
job:
- From the CommCell Browser, right-click the replication set to want to back
up, select All Tasks and then select Backup.
- For supported applications, if you wish to quiesce the source application when the data is captured
for backup, select the Quiesce Applications option.
- If you wish to create Recovery Points on the destination at the end of the
backup job, select the Create Recovery Point option.
- To backup the entire source data, select Full Backup. To backup
source data that has changed since the previous backup, select Incremental
Backup. Note that the very first backup for a replication set will automatically
be converted to a Full Backup.
- From the Backup Replication Set dialog box, select Run Immediately.
- Click OK to execute the backup job.
You can schedule backups to occur with the following procedure. You will be prompted
to create a schedule for the data protection
operation after selecting your data protection options.
Required Capability: See
Capabilities
and Permitted Actions
To schedule a backup operation
from the CommCell Console:
- From the CommCell Browser, right-click the replication set, select All
Tasks and then select Backup.
- For supported applications, if you wish to quiesce the source application when the Workstation Backup
captures the snapshot for backup, select the Quiesce Applications option.
- If you wish to create Recovery Points on the destination at the end of the
backup job, select the Create Recovery Point option.
- To backup the entire source data, select Full Backup. To backup
source data that has changed since the previous backup, select Incremental
Backup. Note that the very first backup for a replication set will automatically
be converted to a Full Backup.
- From the Backup Replication Set dialog box, select Schedule. Click
OK to continue.
- From the Schedule
Details (Schedule Details) dialog box, create a schedule for this operation.
For step-by-step instructions, see
Create a Job Schedule.
Click OK to continue.
- Your backup operation will execute according to the specified schedule.
The following procedure explains the procedure to perform the initial data
transfer using out-of-band synchronization from the command line.
To
perform initial transfer of data using the out-of-band synchronization:
On Windows
- Ensure that the necessary replication pairs are created for the client.
- On the Remote Backup source computer, from the command prompt, navigate to the
<software installation
path>\Base folder and locate the CDRXHelp.exe tool.
You can run the tool with the -h option to
review the available options.
- Execute the following command to identify the Pair IDs for all the
replication pairs.
CDRXHelp.exe -pairs -vm <Instance Name> -cn
<Client Name>
* Use
Instance003 for reduced package installations.
Example:
CDRXHelp.exe -pairs -vm Instance001 -cn
Circus
CDRXHelp.exe -pairs -vm Instance003
-cn September
Sample Output:
REPID |
PAIRID |
SrcPath
|
DestPath
|
DestinationMachine |
540 |
1938 |
H:\Sales09 |
M:\circus\H\Sales09 |
central_1.storage.com |
540 |
1939 |
E:\Production |
M:\circus\E\Production |
central_1.storage.com |
- Set the USN (Unique Sequence Number) for all the replication pairs.
Note that if the USN is not set, the subsequent incremental backup would be converted to a full backup.
If no backup job has been executed from this client:
- Set the USN for each pair using the
-setUSN
option. This saves the current USN of the source volume to the
replication pair.
CDRXHelp.exe -setUSN pairs -vm <Instance Name> -cn
<Client Name> -pID <Pair ID>
Example:
CDRXHelp.exe -setUSN -vm Instance001
-cn Circus -pID 1938
- Manually create the destination folders on the destination
computer. For each source path identified in Step 3, create the
corresponding destination path on the destination machine.
If a backup job has been
executed (or attempted) from this client:
- Read the USN of source volume for each pair. Use one of the following
options.
- CDRXHelp.exe -readUSN
-vm <Instance Name> -cn
<Client Name> -pID <Pair ID>
- CDRXHelp.exe -readUSN -vm <Instance Name> -cn
<Client Name>
-path <Source path>
Example:
CDRXHelp.exe -readUSN -vm Instance001
-cn Circus -pID 1938
CDRXHelp.exe -readUSN -vm Instance001
-cn Circus -path H:\Sales09
Sample Output:
PairId |
1938 |
SrcPath |
H:\Sales09 |
DestPath |
M:\circus\H\Sales09 |
USN |
00007cc4 |
- Set the USN for each pair as identified.
CDRXHelp.exe -setUSN pairs -vm <Instance Name> -cn
<Client Name> -pID <Pair ID> -USN <USN number>
Example:
CDRXHelp.exe -setUSN -vm Instance001
-cn Circus -pID 1938 -USN 00007cc4
Sample
Output:
PairId |
1938 |
Old JournalId |
ffffffffffffffff |
Old USN |
ffffffffffffffff |
New JournalId |
1c625d8d392c299 |
New USN |
00007cc4
|
- Since a backup job has been executed from this client, the
corresponding destination folders would be available on the destination
computer.
- Transfer the data to the destination computer. You can use
a compact disc, thumb drive or a similar method to
transfer the data.
- The initial data transfer is now complete. The next incremental backup job will transfer the changes to the
source data since the initial data transfer. You can now continue with the
traditional backup schedules.
On Unix
- On the Source computer, create your Replication Pair(s) but do not start
them yet.
- On the Source computer, set the current operating system time for each
Replication Pair by using the cdrcmd -startoob
-set <repset_name> -pair <source_folder> command.
|
If you miss this step your Replication Pair
will not have the the correct time and the subsequent incremental
backup would be converted to a full backup. |
Example:
<software_installation_path>/Base> cdrcmd -startoob -set MyReplicationSet -pair /MySourcePath
- Back up the source data.
|
It is recommended that you use the Unix File
System iDataAgent to
back up the source data. |
- Restore the data to the destination path(s).
- The initial data transfer is now complete. The next incremental backup job will transfer the changes to the
source data since the initial data transfer. You can now continue with the
traditional backup schedules.
Configure CDR Recovery Points
Related Topics:
Required Capability:
Capabilities
and Permitted Actions
To configure
CDR for Recovery Points:
- For Consistent Recovery Points involving supported application, you must
Configure CDR to Replicate Application Data.
- Right-click a Replication Set and select Properties.
- In the
Replication Set Properties (Replication Options) tab, select Allow
Recovery Points.
- In the Maximum Number of Recovery Points field, specify the maximum
number to retain.
![note.gif (292 bytes)](../../images/note.gif) |
- Ensure that the destination volume specified for each
Replication Pair has sufficient space for the maximum number of
snapshots that will be created and retained.
- If you decrease this number for a Replication Set with existing
Recovery Points, the system will start deleting the oldest Recovery
Points in the order they were created until the newly specified maximum
number is reached. For additional considerations, see
Delete a Recovery Point Using CDR.
- For a listing of the maximum number the system allows for each
operating system and snapshot type, see
Maximum Number of Recovery Points.
|
- You can configure CDR on Windows to automatically mount the snapshots from the latest Recovery Point
when they are created. (This is not available for ONTAP Snapshots.) You
can configure CDR on UNIX, which automatically
mounts every snapshot by default, to automatically create a symbolic
link to the mount points it creates. To do this, select the Auto-Mount snapshots after Recovery
Point Creation option, then click Enter Mount Points. In the
Enter Mount Points dialog, click the
Mount Point column for each Destination Path and do one of the
following:
- For Windows, do one of the following for each snapshot to be
mounted:
- specify a drive letter (e.g., G:)
to which to mount the snapshot. Ensure that you specify an unused drive letter.
- type a mount point name (e.g., G:\mountpoint1)
to which the snapshot will be mounted.
- For UNIX, type a name for the symbolic link to the mount point
that will be created by the system.
![note.gif (292 bytes)](../../images/note.gif) |
Even though you specify the mount point for a recovery point on a UNC path,
this mount point is ignored when a recovery point is created on a UNC path.
|
- For Windows, select a Snap Engine Type. (For UNIX, the selection of a Snap Engine Type
comes later in this procedure.)
- In the Pre/Post Process tab, specify any Pre/Post Recovery Point
commands to be run. Refer to
Configure Pre/Post Processing.
- If you will be backing up Recovery Points, see
Configure CDR for Backups of Recovery Points.
- Click OK to save your changes.
- It is recommended that you
also see
Space Check for the Quick Recovery and ContinuousDataReplicator Agents
and configure the
Disk
Space Low alert to provide warning that the destination computer,
and the cache volume in particular, is running out of disk space, which will
ultimately cause all recovery points to be deleted.
For UNIX, CDR software
automatically recognizes the File Systems configured on the destination
computer and detects the appropriate snap engine. For more information on
supported snap engines, see Snapshot Engines - Support.
Create a Recovery Point Using CDR
Before You Begin
Required Capability: See
Capabilities
and Permitted Actions
To create
a Recovery Point:
- From the CommCell Browser, right-click a Replication Set, and select
Create Recovery Points.
- From the
Create Recovery Point dialog box, select the type, and whether
to create the Recovery Point immediately or schedule it. See
Scheduling for general
information.
- In addition, you can select the option of backing up Recovery Points. If you select this option, click Enter Backup Details to select the
type of backup as well as any Advanced Options.
- When you are finished, click OK.
- If you opted to schedule Recovery Point creation, the Schedule
Details dialog will appear. Specify the details for your schedule; click
Options for additional choices. When you are satisfied, click OK.
Create a Recovery Point Using CDR in a Fan-In Configuration
Related Topics:
Before You Begin
- Recovery Points cannot be created until you
Configure CDR Recovery Points.
Note that for Workstation Backup Agent, Recovery Point creation is enabled
by default.
- This procedure is only for Fan-In configurations.
Required Capability: See
Capabilities
and Permitted Actions
To create
a Recovery Point for a Fan-In configuration:
- From the CommCell Browser, right-click the destination client, and select
Browse Destination Volumes.
- In the
Browse Destination Volumes window, right-click a destination volume, and
select Create Recovery Point.
- From the
Create Recovery Point dialog box, select whether to create the Recovery
Point immediately or schedule it. See
Scheduling for general
information.
- In addition, you can select the option of backing up Recovery Points. If you select this option, click Enter Backup Details to select the
type of backup as well as any Advanced Options.
- When you are finished, click OK.
- If you opted to schedule Recovery Point creation, the Schedule
Details dialog will appear. Specify the details for your schedule; click
Options for additional choices. When you are satisfied, click OK.
Copy Back File System Data from a Recovery Point or the Live Copy
Related Topics:
Before You Begin:
Required Capability: See
Capabilities
and Permitted Actions
To copy
back file system data from a Recovery Point or the Live Copy:
- In the CommCell Browser, perform a Browse operation for one of the following:
- Do one of the following, depending on which object you browsed:
- In the Recovery Points dialog box, select the Live Copy and/or Recovery
Point(s) to be copied back, and click Copyback.
- In the Browse Window, select the Live Copy and/or Recovery Point(s)
to be copied back, and click Recover all Selected...
- In the
Copyback
dialog box, select a Recovery Host, the host to which the data will be
copied back.
- Specify a Recovery Path for the live data and/or Recovery Point(s)
you want to copy back. The Recovery Path must be larger than the data being
copied back. To assign a Recovery Path, do one of the following:
- double-click the path listed in the Recovery Path column and
type a path on the selected host
- click the Browse 'Recovery Host' button and browse to a destination
path on the selected host
- Optionally, select Overwrite existing data under 'Recovery Path'.
- Click OK to copy back the data. The system displays a progress bar
as it copies back the data. You can track the progress of the recover operation
from the Job Controller window.
Copy Back Exchange Data from a Consistent Recovery Point
Related Topics:
Before You Begin
- While it is possible to copy back Exchange data from the Live Copy, this
data is not in a consistent state and thus application integrity is not ensured.
Required Capability: See
Capabilities
and Permitted Actions
To copy
back Exchange data from a Consistent Recovery Point:
- For Outlook 2003, change the profile for any mailboxes being restored
which have "Cached Mode" enabled, to DISABLE CACHED MODE. "Cached
mode" can be enabled again after the Copyback operation completes
successfully.
- Abort the Replication Pairs for the source volume to which you will copy
back Exchange data. This avoids slow copyback operation on the source volume.
- Dismount the Exchange Stores for the Storage Group to which you will
copy back point-in-time data.
- Delete or rename all Exchange transaction logs on the Production
Exchange Server for the Storage Group being restored.
- In the CommCell Browser, perform a Browse operation for one of the following:
- Do one of the following, depending on which object you browsed:
- In the Recovery Points dialog box, select the Consistent Recovery
Point(s) to be copied back, and click Copyback.
- In the Browse Window, select the Consistent Recovery Point(s)
to be copied back, and click Recover all Selected...
- In the Copyback
dialog box, select a Recovery Host, the host to which the data will be
copied back.
- Specify a Recovery Path for the data you want to copy back. The Recovery Path must be larger than the data being
copied back. To assign a Recovery Path, do one of the following:
- double-click the path listed in the Recovery Path column and
type a path on the selected host
- click the Browse 'Recovery Host' button and browse to a destination
path on the selected host
- Select Overwrite existing data under 'Recovery Path'.
- Click OK to copy back the data. The system displays a progress bar
as it copies back the data. You can track the progress of the recover operation
from the Job Controller window.
- Mount the Exchange Stores.
- For Outlook 2003, the profile for any mailbox(es) changed to DISABLE
CACHED MODE can be changed back to Cached Mode. The user will be able to
see the recovered data instead of the cached copy.
Copy Back SQL Data from a Consistent Recovery Point
Related Topics:
Before You Begin
- This procedure assumes that you used Add App to create your Replication
Pairs. For more information, refer to
Add or
Edit a Replication Pair and
Application Integration.
- While it is possible to copy back SQL data from the Live Copy, this data
is not in a consistent state and thus application integrity is not ensured.
Required Capability: See
Capabilities
and Permitted Actions
To copy
back SQL data from a Consistent Recovery Point:
- Abort the Replication Pairs for the source volume to which you will copy
back SQL data. This avoids slow copyback operation on the source volume.
- Detach the SQL database(s) for which you will copy back point-in-time
SQL data.
- In the CommCell Browser, perform a Browse operation for one of the following:
- Do one of the following, depending on which object you browsed:
- In the Recovery Points dialog box, select the Consistent Recovery
Point(s) to be copied back, and click Copyback.
- In the Browse Window, select the Consistent Recovery Point(s)
to be copied back, and click Recover all Selected...
- In the Copyback
dialog box, select a Recovery Host, the host to which the data will be
copied back.
- Specify a Recovery Path for the data
you want to copy back. The Recovery Path must be larger than the data being
copied back. To assign a Recovery Path, do one of the following:
- double-click the path listed in the Recovery Path column and
type a path on the selected host
- click the Browse 'Recovery Host' button and browse to a destination
path on the selected host
- Select Overwrite existing data under 'Recovery Path'.
- Click OK to copy back the data. The system displays a progress bar
as it copies back the data. You can track the progress of the recover operation
from the Job Controller window.
- Attach your SQL database(s).
Copy Back Oracle Data from a Consistent Recovery Point
Related Topics:
Before You Begin
- This procedure assumes that you used Add App to create your Replication
Pairs. For more information, refer to
Add or
Edit a Replication Pair and
Application Integration.
- While it is possible to copy back Oracle data from the Live Copy, this data
is not in a consistent state and thus application integrity is not ensured.
- Each Consistent Recovery Point for a given Oracle database comprises two
snapshots, which will be referred to in the procedures as "first snapshot"
and "second snapshot" according to the following definition of content:
- The first snapshot includes all Oracle data volumes.
- The second snapshot includes all Oracle log volumes and backup
control file for the database at the time the Consistent Recovery Point
was created.
Required Capability: See
Capabilities
and Permitted Actions
To copy
back Oracle data from a Consistent Recovery Point:
- Abort the Replication Pairs for the source volume to which you will copy
back Oracle data. This avoids slow copyback operation on the source volume.
- Shut down the Oracle database.
- Copy back the following Oracle data from the second snapshot (the
snapshot of any destination log volume) in the Consistent Recovery Point you have selected, to a temporary directory:
- Backup.ctl.galaxy
- dbconf.cfg
- GalaxyControlFile.conf
- init<instancename>.ora
- SPFILE<instancename>.ora
This can be
done using one of the following methods:
-
Mount the Recovery Point, then copy
only the files listed above to a temporary directory.
- Perform a Copyback operation. Since this will not allow you
to select which files to copy back, only use this method if you want to
copy back everything (database, logs, and files listed above) --
assuming the original folders are empty. Proceed as follows:
- In the CommCell Browser, perform a Browse operation for one of the following:
- Do one of the following, depending on which object you browsed:
- In the Recovery Points dialog box, select the Consistent Recovery
Point(s) to be copied back, and click Copyback.
- In the Browse Window, select the Consistent Recovery Point(s)
to be copied back, and click Recover all Selected...
- In the
Copyback
dialog box, select a Recovery Host, the host to which the data will be
copied back.
- Specify a Recovery Path for the data you want to copy back. The Recovery Path must be larger than the data being
copied back. To assign a Recovery Path, do one of the following:
- double-click the path listed in the Recovery Path column and
type a path on the selected host
- click the Browse 'Recovery Host' button and browse to a destination
path on the selected host
- Select Overwrite existing data under 'Recovery Path'.
- Click OK to copy back the data. The system displays a progress bar
as it copies back the data. You can track the progress of the recover operation
from the Job Controller window.
- Create the database tracing directories (udump,
bdump, cdump, etc.) for the Oracle database according to the
dbconf.cfg file you copied back in Step 3. (<Snap2Dir>/archivelog_dest1/dbconf.cfg)
- If the source database uses spfile, copy
spfile from the location you copied back to
in Step 3 to the
default location under ORACLE_HOME. For
example:
cp <Snap2Dir>/archivelog_dest1/spfile
<ORACLE SID>.ora <default spfile file path>
- If the source database uses pfile, copy
pfile from the location you copied back to
in Step 3 to the
default location under ORACLE_HOME. For
example:
cp <Snap2Dir>/archivelog_dest1/pfile
<ORACLE SID>.ora <default pfile file path>
- Copy the backup control file from the first archive log destination (from the
second snapshot) to all three control files destinations. For example:
cp <Snap2Dir>/archivelog_dest1/backup.ctl.galaxy
<controlfile1_Path from spfile>/ control01.ctl
cp <Snap2Dir>/archivelog_dest1/backup.ctl.galaxy
<Controlfile2_Path from spfile>/ control02.ctl
cp <Snap2Dir>/archivelog_dest1/backup.ctl.galaxy
<Controlfile3_Path from spfile>/ control03.ctl
![note.gif (292 bytes)](../../images/note.gif) |
GalaxyControlFile.conf also contains
the locations of the control files at the time the Consistent Recovery
Point was created. |
- If you did not perform a Copyback operation in Step 3, copy all data and
log files to the exact same path as that of the original database, either by
mounting the Recovery Point and copying the files, or by performing a
Copyback operation. In case the same destination volume is used for database
and logs, mount the first snapshot and copy all Oracle data files from the
first snapshot to the path that the control file expects. For example:
cp -a <Snap1Dir>/oradata/rman1/*.dbf /oradata/rman1/
- Copy all the log files for all destinations from the second snapshot to
the paths that the control file expects, either by mounting the Recovery
Point and copying the files, or by performing a Copyback operation. For example:
cp -a <Snap2Dir>/archivelog_dest*/
/oralogs/rman1/
![note.gif (292 bytes)](../../images/note.gif) |
If you have previously chosen to replicate only one (not all) Oracle
instance log locations, after the logs have been copied back, copy them
to the other log location (if any) on the production server. For
instance:
If you have D:\ArchiveLogs1,
F:\ArchiveLogs2, H:\ArchiveLogs3 and you initially selected to
replicate only D:\ArchiveLogs1, after
you copyback to D:\ArchiveLogs1, copy
the same files to F:\ArchiveLogs2 and
H:\ArchiveLogs3. You can either copy and
paste them from D:\ArchiveLogs1 or run
copyback again, specifying F:\ArchiveLogs2
and H:\ArchiveLogs3 as destinations,
whichever is faster in your particular environment. |
- Set the ORACLE_SID and
ORACLE_HOME environment variables.
- Run the following commands as an Oracle user:
sqlplus "/ as sysdba"
- startup mount
- set autorecovery on;
- recover database until cancel using backup controlfile;
- alter database open resetlogs;
- Database open will succeed after recovering the database.
Configure CDR to Replicate Application Data
Related Topics:
Required Capability:
Capabilities
and Permitted Actions
To configure
CDR to replicate application data:
- In the CommCell Browser, right-click the ContinuousDataReplicator icon of
the source machine, and select Properties.
- Select the Authentication tab of the Agent Properties screen,
and select one of the following:
- Exchange/SQL tab - select either Microsoft Exchange Server
or Microsoft SQL Server, click Edit, then supply the necessary
credentials for the server. For more information, see specify the
Account for Accessing Application Servers/Filers.
-
For a clustered Exchange Server, if you are not using VSS to perform
an online quiesce, sufficient permissions are required in order to be able to
perform an offline quiesce; in such cases, ensure that the User Name
specified has Exchange Administrator rights.
- Oracle tab - click Add Instance and supply the necessary credentials
and information for Oracle. Supply a user account with administrator
privileges to access the Oracle application.
- For Oracle on Unix, you can
use the operating system user account to verify the rights to perform
all data protection and recovery operations for the associated Oracle
instance.
- For Oracle on Windows, you can click the Change button
and use the Impersonate User option for this purpose.
- Click OK to save your changes.
Configure Network Bandwidth Throttling
Related Topics:
Required Capability:
Capabilities
and Permitted Actions
To configure
throttling for replication activities:
- In the CommCell Browser, right-click the agent icon
of the source computer, and select Properties.
- In the
Operational Parameters tab of the Properties screen, specify
any of the following:
- Throttling Amount - maximum network transfer rate in megabits per second
(Mbps). The
Utilization Percentage specified in the
Edit Throttling Rule
dialog will be a percentage of the number entered here.
- Bandwidth Throttling Rules - click Add to configure the
following in the
Edit Throttling Rule dialog:
- Days of Week
- Start time
- End time
- Utilization Percentage -- based on the specified Throttling Amount
(see previous item)
- Click OK to save your changes.
Before You Begin
- Ensure that the source and the destination computers are upgraded to the
current release version. See
Upgrades for
upgrade information.
- Stop all replication activities in the source computer. See
Abort Data Replication Activity for instructions.
- In the
Replication Set Properties (General) tab, change the Replication Type to
Remote Backup.
- Start the backup job. It is recommended that the first backup in the Remote
Office is a Full Backup; subsequent backups can be Incremental or Full, as required.
See Start a Full/Incremental Backup
for instructions.
Back to Top