For any errors related to Backup Exec Database encryption key (.As security vendor Symantec (SYMC) pulls itself out of the cloud-based backup and recovery services business, former rivals are pouncing on the opportunity to migrate Symantec customers. Click Ok to import and restart the BE services. In both prompts, browse to the Desktop\Data folder and select the BEDB data base files. In the Right Column, Right Click on the New Server and select Copy Database. Under the middle column, select All Media servers. Locate the BEUtility.exe file under the Backup Exec folder and execute it. 
From the Data Folder on the desktop of the New Server, copy the Backup Exec Database encryption key (.dek) file to the \ Program Files\Symantec\Backup Exec\Data\ folder. From the Data Folder on the desktop of the New Server (copied to the desktop in Step 5), copy all BEX files to the \Program Files\Symantec\Backup Exec\ Data folder (only BEX files). Copy the Catalogs folder from the desktop of the New Server (copied to the desktop in Step 5) to the Backup Exec folder on the New Server. On the New Server, rename the Catalogs folder to Catalogs.old. On the New server, stop the Backup Exec Services from "Tools | Backup Exec Services | Stop All Services". Path:- Program Files\Symantec\Backup Exec\ Copy the Catalogs and Data folder from the Old server to the desktop of the New server. 
On the Old Backup Exec Server, stop the Backup Exec Services from "Tools | Backup Exec Services | Stop All Services" and also stop the "SQL Service forīKUPEXEC instance" from Windows Services Console. 
On the Old Backup Exec Server, Export the encryption key using the steps mentioned in Exporting the Backup Exec Database encryption key
For Backup Exec 15 and later, sensitive information in the Backup Exec Database is encrypted. Make sure Backup Exec is working fine as a clean install on the New server. 
Install Backup Exec for Windows Server on the New Server.Before the existence of the Backup Exec Migration Assistant, the following
0 kommentar(er)
