What Are Your RTO And RPO?
I just had a meeting with one of Alvaka's IT consultants regarding the development of a disaster recovery and business continuity plan for a financial services client of hers. A year ago the client had a very nearly disastrous weather related IT event that could have slammed the whole company beyond imagination. During a heavy downpour a major leak opened up on the roof and dumped significant amounts of water right onto the client’s primary server rack. The servers were so flooded that during the recovery process the techs actually had to de-rack the servers and tilt them over in order to pour out the water. Full disaster was averted when
Smoke testing is a term used to describe the testing process for servers after patches are applied. 
Estimating an average time for patching servers and PCs can be a bit tricky. It can vary from one month to the next, depending upon the number and complexity of the patches released by your software vendors. You must consider all versions of operating systems and have a complete inventory of all your application software to do this job correctly. Our experience has shown that manual patching of systems takes on average of about 1.5 hours each.
This is a basic cost calculator for you to compute your typical monthly cost for patching your servers, PCs, laptops, tablets and associated application software. It also forms the basis for you to begin calculating your Return on Investment for software patching, or for comparison with alternatives to the manual process of patching operating systems and application software—such as Patch Management as a Service, also known as Vulnerability Management as a Service.