If you were talking to someone whose organization is considering Veeam Cloud Connect, what would you say?
How would you rate it and why? Any other tips or advice?
I would rate Veeam Cloud Connect at eight on a scale from one to ten.
I have plans to continue using this solution, and I would recommend it to others who are interested. I would rate Veeam Cloud Connect a nine out of ten.
So, the use basically is for two use cases. It's a combination of three use cases. Compliance, some companies nowadays, compliance standards force them to have a specific backup policy and a specific retention policy, and it's kind of hard to do that manually. Some people just prefer to have a solution that also meets that. That makes it easy. That's compliant. However, some people just want to take their detail. Some people are actually upset about protecting their data being that it's pretty evident. Just sum it short, the backup server is the granular solution. It's basically responsible for managing the tasks and the jobs and all of the other components. The backup proxy is basically the muscle of the solution. This is what actually is interacting with Office 365 and doing the actual backup, it is coordinating the Veeam backup server to do that. You either have radically attached storage or you have storage over the network or it's shared, or it might be a sound storage. Regardless, just any storage that is presented to the Windows operating system, you can use it as storage for the Veeam backup. As long as you have internet connectivity, and no firewall is in place, or specifically, the required firewall forced to be open, that is okay. Most of the users we deal with are shared. They are behind the entire IT environment. The main pitch from our end is based on the fact that this edition is really easy to use, and we want you to try it and see that. Because nowadays, there's a lot of challenges in the market. Clients don't usually have dedicated IT personnel for everything. They usually share one IT person of all the IT folks, for all the workflows in the IT department. Honestly speaking, lots of people just look at it from a business point of view. Like, hey, I just have a business need, I just want to backup my Office 365 data. But, they don't take much concern into what that also requires. Generally speaking, from a backup point of view, the biggest concern is how much data, and what the percentage would be, that you'd like to backup, and how much of the capacity of this data. Also, what are the recovery point objectives, and how frequently do you want to do backups? What kind of retention policy are you trying to achieve, and the shorter the retention policy, the smaller the storage capacity you need, the lower the cost of the solution. But at the same time, some people are tied by their clients and by specific retention policies. So, tell people they need to archive their backups into application appliances, to save on the cost of storage like I do. However, that's not recently possible with Veeam backup for Office 365 yet. Nonetheless, it can be done manually, I believe. So that's basically it. That's what clients need to be careful of and the really important part is to make sure they have enough storage for what they are trying to achieve as they prepare their backup plan. Then, make sure they have the internet bandwidth for this. It is always best to have the ability to channel for this. Backups have to be properly sized, then they should be good to go. They should be worrying about the details part, the sizing, design, and the solution to fit their needs. Other than that, so long as that process goes well, it is pretty seamless after that. I would rate this solution an eight out of ten.
Overall, this is a good solution and I recommend it for simple environments. I would rate this solution a nine out of ten.
I like this solution and recommend it to clients. From a data center point of view, I also do consultation as well as being the principal engineer for the data center from VMware and Veeam standpoint and I've always recommended Veeam for our clients. Right now I've got a very good opinion of the product but it remains to be seen what happens down the line. For now, I would rate this solution an eight out of 10.
I would rate Veeam Cloud Connect a nine out of ten. Not a ten because the GUI needs improvement. It's complex. If it was a little less complex it would get a ten. I would recommend Veeam Cloud Connect. It's a great product because it's great scalability and it scales out from small to big companies perfectly. I think it's one of the best products that you can have on the market.
My advice is that if you cannot afford, or do not have the capabilities of having your own secondary site, then Cloud Connect is a good alternative. It's usually sold as a service based on an OpEx model so there's no capital layout, which makes a lot of sense for customers embracing a cloud-based approach to data protection. Before committing to a solution, do your homework and analyse your backup workloads to determine what your cloud storage consumption would be, especially if you retain data for a really long time. Using a cloud solution is a fast and easy way to get data off-site but the cloud storage costs might be high if your data sets don't deduplicate well. Overall, this is a really good product. I would rate this solution an eight out of ten.
I would rate this product a 10 out of 10.
We're Veeam partners. I'd recommend the solution to others. I'd rate it eight out of ten.
We're Veeam partners. The main difference between Cloud Connect and a standard on-premises solution is that the cloud is a cheaper alternative. For our purposes, we're using it mostly for offsite backups. We like to keep the primary backup offsite. It helps to make for a quick recovery. For me, the goal is to have a more economical approach to the secondary off-site backup, and that's the main advantage of Cloud Connect. I'd advise other organizations to keep the first or the primary backup on-site and use Cloud Connect connected to a public or a private cloud to have a cheaper secondary copy. They should also keep the restore point (as much as possible) in this offsite backup storage location. It is cheaper than the on-site. The capital expense for the on-site storage should be kept as low as possible - without compromising the RGO of the restore, of course. Flexibility is important. Clients should be offered the flexibility to choose whichever storage they would like for secondary storage or off-site backups. And they should also have the flexibility to change from providers as well. I'd rate the solution eight out of ten. I'm not quite a Cloud Connect expert, however, with the experience I've had, it's quite good. I honestly haven't seen anything that is much better. It's not complex or difficult to use or learn. Of course, you need some experience, but the learning curve is not high.
We're a managed service provider, so we handle this solution for our clients. We're also a Veeam partner. I'd rate the solution ten out of ten.
I work for a consulting enterprise. For my needs, the solution offers everything I want. I'd rate it seven out of ten.
We are partners with Veeam. I would recommend this solution, but it really does depend on many factors, such as the size of the environment, what their requirements are, and do they have the capabilities to install Veeam I would rate this solution a seven out of ten.
We connect to the public cloud via Amazon, and for the private cloud, we use a cloud-based VMware solution. I would rate this solution eight out of ten.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.