{"id":1463,"date":"2015-06-01T16:09:55","date_gmt":"2015-06-01T15:09:55","guid":{"rendered":"http:\/\/emtunc.org\/blog\/?p=1463"},"modified":"2015-06-01T16:09:55","modified_gmt":"2015-06-01T15:09:55","slug":"can-you-snapshot-a-virtual-cisco-ironport","status":"publish","type":"post","link":"https:\/\/emtunc.org\/blog\/06\/2015\/can-you-snapshot-a-virtual-cisco-ironport\/","title":{"rendered":"Can You Snapshot a Virtual Cisco IronPort?"},"content":{"rendered":"<p>The Cisco IronPort virtual edition has been out for about a year now. It&#8217;s still not quite as mature as we would like for it to be; for example, it lacks support for Hyper-V, modifying the CPU core allocation to meet peak performance demands, etc.<\/p>\n<p>One of the unsupported &#8216;configurations&#8217; is virtual machine snapshots.<\/p>\n<p>This is what I was advised by a TAC engineer:<\/p>\n<p style=\"text-align: left;\"><em>&#8220;The software was written for physical hardware, and operations such as snapping an image and reloading it at a later point in time, is not supported.<\/em><\/p>\n<p style=\"text-align: left;\"><em>Our appliances often have files open, and taking a snapshot while a file is being written, can leave you with a worthless snapshot, that can&#8217;t be executed.\u00a0 And thats only one of the problems you may encounter<\/em><\/p>\n<p style=\"text-align: center;\"><strong><em>&#8230;<\/em><\/strong><\/p>\n<p style=\"text-align: left;\"><em>I can confirm it is not supported, but nevertheless it will probably work when the machine is completely shut down. It will probably fail when the machine was &#8216;powered on&#8217;. There are no power states like pause or standby which would take the filesystem into a state that would be safe for a snapshot.<\/em><\/p>\n<p style=\"text-align: left;\"><em>I can confirm, no problem if version mismatch due to a revert. A &#8220;revert&#8221; of the machine (CLI&gt; revert)\u00a0 also results in such a mismatch, but this is automatically resolved.&#8221;<\/em><\/p>\n<p>So as you can see, snapshotting your ESA isn&#8217;t technically supported HOWEVER if you follow the basic steps below you shouldn&#8217;t have any issues.<\/p>\n<p><!--more--><\/p>\n<ol>\n<li>Gracefully shut down the ESA<\/li>\n<li>Snapshot the VM<\/li>\n<li>Start the vESA &#8211; make any changes you wish<\/li>\n<li>Restore the snapshot if you run in to problems otherwise delete the snapshot<\/li>\n<\/ol>\n<p>Please note that VM snapshots are not a replacement for configuration backups &#8211; you should still be backing up your vESA config on a regular basis!<\/p>\n<p>The great thing about Cisco TAC is that they will try their best to help you even if you are running an unsupported configuration &#8211; however there&#8217;s only so much they can do before closing the ticket with reason: unsupported configuration \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Cisco IronPort virtual edition has been out for about a year now. It&#8217;s still not quite as mature as we would like for it to be; for example, it lacks support for Hyper-V, modifying the CPU core allocation to meet peak performance demands, etc. One of the unsupported &#8216;configurations&#8217; is virtual machine snapshots. This [&hellip;]<\/p>\n","protected":false},"author":32,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"categories":[1],"tags":[135,136],"class_list":["post-1463","post","type-post","status-publish","format-standard","hentry","category-tech","tag-cisco-ironport","tag-esa"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p1trTO-nB","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/1463","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/comments?post=1463"}],"version-history":[{"count":5,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/1463\/revisions"}],"predecessor-version":[{"id":1468,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/1463\/revisions\/1468"}],"wp:attachment":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/media?parent=1463"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/categories?post=1463"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/tags?post=1463"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}