Microsoft Windows Server are very great products to work with. And,... being a Microsoft Certified Trainer,..  I like to share new knowledge with the rest of the world for free on this website. So, the initially set up was for my own references, but now I share it with you. Enjoy it !! Due to the fact that a big percentage of visitors of this page are international based, this article is in the English language.


Last week i was asked to look into some backup issue's with several (on premises) customers. As I just enjoyed a very nice holiday in southern Europe, I started very relaxed on the first issue's.  
The main overal problem was the fact that "Snapshots" where not correctly removed from the virtual machines after the backup.

I investigated this thoroughly and eventually found a solution that I would like to share with you all through this article.

The errors related to this article:
Some of the related faults I noticed are shown below. I added them to this article in the hope that all you engineers can benefit from this and are able to find this article better through search engines.

  • A VSS critical writer has failed. Writer's state: [VSS_WS_FAILED_AT_FREEZE]
  • [VimApi] Create snapshot, ref "vm-xx", name "VEEAM BACKUP TEMPORARY SNAPSHOT", description "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "False"
     

Googling around did not bring very much. An article on the Veeam site only suggested that I migrated the effected server to another datastore as disk latency did not allow the creation of the snapshot in a timely matter. I believe it is article 1337 I believe. 
Something simular 


Migrate server to the quicker datastore as latency on the current one does not allow create Snapshot in timely manner.
This is rather undocumented until now, but I spoke with engineers from Veeam and Commvault about this and they unofficially agree with my theory and solution. I won't be surprised if this will become a "General/Common" solution for them in the future.

 


Now, there is a large amount of scripts available on the internet, but often, 
a certain powershell version is required, depending on the commands etc. etc..
Now how can you determine your installed powershell version in a fast and efficient way?

You can find your version by opening the regular Powershell module an just type Get-Host Toepasbaar op: Windows 2000 server alle edities, Windows 2003 server alle edities, Windows 2008 alle edities.



How do you start this:
Press the "Windows-button (the flag) and type PSR (full name is PSR.exe, short for Problem-Steps-Recorder). his program can also be found in the Controle Panel but thats a lot of clicks and we don't want that. The "Steps Recorder" tile will appear and at this point you are also able to pin this appilication to your start-menu. Hit "Enter' and a small (tool)bar will appear a little less above the left middle of the screen. This is all very easy to use, everyone will understand the meaning of "Start & Stop record". It is possible to add a comment as well between the screens. Another point is the ability to record, by default, your second screen at the same time. There are not a lot of screen utilities which can do that... 



After stopping the recording you must provide a location and name for the ZIP file to save. Go there with the explorer and open the ZIP file. Within it you see a MHTML file. Open it, the default is internet explorer, and see all the screenshots, key-strokes an actions that has been done before. As it is in, the relatively unknown, MHTML format, you can go through the file with the use of "Next" and "Previous" options which is very handy. Until now, i have advised to use this program mainly for the next 2 purposes.

  • Mail the ZIP file as an attachment to a helpdesk or someone who can help you with a specific problem. All actions has are being recorded, as well as all the key strokes. A complete story, in which there are now doubts as everything is visible and clear.
    Example snapshot error vSphere







  • Use the MHTML file for import in Microsoft Office Word, or copy/paste it into another program. This can be used as a very good basis to create a manual, guidelines or a procedure. Very handy and error reducing as every actions is allready present.


An example of the ZIP and theat it, and start using this beautifull buildin feature!


Tip 1:
 Pl 


I hope this article has helped you, and getting you enthusiastic for Windows 8 as much as I already am!
 

 

 

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Ben OostdamBen Oostdam has been working with Windows systems since 1993. Worked for several companies as a system administrator, and is currently a Senior Support Engineer for a large company located in the Netherlands.

Disclaimer: The information contained in this website/article is for general information purposes only. The information is provided as is, by Ben Oostdam and while we endeavour to keep the information up to date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk. In no event will we be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website. Through this website you are sometimes able to link to other websites which are not under my control. I have no control over the nature, content and availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views expressed within them. Every effort is made to keep the website up and running smoothly. However, I take no responsibility for, and will not be liable for, the website being temporarily unavailable due to technical issues beyond our control. All entries in these articles, are my individual opinion, or from co-writers and they don't necessary reflect the opinion of my employer.

 

Tuesday the 16th, July 2019. All rights reserved.. // Oostdam WebDesign