|
By centralizing control over
your software and hardware, you can reduce costs and
improve security and reliability. As a company grows,
additional C-Cure systems are often added without centralized planning.
This ad hoc growth and mergers or acquisitions
yield additional C-Cure systems.
The card management overhead, and expense of maintaining
multiple software and hardware installations can become
burdensome. By consolidating the systems, you save on
expensive datacenter space, hardware/software
maintenance, and management and data entry labor. |
| |
|
| |
Highlights |
 |
C-Cure backups are sent to FIS and
loaded on a development system |
|
|
Data is extracted from each system using
FIS tools |
|
|
One system is designated the "base"
system. All personnel and configuration data from the
base system is retained |
|
|
Configuration data from the rest is
added to the base. Certain data such as users,
passwords, personnel views, maps, and user privileges is
not transferred |
|
|
Deleted personnel records are removed
and personnel records from the non-base systems are
update/added to the base system including assigned
clearances |
|
|
The databases are optionally partitioned |
|
|
A C-Cure backup is returned to load on
the new server |
|
|
The C-Cure redundancy option is often
added to the new server to improve security and
availability |
| |
|
| |
Notes |
|
|
All systems must upgraded to the same
C-Cure version |
|
|
FIS recommends customers do a database
"cleanup" prior to sending data to FIS to merge. Items
like offline hardware, duplicate person records, unused
clearances should be deleted if possible |
|
|
The turnaround time is about 3 days for
a 2 system merge. Add an additional 2 days for each
additional system |
