Restore Data - Office Communications Server - Full System Restore
Topics |
How To |
Full System Restore |
Related Topics
Overview
Perform a Full System Restore
Post-Restore Considerations
A full system restore differs from a normal restore based on the severity of
the problem. Most times, when data is lost or removed, it is recovered from the
backup media through normal restore procedures. But when a normal restore operation cannot correct a
software problem, some level of full system restore is required.
The Office Communications Server
works in conjunction with the Windows File System iDataAgent.
In addition, the SQL iDataAgent is used to back up the database that contains the OCS metadata. Due to these agents, operating system, and database interrelationships, a full system
restore for OCS can involve several components and processes.
In addition to restoration of OCS data and/or metadata, a full system restore
of OCS
may include restoration of any or all of the following components:
The following chart outlines
two main situations and the required recovery processes.
| Situation |
Process |
| Only OCS metadata is lost |
Loss of OCS metadata requires a restore of the SQL database that
contains the OCS metadata. Refer to
SQL Server
iDataAgent
for more information on |
| Hardware failure or operating system is corrupt |
This scenario requires you to check the hardware and
rebuild the operating system before attending to the
iDataAgents and the data that is involved. See
Perform a Full System Restore
on this page. |
- Make sure that you have backups of OCS, Windows File System, and SQL iDataAgent.
- Use the same disk size, partitions, and number of disks that you used
before the failure.
A full system restore is the process of restoring all files (including OCS
data, the
operating system, applications, and agents) and the OCS metadata database on a client computer
after a catastrophic event.
Before You Begin
- Rebuild the hardware as it existed before.
- Install the same Windows operating system with the same patches that were previously
installed. See
Rebuild the Operating System on the Full System Restore page for Windows
File System.
- Configure the system with the same networking parameters and passwords that were
previously set.
- If you are not using DNS, set up peer-to-peer communication with the CommServe. Edit the
host file to include the CommServe name.
To perform a full system restore of Office Communications Server:
- After rebuilding the operating system, restore the Windows File System
iDataAgent software, exclude
OCS from the restore. See
Restore the Windows File System
iDataAgent.
| |
- Ensure that you exclude OCS from the restore.
- Also, ensure that the Unconditional Overwrite option in
the Restore Options dialog box is selected when performing a full
system restore of OCS server.
- Note that the OCS services will be disabled after the File System restore is
performed.
|
This step may bring back the SQL iDataAgent; if
not, install it as well.
- Restore the SQL
database for the OCS application using the SQL
iDataAgent.
Refer to Restore Data -
Microsoft SQL Server - Full System Restore for more information.
NOTES
- If the SQL instance on the OCS is in such a state that the
SQL iDataAgent will not
attempt to install, you may override the installer prerequisite checks
by using the
GalaxyInstallerFlags registry key. This may allow the recovery
process to progress further.
- Start the OCS Front End Service from the Service Control Manager.
- If the service does not start, use the SQL Server
Management Studio to enable the Cross DB Ownership Chaining
option (using "sp_dboption '<dbname>', 'db chaining', TRUE") for both
rtc and rtcdyn databases.
- restart the service.
- Restore the following using the in place restore:
Perform a full backup of the
following components to ensure the existence of a current backup:
- OCS
- Windows file system
- SQL iDataAgent database that
contains the OCS metadata
- Enable the OCS services
Back To Top