Hmi Backup And Restore Utility

0 views

Skip to first unread message

Stetson Saenz

unread,

Aug 3, 2024, 1:20:54 PM8/3/24

to beypisrilpnorth

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

I backup primser server by using this command (I did not using migrate=true) then try to restore to another primary server (same hostname/IP/version) . I could see the ZCC login page...but login fail and show error 500.

[07/06/2023 11:47:19.987] [1484] [ZENLoader] [249] [] [Loader.MessageProcessorModule] [] [Corrupt Message File 1688615226-0000-d2c70d8c5a7ab2deedbb2f86afb5b07e.log: MessageID null or exceeds 256 char:

] [] [] [] [ZENServer]
[追蹤] [07/06/2023 11:50:01.320] [1484] [ZENLoader] [256] [] [QueueAdminImpl] [] [Scheduling simple action=deleteeq.process,null] [] [] [] [ZENServer]

In addition, after I recovered (using ZCC to log in) and tested that other clients can connect smoothly, but the Primary Server's own Agent cannot update its relevant information...Set it to Debug Mode to check and found some information (Protocol error and other information )
Does the restored Primary Server's own client need to perform additional actions to connect smoothly?

The Safe data files are restored to the PrivateArk\Restored Safes folder in the same structure as that in which they were backed up. After the metadata backup files are restored to the PrivateArk\Restored Safes\Metadata folder, a synchronization procedure will take place, after which users will be able to work with the files immediately.

The above example restores the entire Vault from the Restored Safes folder on the Vault machine. It will load the metadata, copy the data files to the Safes\Data folder, and synchronize the data with the metadata. Once the operation is complete, the Vault is operational and usable, and reflects the exact state it was in when the backup was taken.

The above example will synchronize the backup files that were restored in the Vault (using the RestoreDB command) with the restored Metadata. This command will be carried out, rather than simulated, and will prompt the user for confirmation during the process.

Backing up the MOVEit DMZ system can be done in one of two ways.First, you may elect to use existing backup procedures at your organization to handle backing up the system.If this is the case, you will want to consult theTechnical Reference for a complete list of thefiles, folders, and registry settings that MOVEit DMZ uses, and that need to be backed up.

An alternative to a traditional backup-to-tape method is to use the MOVEit DMZ backup and restore utilities provided by Ipswitch.These command-line utilities perform complete backups and restorations of all the files, folders, certificates and registry settings necessary toreplicate your current MOVEit DMZ configuration onto this or another platform.

The backup and restore utilities are capable of backing up and restoring the MOVEit DMZ configuration database (MySQL only),configuration registry keys, folder structure, and custom color schemes, logos, and templates.Encrypted files can also beoptionally backed up (they are not by default), as can both server and client SSL certificates (they are by default) to createa complete backup of the MOVEit DMZ state. Both utilitiesautomatically determine where the critical MOVEit DMZ files are located on the server, as well as how toconnect to the MySQL database to perform lock operations. Both utilities also provide options to allow administratorsto override these automatic detections.

Backups and restorations can be done across differing types of DMZ installations (but NOT differing versions),such as web farm and standalone installations, and installations with differing path structures. This capabilityrequires the backup and restore utilities to NOT backup MOVEit DMZ installation path information, database access information, oremail server settings. These are typically configured on a per-installation basis, and shouldnot be replicated across differing servers.

The backup utility's ability to back up the MOVEit DMZ database tables only applies to MySQL databases. When using MicrosoftSQL Server as the database for MOVEit DMZ, the utility must be run with the "--without-database" option, and the MOVEit DMZdatabase should be backed up using other tools. If the utility detects that SQL Server is being used, and the "--without-database"option has not been specified, it will display an error message and exit.

The backup utility obtains a read lock on all MOVEit DMZ database tables before backing up the MySQL database information.This is to ensure that the data does not change during the backup process. As a result, any requests that come in to MOVEitDMZ while the tables are locked will wait until the tables are available again before continuing (the read locks are released oncethe database tables have been backed up). For this reason, it is best if the backup process is run during off hours.

The backup and restore utilities do NOT back up NTFS permissions, NT users/groups, or IIS settings.If you are using these utilities to maintain a "hot standby", you will need to set these items upon the second box ahead of time. (Frequently people create a hot standby by restoring a full tape backup onto a new machine,then use periodic runs of the backup utility to keep data on the hot standby fresh.)

