The-Asterisk

In just over a month's time, this nation has gone from high-flying normalcy to a grim situation which I believe has not yet reached its nadir. The US stock market has lost one third of its value, infections and deaths from the corona-virus have increased and, at the recommendation of Federal and State authorities, massive numbers of business have essentially shut down. At least four states have declared a state of emergency whereby only critical and essential businesses may operate. I expect that many other states will soon follow. That would be a sad and irresponsible move by the governors of those states. The authorities are in a precarious position, wedged between political correctness and the inevitability of "not doing enough, soon enough". I understand this. Mass and instantaneous media makes their decisions much more difficult with pundits, frightened citizens and the toxic Twitterverse questioning their every decision and blaming them for every slip and blunde...

Over the past several weeks, I have been working with on learning Veeam backup solutions. Veeam's approach is a bit different and their nomenclature is much different from other backup products, perhaps owing to their European roots. They also have a confusing licensing structure. Combine the nomenclature differences, the licensing complexities and the myriad of applications it takes to run the product and it creates, to me, a steep learning curve. That said, Veeam is an effective and affordable Enterprise-grade product. I had installed Veeam Backup and Replication on a test server several months ago. After working with it for a while, I abandoned the project ("Squirrel!!!"). I came back to it a couple weeks ago and began my effort by downloading and installing the latest version. When the installation of Veeam Backup and Replication (VBR) neared completion, I got an error. It was a popup on the screen which said " Failed to create database VeeamBackup. Create ...