Azure DevOps vs. Veeam Data Cloud for Azure

Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.

Incentivized

For our purposes I can't particularly find any shortcomings of Veeam Backup for Azure. It has been working well for our needs for a few years now. Maybe for someone with a larger cloud footprint or more complex needs, or maybe someone who wants to be able to deploy and configure the appliance using infrastructure as code it may not be as practical.

Incentivized

• Utilize Git as a repository to share work between multiple users
• Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
• Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
• Track status of each task
• Integrate with Git to utilize branches, merging, approvals, history, etc.

Incentivized

• Reduce storage costs and minimizing the impact on network consuption.
• Veaam Backup for Azure provides application-aware backups for Microsoft SQL Server, ensuring that our data is backed up and available for recovery correctly.
• Replication: Veeam Backup for Azure helps us to replicate our workloads to another Azure region or on-premises environment for disaster recovery purposes and compliance needs.

Incentivized

• I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
• The wiki is not the prettiest thing to look at, so it could have refinements there.
• It could improve the search slightly better.

• Documentation around service account permissions was a little sparse when we implemented it
• It's sometimes hard to get the reason behind a (rare) job failure without going into logs
• The UI around snapshots and backups could do with some clarity around the restore points that will be available

Incentivized

I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.

Incentivized

Plainly, the product just works. I don't have to babysit it.

Incentivized

It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).

Incentivized

It was so easy that you thought it wasn't working. Once you saw data and was able to recover it or do a restore with the product those beliefs in the system went to the roof. Once you get a product that does everything you want it to do, you will give it it's props.

Incentivized

When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.

Incentivized

Great support team!

Incentivized

Was not part of the process.

Incentivized

Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.

Incentivized

Backup Exec was a very clunky application and took forever to backup to and restore from. We would backup to SSD external hard drives from a flash array, but the process still took forever to finish. Sending our data to the Azure blob storage via Veeam is a faster and more secure process than saving to the external hard drives with Backup Exec.

Incentivized

• We have saved a ton of time not calculating metrics by hand.
• We no longer spend time writing out cards during planning, it goes straight to the board.
• We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.

Incentivized

• We have had fast recovery of documents when needed; sub 10 minutes from start of restore to complete and in the users hands
• Easily a value add for backing up files outside of the given Microsoft retention period; piece of mind
• Easy tool to use with minimal training required to use it and set up backups
• When you do change your cloud licensing it does require manual intervention to update backup data requirements. if the business makes changes then your backup person may not know to make these changes

Incentivized