Hmm, this should not be a problem for you since you are a service provider? For example, you can buy 15 workstation licenses and deploy 2 licenses to one client, 3 licenses to another client and so on? As long as your total number of licenses across all of your clients does not exceed 15 (and Veeam Availability Console will help you track that).
Scenario 1:
My customer wants to protect 1 psyhsical server or client to cloud. So they have to buy 5 workstation license.
Scenario 2:
Another customers want to protect 3 virtual machine to cloud. But they havent got any vmware and veeam backup & replication license. So we want to sell 3 workstation license and connect cloud repository.
BCO file contains your Veeam Backup and Replication configuration backup and should be used to restore your backup server it case of total disaster. If you are referring to VAW central management and configuration via API it will be supported by simple scripting options (import/export of config) and distribution of this configuration via file.
Regarding the core support. It’s not going to be introduced in v2, but it's planned for sure.
I was hoping that the slightly delayed release date might have meant a change to the plan re support in Core but I see not. Would this be within the next 12 months or longer? Don't forget, if you need a beta tester...
For example client have psychical server. They want to backup up NAS first, then cloud connect server. How can they succeed it? Because in site backup is more critical.
For example client have psychical server. They want to backup up NAS first, then cloud connect server. How can they succeed it? Because in site backup is more critical.
Install Full Veeam Console - apply agent licence and switch to "Full" view mode in the options.
Add NAS as repository and point the Agent to backup to that Veeam repository.
Add cloud Connect repository to Full Veeam console.
Then Setup a Backup Copy Job in the Full Veeam console and point it to the Cloud Connect repository.
Veeam B&R free edition should be switched automatically to full functionality mode when you add the agent license (VAW or VAL).
EDIT: Please let me know when its not working /under what circumstances and share your license setup. I'll ask QA folks to confirm (feel free to send me a PM if required)
I believe that this was an early promise and was wondering if it will actually be implemented and is being actively worked on, or if this will become a pipe dream. We have to maintain a second backup solution to manage cifs backups and that is not an ideal scenario. especially when that solution is CommVault.
Thanks
My question was directed at having a different retention policy requirement at a folder level inside the VM that is longer than the retention policy of the whole VM. Say for a folder that has compliance information or product versioning data. I don't see a way to have differing folder level policies. Thoughts?
The new 2.1 release noted claim "NEW Veeam Agent for Microsoft Windows 2.1 works with Veeam Availability Suite™ 9.5 Update 3 to deliver Availability for ALL workloads — virtual, physical, and cloud — from a single management console, extending Veeam’s leadership position from being the best for VMware vSphere and Microsoft Hyper-V to #1 Availability for any app, any data on any cloud, and allowing customers to completely get rid of legacy backup forever!"
Does this mean that we can now backup our CIFS shares with the agent? That is a critical workload that requires legacy backup methods but i do not see it in the release notes, or does the claim really mean ALMOST ALL workloads?
Hi Scott, CIFS shares (NAS devices) cannot be backed up with VAW 2.1. The feature you're asking for is in our top priority list for the future releases of Veeam products.
Understood however i would then request that the press release or documentation that i pointed out be modified as it is a false claim as every Veeam customer with data on a nas device still needs to maintain their legacy backup methods.
I'm trying right now
