I wasn’t aware of this until recently, so it was a good thing to find…..
In Simpana 10 a number of Pre-Check Operations performed during the push of Updates from the Commserve are disabled by default.
Those Pre-Check Operations are outlined below;
- Client connectivity check – Verifies whether the client can communicate with the CommServe.
- Disk space check – Verifies whether the client has sufficient disk space for the updates to be installed.
- Package synchronization – Verifies whether the updates are already installed on the client.
Of course since one of them is Disk space check, imagine what happens during an SP push update to a Unix client whereby you don’t have enough disk space to perform the Update operation on client. The client may end up corrupting the existing Simpana software on the client due to the SP update failing due to lack of space if it gets enough of the way through the progress. I saw this first hand recently on a client.
The regkey to set that will enable the Pre-Check Operations to be performed in the future is below;
I confirmed that Pre-Check Operations didn’t occur as I saw the following log lines during my Push of an SP against a client. The log named below is found on your Commserve.
6196 3914 12/17 09:45:47 4825406 [UpdatePatches]() - Initiating update patches on client
6196 3914 12/17 09:45:47 4825406 [UpdatePatches]() - Skipping disk space check for client to reduce client connections
As always, if my post helps you in some way, please drop me some feedback by way of a comment. Love hearing from people.
Source: Simpana 10 – Books Online Documentation.