Every time you apply a PPM to Central, the central first checks the PPM for build number. If the build number is higher at the same time compatible, then it applies the PPM. If the build number is (i) lower or same or (ii) higher but incompatible, then it rejects the PPM. The reason why higher builds that are incompatible cannot be applied is, over a period of time we would have released a number of PPMs. It becomes difficult to upgrade from a very old build (6005) to a new version (7200) as we would have done some changes on the design, tables etc. In such cases you have to upgrade to some intermittent builds (7000) before upgrading to the very latest build (7200).

Once you apply the correct PPM, the Central first takes a backup of the database and configurations and then applies the PPM. A pop will be displayed saying that the Central has been successfully upgraded to the build what you have applied. Now start the Central service. All the configurations done before the upgrade will exist post upgrade also. It is enough that you upgrade the central alone. The Probe and the agent automatically get upgraded themselves from the Central.

The Probe when contacts the Central also checks for the build number. If the Central has upgraded to a higher build, then it downloads the same PPM from the Central and applies to it. Similarly the Agent also (i) downloads the new agent exe file. (ii) uninstalls the old agent and (iii) installs the new agent. The configurations that were made before the upgrade will exist post upgrade also.

Click here to know the step by step process to be followed for applying the PPM

Backup:
During the upgrade the backup operation in MSP Center Plus is done automatically by executing a batch file called BackupDB.bat [\bin\backup]. Central service needs to be stopped before executing the BackupDB.bat. Once it is executed it takes a backup of the database as well as the configurations files that are in the Central. The time taken to backup the Central depends may vary according to the size of the database. Once the backup is completed, the backup file is saved as a .bak file under the backup folder.

In builds prior to 7002, once the BackupDB.bat file is executed, it creates a folder named central_backup_<date & time> in parallel to the Central directory and saves a copy of all the files in the Central. This model was more time consuming and was replaced with the earlier said method.

Attachments (1)

RSS of this page