Easy2Patch Backup & Restore

Scope: Easy2Patch 4.0

Backup Easy2Patch 4.0

It is important to back up the Easy2Patch software periodically. This backup will allow the failed server to be restored. With backup, all configurations, certificates, and software inventories sent to the ConfigMgr/WSUS/Intune system are protected. The data that needs to be backed up and how to back them up are explained below.

There are 3 backup parts: These backups will be taken under a single folder and this folder will be backed up by the central backup system. If the backup of the server used is taken apart from manual backup, all components can be recovered at once. The backup steps and files to be backed up with manual or specially created jobs are explained below. The order of operations is not important. Although it is not necessary to stop the service, it is recommended to stop the service so that the data does not change.

1. Download folder containing downloaded 3rd Party software.

2. Code signing certificate

3. Database

Stop service from Schedule Pane

Backup Downloaded Files

The 3rd Party installation files downloaded by Easy2Patch are located in the address specified by Download Path under General Settings. There is a folder named Download in the root directory of the selected drive. This folder should be backed up.

C:\ Drive used for downloaded files

Backup Code Signing Certificate

The Code Signing certificate used by WSUS must be backed up in case it needs to be signed again after rollback. This certificate is located in the LocalMachine\TrustedPublishers container and must be backed up with the private key.

Export Selected Certificate

Backup Database

Easy2Patch 4.0 stores all configuration data in the SQL Server database. Important data such as information about deployed applications and superseded relationships between resubmitted applications are stored in the database. Database backup can be taken with a job you define on the SQL Server agent, manually or with backup software. The backup file with the bak extension should be stored in a separate location with other backups. The following SQL script can be used to take backups. You should change the C:\SQL\BACKUP path to a folder path in your environment.

BACKUP DATABASE [Easy2Patch] TO  DISK = N'C:\SQL\BACKUP\Easy2Patch.bak' 
WITH NOFORMAT, INIT,  NAME = N'Easy2Patch-Full Database Backup', 
SKIP, NOREWIND, NOUNLOAD,  STATS = 5

Restore Easy2Patch 4.0

After reinstalling Easy2Patch for various reasons, it is necessary to restore old data. When you restore the data, the system will continue where it left off. For this purpose, you need to perform a normal Easy2Patch installation before the restore. It should be noted that if Easy2Patch is installed on a newly installed operating system (different from the server it is licensed for), the license will not come with the restore. In order for the license to be activated, [e-mail] or [e-mail] must be contacted. The following backups should be restored in order. As in the backup, the service should be stopped during the restore. The service should be restarted after the operations are completed.

• Download folder containing downloaded 3rd Party software.

• Code signing certificate

• Database

Installing Easy2Patch 4.0 on a New Machine

Install Easy2Patch 4.0 software as if you were doing a new installation. If the database is already installed on SQL Server, you should delete it. Complete all your configurations with the FTW wizard that will be run after the installation. For installation procedures, see. Installing Easy2Patch 4.0.

Restore Downloaded Files

The backed up download folder is copied to the root directory of the drive selected on the settings screen. For example: D:\Download.

Restore Easy2Patch Database

Easy2Patch database must be restored from SQL management interface. The following T-SQL can be used for restore. If a backup was taken with a backup software, the restore process must be done through this software.

The T-SQL script that can be used for Manual Restore will be as follows. Change the path of the backup (bak) file according to your system.

The SQL Server version must be equal to or higher than the version of the backup system. Otherwise, you cannot restore the database.

USE [master]
ALTER DATABASE [Easy2Patch] SET SINGLE_USER WITH ROLLBACK IMMEDIATE
RESTORE DATABASE [Easy2Patch] FROM  DISK = N'C:\SQL\BACKUP\Easy2Patch.bak' WITH  FILE = 1,  NOUNLOAD,  REPLACE,  STATS = 5
ALTER DATABASE [Easy2Patch] SET MULTI_USER
GO

After the database restoration process is completed, you can complete the licensing process.

Restore Code Signing Certificate

Finally, the code signing certificate must be imported. Click the import button under Settings\Management\Certificate, select the backed up code signing pfx file, and enter the certificate's password to complete the process.