Older log files will be removed and other types of older debug informationĬleaning up database will stop the server while the cleanup is performed. The clean up can remove all files located in the backup staging directory. Here is how you could do the disk cleanup prime/admin# ncs cleanup ![]() ![]() You can check your CPI database utilization as below (optvol is the one holding CPI database which is running out of space) prime/admin# rootįilesystem Size Used Avail Use% Mounted on Within a day that space consumed by the database and constantly getting above alert. As suggested, did a “disc cleanup” and that helped to recover ~25G. ![]() When checked in CLI, PI database size is 638G (97% of allocated space ). Within 2 months of the upgrade, got to below alerts stating CPI running on low disk space. When I upgraded CPI 2.2 to CPI 3.0 most of the settings left as default unless those were changed in 2.2. Of course you will loose historical data and has to do manual work, still worth doing. If you have worked with this product, many of us know “ do a fresh install and import maps” is the safest approach for a Prime Infrastructure Upgrade. ![]() That time I chose to go with inline upgrade as it was supported. Couple of months back I upgraded our prime infrastructure to 3.0 from 2.2.
0 Comments
Leave a Reply. |