VMware vSphere Labs – Foundations – First Series

Well, I have decided to dub my basic intro into VMware workstation labs as “Foundations” . I, like many others, enjoy discussing and learning about everything. Storage, networking, what I want to achieve, what I am designing for, name a few things you will have to consider in your lab. Sure, there is the easy stand up a lab slap some storage on it, run ESXi, Build vCenter, but for the few, the proud, and the pros… we like to cover it all. This series is pretty much going to go through every bit of that. Yeah, every bit… even the crumbs from the table. So here is the outline and obviously post videos and notes on each. Duly note, that at any time I may add a few dozen more post to foundations as I embark on this journey. I am looking forward to it and I hope you do as well! (Perhaps when I get to it I will do some CommVault vs. Veeam videos when I get a chance – OH, the drama!)

1. The different kinds
2. The Downloads and what you need to know
3. VMware Workstation Storage Considerations
4. Networking Considerations and Design
5. Installing Custom VMware Workstation 8
6. Creating you windows 2008 R2 template VM in VMware Workstation 7 and 8

Yeah, I know who would’ve ever thought a lab took this much thought. It’s just good stuff to think about and if people are board well you got something to do or watch. By the way, some videos have some music others don’t. Again feedback always appreciated!

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

VMware vSphere Labs – Foundations – VMware Workstation Storage Considerations

This video informs you of what you may or may not know about the different types of storage you can use for your VMware vSphere lab set up. Things like physical iSCSI and NFS and Virtual Storage Appliances (VSA) are important to know about and some are MIUCH cheaper than the other.

Links Show in the video:

http://www.techhead.co.uk/how-to-configure-openfiler-v23-iscsi-storage-for-use-with-vmware-esx
http://go.iomega.com/en-us/products/network-storage-desktop/storcenter-network-storage-solution/network-hard-drive-ix4-200d-cloud/?partner=4760
http://nickapedia.com/2010/05/01/celerra-vsa-uber-smaller-faster-easier-geekier/
http://thehyperadvisor.com/?p=934
http://www.vmware.com/products/datacenter-virtualization/vsphere/vsphere-storage-appliance/overview.html

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

VMware vSphere Labs – Foundations – Networking Considerations and Design

This how to will go into some detail of the Networking consideration for your VMware Lab. It’s all in what you want to do.

This video addresses those considerations and provides some details on how you may want to do that. If you want some resources for particular lab setup head on to the bottom.

Another Lovely Video

