Introduction
It is sometimes necessary to move the COPIA share (the Copia Application Data files) to a new server. The destination may be a new machine with a new operating system, or a virtual machine within the company or 'in the Cloud'. When moving a single-machine system to the Cloud, please refer to Installation Notes - Cloud.
This topic assumes that you are setting up a Windows server as a file server for the COPIA network share. If you are using a non-Windows file system to host the COPIA share, please contact Copia Support for detailed advice.
CopiaFacts includes features to simplify this process, but it is very important to follow the steps in the correct sequence.
Essential FIRST Step - Preparation
Before starting to relocate and copy files to the new machine, we recommend using the CFHK housekeeping program to delete or archive older transaction files (FS, MCF) which you do not need to copy to the new share. This can greatly speed up the processing.
You must always begin by running COPIAINSTALL9 on the machine which is to be the new server. There are two situations which can arise:
•It is a brand new machine on which no CopiaFacts applications have been installed.
The second large button in COPIAINSTALL9 will then show 'First Time Installation on any network machine':
Proceed to set up the Copia Share and copy the license file from your current server. This procedure will also create new FFCFG.INI and COPIACONNECT.INI files on the new server.
If your site runs a single CopiaFacts server machine and the CopiaFacts server applications are also to run on the same new machine as the network share, having previously run on the old machine, do not yet install the server applications. Wait until the files have been copied over in step 2.
•CopiaFacts applications have already been running on the new machine, connecting to the old server.
The second large button in COPIAINSTALL9 will then show 'Relocate the COPIA share ... to this machine':
Proceed to set up the Copia Share and copy the license file, if requested, from your current server. This procedure will also create new FFCFG.INI and COPIACONNECT.INI files on the new server.
Second Step - Shutdown
It is very important to shut down all CopiaFacts applications and services before migrating the file server to a new machine. If you have users of the CopiaFacts Client in your organization, you should remove the access permissions on the old COPIA share so that FFCLIENT users are unable to access the share while files are being copied. Failure to take this step may result in transactions being lost or 'unique' FS numbers being duplicated.
If you are unable to prevent use of both file servers overlapping, you should increment the values in all the 'next' control files listed in step six below by a sufficient amount (for example 1000) to cover the use during the overlap period, in the copies on the new file server. All these files can be edited in NOTEPAD or COPIAEDIT. This will prevent duplication of the 'unique' numbers.
Third Step - Copying
 | CopiaFacts version 9 has added new programs CFEXPORT and CFIMPORT to transfer configuration files and registry entries to a new machine. These programs can also be used to backup and restore settings. CFEXPORT can be run on a machine running version 8 if you are upgrading to version 9 at the same time as the move. |
| If you use CFEXPORT and CFIMPORT, they will handle most of the manual steps below for you. The CFIMPORT topic mentions some decisions you may still have to make. |
Close all running CopiaFacts applications and copy the files in the COPIA share to the new server, making sure that FAXFACTS\FFCFG.INI is not copied. You should also not copy COPIACONNECT.INI in the ProgramData\Copia folder. Copying these files would overwrite the files which have been set up in step 1.
If you have users on other workstations using FFCLIENT, it is important to make arrangements for FFCLIENT not to be started on running while the copying is being done.
Manually Copying Files
You can use Windows Explorer or XCOPY to copy the COPIA share files over to the new machine, but be sure to check which of the many command-line options are relevant to your copy operation.
If you need to copy over saved files from the Gateway, these are usually not in the COPIA share. You will normally find these files in C:\CopiaSMTPRejectMessages and C:\CopiaSMTPSaveMessages. local to the machine on which the Gateway is running.
Manually Copying Registry Entries
If you have been running CopiaFacts programs on the old file server and will continue to do this on the new file server, copy (export and import) the contents of the following registry keys from the old server to the new:
HKEY_LOCAL_MACHINE\SOFTWARE\Copia
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Copia
HKEY_CURRENT_USER\SOFTWARE\Copia
The last of these keys must be exported using the account which is normally used to run CopiaFacts applications on the old server, and imported using the account which will be used to run CopiaFacts applications on the new server.
Copying these registry keys will ensure that your personal settings for Copia applications are transferred to the new machine. To export the sets of registry keys, right click the indicated key, select export, and choose a location to save the file. You should keep these files as a backup of your CopiaFacts registry settings. Importing is done by double-clicking the file on the new machine. Administrator privilege is required to add keys under HKEY_LOCAL_MACHINE.
Programs
If you have been running CopiaFacts programs on the old file server and will continue to do this on the new file server, now is the time to install CopiaFacts server programs on the new machine. The server installer executable should have been copied over in step 1 from the COPIA\NETBIN folder on the old network share to COPIA\NETBIN on the new server. Use the installer to do this: do not manually copy over the COPIA Program Files folder(s).
Fourth Step - Printer Drivers (only if required)
If you have CopiaFacts print drivers installed on the old server and require them on the new server, these must be installed separately on the new server. The settings cannot be copied over.
| Note that CopiaFacts no longer requires the Document Converter print driver to convert PDF, Office and HTML documents for faxing; using print drivers is an option only. |
Fifth Step - Connecting to the new Share
On each other machine running CopiaFacts applications, such as the COPIAFACTS engine, FFEXTERN Document Converters and processes, SMTP Gateway, Desktop Client applications, visit the machine and run:
\\NEWSERVER\COPIA\COPIACONNECT.EXE
The easiest way to run this is to open a Windows Run box by keying Windows-R and typing the above command. The process will request elevation if UAC prompts are enabled.
Sixth Step - Bringing up CopiaFacts on the New Share
If you have been unable to follow the advice in step 2, and have continued to run CopiaFacts applications with the old share in use before you start working with the new share, then there are two important checks to make.
•You need to copy over the recent transaction files (.FS, .MCF) which have been written to the old share since you made the copies in step 2 above. This can be done using the XCOPY command-line switch /D, which copies over only newer files. Be aware that there may be different files with the same names on the new file server.
•The files containing the next number to be used for each transaction must be checked. Three of these are in the COPIA subfolders below, and one is with the Gateway messages:
FAXFACTS\CALLBACK\TOSEND\NEXTFS
FAXFACTS\MAIL\NEXTMCF
FAXFACTS\USERJOBS\NEXTJOB (for Job Administration option only)
C:\CopiaSMTPSaveMessages\NEXTMSG
If you used CFIMPORT to import these files, it will have offered to increment the NEXT files for you.
If you fail to manage the 'next' control files correctly there may be duplicated transaction file numbers on the old and new COPIA shares.
Finally, you should check that you have no hard-coded machine names in your CopiaFacts command files, for example a command where you use \\server\COPIA\FAXFACTS instead of @FFBASE. CFFIMPORT, if used, will have scanned the imported file names for you to find any hardcoded drive letters or UNC paths. Alternatively you can do this by using the CopiaFacts Search/Replace utility FFSR. There are examples for this in the FFSR topic.
Troubleshooting
If you have accidentally copied \COPIA\FAXFACTS\FFCFG.INI from the old server and overwritten the files set up in step 1, the following entries will need to be corrected manually, as in the example below:
[FFCONFIG]
ExpectedUNCpath=\\oldserver\COPIA
ServerIP=192.168.1.182
The above entries should be changed to reflect the new server and its IP address.
