Home > Data Protection > PowerProtect DP Series Appliances > White Papers > Integrated Data Protection Appliance: Configuration Best Practices > Installing the IDPA preinstallation patch
Before you configure the DataProtection-ACM virtual machine, install the latest IDPA preinstallation patch if it is available.
For example: Idpa_pre_update_N.N.N-nnnnnn.zip
In this example, N.N.N is the latest preinstallation patch version, and nnnnnn is the build number.
Note: You must install the preinstallation patch before you connect to the DataProtection-ACM using a browser for the initial configuration.
The following steps describe how to install the preinstallation patch on the DataProtection-ACM.
# rpm -qa | grep dataprotection
The .zip file contains the Idpa_pre_update_N.N.N.nnnnnn.tar.gz patch and an associated ReadMe.txt file. N.N.N is the latest preinstallation patch version, and nnnnnn is the build number.
Note: For more information about installing the preinstallation patch, see the ReadMe.txt file.
The following image shows a sample WinSCP session configuration window.
The following image shows the Putty configuration screen for DataProtection-ACM.
The default password for the root user is Idpa_1234.
rpm -qa | grep dataprotection
cd /tmp/patch
tar -xvf Idpa_pre_update_N.N.N.nnnnnn.tar.gz
The contents are extracted to a subdirectory named Idpa_pre_update_N.N.N.nnnnnn.
cd /tmp/patch/Idpa_pre_update_N.N.N.nnnnnn/
chmod +x install.sh
./install.sh
Messages are displayed on the screen during the installation process. If the following message displays, disregard the message:
“warning: file /usr/local/dataprotection/var/configmgr/server_data/config/ InfrastructureComponents_Template.xml: remove failed: No such file or directory” “warning: file /usr/local/dataprotection/customscripts/Config.properties: remove failed: No such file or directory”
rpm -qa | grep dataprotection
Note: If the following message is displayed, see the KB article IDPA 2.3.0.623733 Pre-Patch pre-requisites and workarounds (535790) to resolve the error:
“Successfully validated build number of hotfix with current build number. This hotfix is not applicable at the current state of ACM.“