...
- Copy the exported zip file to a Kubernetes shared location in the PVC.
Open the restore.xml located at <shared>/migration/template/restore.xml.
Info shared is the folder created at the root level in the PVC when you deploy Adeptia Connect. - Provide the path of the exported zip file in the <SourceZipLoc> tag of the restore.xml as illustrated below.
- Open the values.yaml file.
- Enter the path of the restore.xml file in the environment variable MIGRATION_XML_FILE_PATH.
Run the following command to restore the objects.
Code Block language css theme Midnight helm upgrade -i migration adeptia/migration -f adeptia/values.yaml -n <NAMESPACE>
Redeploy all the accelerators (the bundled accelerators, and the drivers).
As In AC v4.0 environment, the server-configure.properties, and other properties files do not exist in the microservices environment, the system generates a .csv file with the name Config_Report_<name of the exported ZIP>. This file helps you identify which all properties of server-configure.properties file from AC v3.5 have been converted to environment variables and placed in the values.yaml file. These properties coming from the AC v3.5 environment are handled in the following manner in AC v4.0 (microservice) environment:
...
Some of the properties have become environment variables.
Info You can find the list of these environment variables in a .csv file that is generated by the system after performing the restore operation. You can refer to this file to make the changes in the values of these environment variables (converted properties) in values.yaml file.
...
The file has the following name format. Config_Report_
...
<name of the exported
...
ZIP>. This file is created in the same folder where the exported ZIP file is located in the PVC. - Some properties are moved to database with the same name or different names.
- A few properties are deleted.
- The remaining ones are bundled with the application.