Networking (As seen in the video if you want to reproduce

1. Management Stack for vCloud :
2. Production stack for tenants:
3. VMnet1  192.168.240.xxx – ESXi Management Host-Only (isolated for security )
4. VMNET2 192.168.238.xxx – iSCSI (vmkernal port group and NFS will be shared)
5. VMNET3 192.168.237.xxx – vMotion
6. VMNET4 192.168.5.xxx – VM Networks for ESXi host
7. VMnet8 192.168.4.xxx – Production-MGMT

   .10 = Domain Controllers

   .20 = vCenter Servers (2 interfaces one for ESXi MGMT and Production)

   .30 = All Other systems

8. VMNET5 192.168.120.xxx – vCloud Mgmt

Other Wonderful Links on vSphere Labs and Networking Design included are SRM and vCloud Director Setups:
http://nickapedia.com/2010/10/07/lights-camera-replication-uber-srm-video-guide/
http://www.hypervizor.com/2010/09/video-guide-taking-vmware-vcloud-director-for-a-spin-and-on-the-go/
http://www.yellow-bricks.com/2010/09/13/creating-a-vcd-lab-on-your-maclaptop/
http://blog.tsugliani.fr/featured/create-your-own-virtual-vcloud-lab-part-1/
http://www.chriscolotti.us/vmware/vsphere/vmware-vcloud-in-a-box-for-your-home-lab/

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

VMware vSphere Labs – Foundations – Downloads and knowing what you need

This video just covers the basics of what you need to download to get your vSphere Lab up and going. For more this video isn’t useful but it does address understanding Trials, how to access to products, and etc. This is covering a VMware Workstation 8 Lab set up.

Basically here is an overview of what the video covers:

1. 60 Day Trials
2. The Value of Partnerships
3. Understanding the foundation and products for building your lab
4. What to consider from a product stand point
5. #VMTNSubscription Movement

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

VMware vSphere 4 and 5 Labs – Foundations – The different kinds…

To Build a lab:

I have been thinking a lot about how there seems to be a few gaps in the VMware community when it comes to learning to set up a VMware vSphere lab environment. So I thought I would take the time to try and put together a full on post dedicated to resources on building a VMware Lab. When I first thought about this I wasn’t sure if I wanted to do a full A-Z build. Covering every single feature or deployment, but often times I would rather not re-invent the wheel. There are MANY post covering how to do this in general but I wanted to make a point of identifying the types of labs that you can set up and how to exactly go about it as well. The key word is “lab” so you don’t want to spend a ton of money (unless you have it) on your lab. To start off there are a multitude of setups you can do and many ways you can do it. I also want to stress that if you are getting ready for your test then YOU need to have one of these labs.

vSphere Lab video 2 Cents and quick overview! (this is my fist video post)

Nested VMware vSphere Lab

1. Hosted on a Desktop Virtualization Product Like VMware Workstation 7 or 8
2. Allows for easy HCL compliance
3. Does require a robust desktop
4. Can get slow depending on what you’re doing (design)
5. Networking is all virtualized (plus)
6. Storage can be virtualized or something like iSCSI can be used
7. Mobility (can move VM’s around between desktops and laptops)

Physical VMware vSphere Lab

1. Runs ESXi as bare metal
2. Is more expensive
3. “Real World” set up so is truly a lab
4. Must meet HCL
5. Will need Physical Networking (Managed networking highly recommended)
6. Takes longer to build out or rebuild
7. Can run nested labs on top of ESXi (pretty much using ESXi in the way you would use VMware Workstation)
8. Storage can be virtualized or something like iSCSI can be used
9. Can move hosted VM’s but the physical systems are not portable/mobile (depends I guess)

In a nutshell I will be covering the nested set-up since that seems to be the less expensive rig. I also love the fact that I can move it around to my laptop and desktop which is quite handy. Also fairly easy to backup as well.

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

VMware Certified Professional on vSphere 5! – My Experience

On January 31, 2012 I officially passed my vSphere 5 exam and I am now a VCP 5. The test was very interesting indeed. You hear all sorts of rumors and things of that nature before you take it. I have made a post previously HERE. This pretty much covers everything you need to know. I don’t think I can discuss testing material but what I can tell you is learn a lot about the components of vSphere 5 clustering. Also learn about the Pros and the Cons centered around all the vSphere 5 features.

The test in of itself was actually harder than the vSphere 4 test I took over a year ago. I was also a lot more prepared and had some pressure on me to get it done because I wouldn’t have to pay for training. I would encourage that if any of you are familiar with vSphere 5, Been running it in a lab, and constantly learning new features, know vSphere 4.1 well, then I would go ahead and go take the test. Reason being is that you can end up spending more money waiting to take it later when you can possibly pass it now. Most companies are also going to be more willing to reimburse the expense of an exam then to actually spend money on an course.

Notice my comment on 4.1. Previous VCP were based off of 4.0 only. If you are really familiar with 4.1 then you already have a good lead into the knowledge base of 5.0. If you are a VMware partner then head to the partner portal and take some other course ware related to “What’s New” in vSphere 5. I did pretty good considering the amount of time and the pressure. I would definitely vote on subscribing to the latest VMware Certified Professional on vSphere 5 brown bags over at Cody Bunch’s site.

Either way, now that I have my VCP 5 out of the way I can hopefully attempt to get some advanced certifications around vSphere 4 taken care of.

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.org and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

CommVault Simpana 9 Vs. VEEAM 6 Round 2 “DING!!” – Features – VMware Backup

CommVault Notes are currently ommitted for the time being:

The Bad:

VEEAM:

1. vCloud Integration is supported but “lacking” for a better term (requires some manual work)
2. Apparently doesn’t have the best dedupe (Is still debated I believe)
3. CPU based (Socket) licensing (You know what your getting upfront. No additional cost when compared to A la      Carte or Capacity)
4. No Physical backup (yeah, yeah, we all know that)
5. NFS best performance is a Linux installed OS with NFS mounted for a target
6. Not a TON of features or granularity as it seemed to me when compared to commvault. CommVault just      has a ton of bells and whistles. (Can be pro or con)

The Good:

Similarities: (Yes you can correct me here if you like)

1. Both can scale out (CommVault uses Media Agents and Veeam uses Backups servers and repositories
2. Offer Central Management Solutions
3. Both do SAN based backups (LAN-Free, snap protect, whatever you want to call it)
4. Load Balanced Based Backups (Media agent in CommVault can do this and Veeam does it with Backup Proxies)
5. Both have certifications on various storage arrays for the SAN-Based backup
6. Both have VCD support but not completely automated restores (I do see this hopefully changing)

VEEAM

1. Very Simple Basic approach. In some ways this can be good or bad but the fact it has a simple approach was nice this makes it easier for people to learn and use.
2. Restores super easy (single click)
3. Can install easily as a single instance (all in one backup server) or scale out for enterprise wide deployments (NOTE:easy)
4. Backs up Object Level without an agent (This is a nice plus no agents = no special networking)
5. Can Dedupe to a NFS (Dedupe) Media Target (not sure how but they say they can do it, please correct me if I am wrong)
6. Licensing is CPU sockets based so you can now what you are licensed for. (Can be more than an ala carte version of CV. However I would think would be cheaper in most instances)
7. Can verify and test backups in a sand box environment (i.e. send an email from an exchange server)
8. For whatever reason we had no snapshots left by Veeam ever… really nice.

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

Cisco UCS Journey – When to update firmware

Don’t update if its not broke. If it breaks then update it. If you have issues with false alerts you may want to update firmware. I saw this with 1.4j.

The issue is not with the IOM but with the chassis communication bus(i2c bus) and hence the IOM is not getting detected and backplane ports never come up. If you seeing alerts related to PSU and those types of things then you may want to pay attention.

I2C is a bus that provides connectivity between different components in the chassis.

The PCA9541 is an I2C part that helps us control access to the shared devices in a chassis; the chassis serial eeproms, power supplies, and fan modules.

The 9541 I2C mux has known hardware/hang issues that can cause failures to access hardware components on the chassis. This can result in failures to read fan and PSU sensor data (such as fan speed and temp), triggering faults to be raised for the component (such as fan inoperable).

Some early PCA9541s that were used have a bug that if they are switched back and forth between IOM1 access and IOM2 access too quickly, they will get stuck and not allow any connection to the devices behind them.

Action Required:

Required to upgrade firmware version to 1.4(3q) or above.

Workaround to be followed before going for firmware upgrade:

• Reseat all the PSUs one by one in the chassis. Wait for 10min after inserting one unit ,so that it could stabilize.

• Reseat all the Fan Units on the backside of the chassis. Wait for 3min before going for the next one.

• Reseat both the IO modules. Wait for 20min before going for the next one.

• Verifying the i2c counter for the chassis.

• (Requires Down Time)Power cycle to reset all counters to fix issues in the running version.

• (Requires Down Time)Upgrading to firmware version 1.4(3q) or above (2.0 release) for a permanent fix.

Please follow the link to download the 1.4(3q) bundle:

http://www.cisco.com/cisco/software/release.html?mdfid=283612660&release=1.4%283q%29&relind=AVAILABLE&softwareid=283655658&rellifecycle=&reltype=all

Related Issue with firmware version used:

Incorrect behavior of I2C bus or CMC software interpreting I2C transactions?

1. Fans (count 8 or less), PSU (count 4 or less) can be reported as inoperable. State never cleared.
2. Fans are running at 100% rotation rate.
3. UCSM cannot retrieve the PSU/Fan part detailed information
4. Transient errors indicating Fan inoperable, cleared in one minute time interval.
5. LED state does not match faults reported in UCSM and actual health of the system.
6. Incorrectly reported thermal errors on blades and chassis .

Fixes that are promised for 1.4(3q):

1. CSCtl74710 I2C bus access improvements for 9541

PCA9541 (NXP I2C bus multiplexor) workaround to improve bus access for parts built prior of mid 2009. The workaround assures that if internal clock fails to #:start it gets retried. The change designed and works as expected for both PCA9541 and PCA9541A parts from NXP. PCA9541 parts due to the internal clocking bug #:had a high number of bus_lost events.

1. CSCtn87821 Minor I2C driver fixes and instrumentation

New Linux I2C driver has optimization to handle I2C controller and slave devices synchronization. With older driver simple synchronization error could appear as uncorrectable device errors.

1. CSCtl77244 Transient FAN inoperable transition

During UCS (CMC) firmware upgrade and switching to new master/slave mode CMC erroneously takes information from the slave IOM and evaluates fans as inoperable based on stale data.

1. CSCtl43716 9541 device error. Fan Modules reported inoperable, running 100%

Software code routine bug where single bus_lost event followed by successful retry will result in an infinite loop. As result Fans are reported as inoperable and are not controlled by CMC.

1. ??

Removed an artificial cumulative threshold to enable amber color LED upon reaching 1000 bus_lost events. This was implemented as a monitoring mechanism to simplify identification of the PCA9541 devices. This is no longer needed since a proper software workaround is implemented.

Since this email we have started the update to firmware 2.0. This is a separate blog I am going to write because that too was pretty intense. I will provide some additional steps that we performed to lessen the impact. One thing is for certain don’t expect it to NOT be impacting….

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com  and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

Network Troubleshooting 101 – vSphere VM Guest (Updated)

General Information (VMware information): (Updated)
What is Beacon Probing?
Well, if you don’t know I would give the following Kb a read.
You can find that here:

Let’s hope I can do this some “Justice”

A few weeks ago I ran into an issue where VM NICS would just randomly go down. The only way I could get them back online was to perform a vMotion of the VM to another host and resetting the port connection on the dvSwitch seemed to fix the issue. So essentially I wanted to highlight some basic troubleshooting steps and things you can do to help you better pin point where the issue may be occurring.

1. From the Guest VM having the issue attempt to ping any other VM on the same host, switch, and portgroup. This will allow to pin point the issue to see if it is related to the physical or virtual networking.
2. Enabling Beacon Probing can help detect upstream failures. (Be sure to read up on it) Enabling beacon probing will increase bandwidth utilization and CPU cycles on an ESXi host so simply consider the tradeoffs.

Why I need to enable it?
VMware recommends to  introduce this change for either permanent or temporary use. Beacon probing as stated above can help or allow us to detect other failures which may occur upstream. When the failure occurs on the VM this will help you isolate the issue as being related to the VMware Virtual networking or the Physical switching (So can troubleshooting). If the failure happens on the VM and the Virtual Switch uplinks trigger an alert this will help you to pin point the issue.

Implementation Instructions:

Enabling Beacon Probing for Distributed Virtual Switch for a vCenter:

1. Before enabling Beacon Probing I will engage James Hendrock to get Bandwidth utilization before and after enabling Beacon probing.
2. Log on into the vSphere Client and connect to any vCenter you want to change it on
3. Browse to Home > Inventory > Networking
4. Expand the following objects in the tree to the left: (see figure)
5. Right Click a Port Group under the dvSwitch switch > Edit settings…
6. Highlight under policies the Teaming and Failover: (see figure)
   

1. Select Network Failover Detection Dropdown (should currently say Link Status only) > Select Beacon Probing (see figure)
   
2. Click Ok
3. Repeat steps 4-7 for all other Port Groups on dvMgmt dvSwitch.

Take Away:

1. Beacon probing is best used with a 3-pNIC configuration with even a N+2 Switching design being highly recommended
2. Beacon probing configured with 2-pNICs means that whether or not you use it in a N+1 configuration it will detect a downstream failure but it has no way of knowing which uplink is bad.
3. In a 2-pnic configuration if one fails it will trigger a redundancy lost message but at the same time just shotgun traffic down both pNICs to ensure communication is sent.
4. If you are going to use Beacon Probing you must also consider the network design.

Resources:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1005577&sliceId=1&docTypeID=DT_KB_1_1&dialogID=273348945&stateId=0 0 273356736
http://blogs.vmware.com/networking/2008/12/using-beaconing-to-detect-link-failures-or-beaconing-demystified.html
http://www.bctechnet.com/?p=10
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1012819&sliceId=1&docTypeID=DT_KB_1_1&dialogID=273348945&stateId=0 0 273356736
http://frankdenneman.nl/2011/02/ip-hash-versus-lbt/
http://www.yellow-bricks.com/2010/08/04/high-physical-switch-cpu-load/

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com  and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~

VMware Backup CommVault – Features (Simpana 9)

As some of you may or may not know I have been working with CommVault. Here is High Level overview of some features.  (IF any notes are not accurate please contact me for an update. This version was based on just plain Simpana 9. This is not the latest release of the product which may be improved or different.)

CommVault Simpana 9
Features

Architectural – Informational

1. ComCell – is the group of ComServe servers

1. ComServe servers are the same thing as ComCells (Stand alone or distributed) and is a way to separate data with a physical boundary:
2. Is a Master server and media agents

2. ComCell can support more than 5000 Physical Servers depending on configuration
3. You can define groups and roles granularly and use AD to assist this.
4. Can use multiple AD authentications and connections.
5. Is a distributed model and can involve multiple media agents.
6. Scaling involves using media agents.
7. Media agents can have certain licensed options on it.
8. Using multiple media agents (if licensed the same) can do balancing between the two based off current utilization. Meaning some backup operations may run on Media agents that are not under load. This can ensure backups run without being impacted by performance or load.
9. Distributed model allows for a certain level of High Availability allowing other media agents to pick up the slack if one goes down.

1. Require SQL server
2. For mounting NFS backup media it requires a Linux based media agent

Encryption – Set on the media agent properties under “Encryption”

1. From Host to Media Agent Encryption
2. Various encryption types
3. Encryption of data in flight (only data handled by CommVault)
4. Encrypt to disk > Dedupe Data to disk can be encrypted
5. Encrypt after moving from disk to other backup target
6. Uses Keys to only allow Customer data to be read by only the customer
7. CommVault is the only solution that can do data – dedupe encryption. (verify?)
8. Properties of the media agent to set encryption (Right click the media agent)
9. Encryption Direct Media Access can be a caveat depending on how you want to be able to access the encrypted data. Password protected no Password, or using keys…
   1. Some customers tapes use TKLM (so no need
   2. Data Domain Media targets present particular challenges
10. Encryption with CommVault gives you a lot of granular control (from the looks)

Storage Policy – How it handles the data being written to the media.

1. You can set up various polices per client to separate the data being backed up.
2. Data Streams –
   1. Can be set to more or less (default is 30
   2. When Data streams are filled jobs go into pending
3. You can specify different data pools for different policies (Backup media types)
4. At the application layer CommVault can open up more data pipes and targets to disk/readers for streams – this means that CommVault does produce one of the best through puts when moving data.
5. Data archiving and retention offers a wide-array of options
6. Data Deduplication
   1. Dedupe ratio on “first pass full image level” was all over the place.
   2. Is an option that can be set individually on each storage polic
   3. Can create a new DeDeup data base with each polic
   4. Database – is only a check in basis and can be set on a “client” level. This means that a client can have their own dedicated dedupe Database
   5. If dedupe is gone we can still restore data based off metadata in the backup data (How CommVault is designed and backups up data
   6. You can recover a dedupe database and CommVault can back it up
   7. Dedupe to tape – Price per performance conversatio
   8. Reduces Cost of Tapes in general per Yea
   9.  Requirements should be define
   10. Writes in volume
   11. All tape writes are sequentia
   12. All data has to be staged to disk in order for CommVault to read that dat
   13.  customer requirements may be only “tape” backup
   14. RTO and RPO becomes a talking point
   15. Hybrid design of CommVault allows you to mix and match different types of backup data. This gives you a lot of granular control of your backup policies. (Strong Plus)
7. Properties of Storage Policies:
8. Check Copies > Right Click Storage Policy > Select Copy Precedence
9. Highlight a storage policy in the right pane is the Copy of the Data in that policy.
10. Copy to disk
11. Copy to tape
12. Backup Jobs associated
13. Dedupe rate
14. Alerting for Aux Copy (i.e. basically when you move data from disk to tape)
15. Storage policies control the retention of backup jobs – NOTE: This is not handled in the schedules
16. Synthetic Full – which means it’s compiled all the incremental and the full backups along with Deduplication. This allows quick recovery and eventually only utilizes incremental backups to perform restores. Also this is a very fast backup.
    1. Gets ACL’s from the very first backu
    2. Takes all disk signatures and creates a synthetic from and the incremental after. The SF merges the Full/Incremental backups and avoid the re-compiling allowing for faster backups
    3. You are not getting the original backup – or ACL’s afterwards.
    4. A different conversation with Tapes
17. Adding another copy (retention/archival so to speak):
    1. To add a new copy of the storage policy just right click the storage policy > go to all task > new cop
    2. With each copy you can define different properties on how that copy treats the data. Again giving you a large amount of granular control over retentio
    3. You can also define a new schedule as wel
    4. If something occurs with the fabric or SAN and you have a separate copy that is not affected by that failure you can swap the copies to allow the backup to still run if the primary backup media was down or not available.
18. You will still have to configure associations (backup jobs)

Backup Jobs –

1. Data Readers – These are how many VM you can essentially backup at the same time.
   1. Can be changed up and down.
2. Different backup sets allow you to separate physical boundaries and can sometimes backup or touch the data more than once.
3. Defining subclient within the backup job allows you to separate backup objects without touching the same data multiple times.
4. Subclient is essentially the backup objects or targets.
5. You can associate your Backup set with certain Backup Policies
6. Backup Types
   1. Incremental

2. Full

3. File Level

1. Network Agents are how many processes it uses to move that data
   1. This affects streams on the back-end – (Network Agents times Data readers = Data streams)
2. Dedupe at:
   1. Client

2. Media Agent

1. Schedule
   1. Can define times

2. Can associate backup jobs

3. Can define full backups

4. Can Define incremental backups

Streaming Backups – Media Agents

1. Are essentially data movers
2. Media Agents can share different types of storage and can be load balanced
3. Fault tolerance can be used for media agent streaming
4. Intelligent – Load Balancing

Restore

1. For individual file restores an agent may come into play if you don’t have permission

1. Impersonate User is an option

2. Use an agent that is already authenticated

3. ACL/Permissions restoration is optional

1. Restoring an image VM
   1. By Subclient is an in place restore

2. By Left pane is granular restore

1. Support for vCloud Director – (I don’t see this not being addressed)
   1. Manual import into vCloud Director

2. vSphere restore automated VCD requires an admin to be involved

SMTP

1. User security MUST have a defined email address (User Properties) to use SMTP
2. Must be the user on the local machine/domain.

Licensing

1. Can be A La Carte (Line Item)
2. Capacity Licensing (You get everything they offer but pay by the TB)
   1. This can be good because you can factor DR cost into the Per GB/TB a client uses or enterprise.

2. Can be quite expensive

Other Information

1. Proof of Concept requires negotiating with CV.
2. I do believe the VCD GAP will be addressed in the coming days. I cannot foresee this not being addressed.

***Disclaimer: The thoughts and views expressed on VirtualNoob.wordpress.com and Chad King in no way reflect the views or thoughts of his employer or any other views of a company. These are his personal opinions which are formed on his own. Also, products improve over time and some things maybe out of date. Please feel free to contact us and request an update and we will be happy to assist. Thanks!~