The initial book will cover Veeam Monitor, Veeam Reporter and Veeam Backup & Replication. I’m going to try to squeeze in as much of my perception of what these products are and do.
Also I have created a dedicated site http://book.veeam.co.uk where you’ll find (when the book is published) any corrections or updates to the content. I’m some months off completion and I’ll probably try to self publish but seen as I’m at the half way mark its time I told you all.
If you want to talk about it you’ll find me at: firstname.lastname@example.org or @rickyelqasem
Popularity: 5% [?]
Ok I have to make my apologies about this section, it’s been sometime that I have continued these PowerShell Lessons and the reason for that was I was waiting to get my hands on a new PowerCLI book.
So now I have a copy I think it’s time for me to once again start these lessons up again and hopefully learn a trick or two from this book. However I still plan to focus on core fundamental PowerShell code for now and try to drop in the odd PowerCLI usage.
In this Lesson we’ll look at spaces, wildcards, escape characters and how they can be used in PowerCLI.
In PowerShell a space is seen as a delimiter between variables and parameters so a typical problem you may run into is when you are querying an object like a VM that has a space in the VM name. vSphere allows you to use the space character in the VM name for example WinXP Test 1 is a legal name for a VM. However if you try to manipulate this VM buy inputting the VM name as is PowerShell will not know that WinXP Test 1 is one piece of text and will fail or will only use the first part of the text WinXP. To get around this just place the text in quotes, so the VM name would be inputted like so:
You can also use single quotes too ‘ but what if you need to input the quotes/single quote symbol as a legal character which is part of the VM name like: WinXP’1 well the answer is simple just surround the VM name with the other quote character. So in our case it would look like this:
Ok so what about wildcards? If you were/are familiar with DOS command-line or another shell environments like bash for example these shells often provide a way of performing a query on a group of object opposed to a single object that have common characters in the name of the object. So for example we may want to search the list of VMs that begin with the character ‘v’. To do that is very simple we just enter the asterisks symbol * after specifying the character we want to search on. Here’s an example where we list out only VMs that begin with the letter v:
And we are not just restricted to searching against 1 character. This next example shows we can query with 2 characters.
We can use a different wildcards to specify that the query should list out only objects that have a letter at a specific position by using the ? wildcard. So in the above example we could have done the below to list out VMs where the second character is ‘l’ like so:
We can also use the  wildcards to:
specify a range of characters Get-VM – name [m-z]Lab* which would list out any VMs that started with any letter from M to Z and ends with Lab
specify multiple characters Get-VM –name [uv]Lab* which would list out any VMs that started with letters U or V and ends with Lab
One last thing I want to show you is the use of the back tick symbol `. One thing PowerShell will allow you to do is escape out of the command line so the structure of the command line can be presented over multiple lines. So coders do this to make it easier to see how they form a command line. Instead of trying to do all on one line we can use the ` to bring us down a line. From here we enter more of the command line and if we want to start another new line we just hit enter.
Each new line is started with >> prompt but when you have finished just hit enter one more time on a empty line and the command will execute.
I hope you found this useful. And I promise to bring you more of these lessons in the very near future.
Popularity: 12% [?]
Not sure how long you have known me for but when I started this blog 2005/2006 I blogged about a software ISCSI solution called Starwind from a company formerly called Rocket Division (Now Starwind Software). Well the guys over there were kind of enough to give me an NFR of their product as I was going to need a ISCSI solution whilst delivering VMware training courses. VMware was just preparing to release VI3 and I knew it had better ISCSI capabilities so I needed a cheap solution fast and very cost effective. Free was a good start and I even installed it into a VM so I didn’t need hardware for my usage.
Anyway that is history now and over the last few years Starwind has been adding more and more enterprise features to its product and even releasing a free version (wonder where they got that idea). I think it’s about time I got familiar with Starwind again. They recently added the following features:
- Host operating systems: any modern Microsoft Windows OS is supported.
- Works with all the leading Hypervisor vendors: VMware, Microsoft, VMware.
- Data De-duplication (fully supported, variable block size). Data Deduplication is a specialized mechanism of data-reduction, reducing storage capacity requirements by eliminating duplicated data within and between files.
- Unlimited storage capacity & Unlimited number of supported concurrent iSCSI connections.
- Full Production use is allowed.
- Support. Free version is covered with a basic support plan (an open public community forum). Support upgrades are available for paid per-incident plans or switching to any commercial version with extended functionality where an annual support plan is included.
- Caching. StarWind has a multi-level cache mechanism implemented. The cache can use gigabytes of RAM and converts it into to extremely fast level 1 write-back or write-through cache, providing superior storage performance over many conventional SANs.
- CDP (Continuous Data Protection) and Snapshots that are completely compatible with VSS (Volume Snapshot Services).
- VTL (Virtual Tape Library) and WAN replication are offered as paid upgrade options.
- iSCSI boot is fully supported with iSCSI boot capable NIC.
If you are interested too then click > HERE < to find out more.
Popularity: 3% [?]