Portal Home > Knowledgebase > Articles Database > Patching and Roll-back Strategy
Posted by YUPAPA, 03-22-2014, 12:44 PM I'm wondering whats your strategy when it comes to patching your server regularly? By patching I mean you upgrade the packages on the server. As you know there are dependencies when you upgrade / remove packages. How would you go about downgrading back to the previous state while keeping all the dependencies intact? The plan I've been using is to split mirror when we patch. I'd like to know if you or there is a better plan for it?
Posted by Isaac Newton, 03-22-2014, 11:54 PM Well, it depends on the lot of the type of environment one has. Let me share my two cents: If I'm on Vmware VM, I always take a snapshot first before applying any kind of DB patches. If it is file level fixes/patches, I just take a backup of the files or directories it would replace. Ideally, we shouldn't find ourselves in a situation where we have to rollback any patches on the production environment, which means, proper testing has to be done on testing environments/QA .
Add to Favourites 
Print this Article