The backup utility is also not able to override the "do not export private key" setting you mayhave set when you imported your SSL server certificates. If the utility encounters an SSL servercertificate export error related to private keys it will immediately print the error encounteredand then exit. You can use the "--ignore-cert-export-errors" option to prevent the utility fromexiting like this, however the problem certificates will still not be backed up.

Starting with MOVEit DMZ 3.1.5, the backup and restore utilities are installedby the MOVEit DMZ setup program, and are placed in the MOVEitDMZ\Scheduler folder.The two application filenames are DMZBackup.exe and DMZRestore.exe.The programs need to be in this location in order to use some requisite libraries provided by MOVEit DMZ.These utilities may not work correctly if run from any path other than MOVEit DMZ's Scheduler folder. Ifthe utilities are run from outside the Scheduler folder, an error message will be displayed and theutility will exit.

In addition to the backup and restore utilities themselves, two additional programsare installed for use by the utilities. The first is an archivingapplication which supports the creation of fileslarger than 2GB. This application is called 7-Zip and is run using the 7z.exe programfile. The second is an SSL certificate extracting application which dumps the various MicrosoftSSL certificate stores into a format which is usable by the backup and restore utilities. Thisapplication is called ExportCerts.exe.

This will create a file called MOVEitDMZ_Backup_xxxxxxxx.7z in your Scheduler directory,where xxxxxxxx is the current date in YYYYMMDD format.This file will contain all the necessary files and information to reconstruct your DMZconfiguration. It will not backup the actual encrypted files in your DMZ configuration,however, it will backup the existing folder structure. To backup the encrypted files aswell, add the "--with-files" command-line option to the above command.

Since doing a complete backup with files requires a large amount of free disk spaceon the server (roughly twice as much free disk space as the size of your\MOVEitDMZ\Files directory), many customers opt to run a config-only backup, andthen backup the encrypted files in a different way (NTBackup, read-only FTP server,etc.). Customers who use this method should add the "--with-file-tables" option, toforce the backup utility to back up the file-related database tables, which arenormally skipped when a config-only backup is performed.

If you would like to see what the utility is doing while it runs, add the "--debug"command-line option to the above command. For a complete list of the optionsavailable in the DMZ backup utility, see the Backup Utility Commands sectionbelow, or execute the following command in your Scheduler subdirectory:

The DMZ Backup Utility is a .NET console application which runs in the Schedulerdirectory on a MOVEit DMZ system. The utility is command-line driven, so it can easilybe integrated into a batch file. A list of available options can be generated by enteringthe command "dmzbackup --help". The default values listed for the database location, DSN,and DMZ directories are gathered from the registry on the DMZ system. The values may beoverridden by using the command-line options.

The backup utility creates a backup file by copying all desired files, folder structures, and settings into atemporary directory, and then archiving the contents of that directory using either Zip or 7-Zip. The temporarydirectory is then removed at the end of the procedure. The following details the specific actions taken by thebackup utility:

To perform a simple restoration, you must first have completely installed MOVEit DMZ on your target system.For best results, the version of DMZ should be the same as the version that you backed up. (If this is not the case,such as if you are migrating your DMZ server to a new platform, and are upgrading to a new version at the sametime, you will need to re-run the MOVEit DMZ installation program after the restoration and choose the Repair option.Be sure to read our MOVEit DMZ Migration Guide ifthis is what you are doing.)You must also have transferred the backupfile to the target system. Once you are ready to begin the restoration, open a command prompt and cd to the Schedulersubdirectory of your MOVEit DMZ non-web directory. Next, execute the following command, making sure to substituteyour correct backup file path for the entry in the brackets below:

The restore utility will stop your webserver and database before actually restoring files. It will then decompressthe backup file to a temporary location and then copy the backed up files to their appropriate locations. Finally,it will restart the database and webservers. If you would like to see what the utility is doing while it runs, add the"--debug" command-line option to the above command. For a complete list of the options available in the DMZ restoreutility, see the MOVEit DMZ Restore Utility section below, or execute the following command in your Scheduler subdirectory: