License via Cloud Connect?

[prewest]

Hi all,

I have just migrated a client from a B&R server to a B&R Cloud Connect server, except it looks like it still uses the license from the original B&R server.
How can I switch it so it will use a license from the B&R CC server via port 6180?

Kind regards,

Arnold van Blanken

[Vitaliy S.]

Hi Arnold,

Veeam Cloud Connect does not licence Veeam Agents, it only licenses backups stored in the Cloud Connect. If you want to send backups to Cloud Connect, you need a license key for the Agent (standalone).

Thanks!

[jspeicher]

I don't thats a great thing, it'd be ideal to have CC to be able to manage and apply agent licenses just like B and R does, ideally features are not taken away, but added for CC, doesn't make any sense why this wouldn't be added in the future.

+1 for requesting the same thing.

[Vitaliy S.]

Jason, you can apply Agent license keys via Veeam Availability Console (for Windows Agent right now, support for Linux Agent is coming next year). Not sure that Cloud Connect will ever have the requested functionality due to these reasons (discussed in the VCSP forums).

[ortoscale]

I've installed new version, with some hassle now i can't get veeam cloud connect listed among possible targets.
At the moment I'm doing it hard way add cloud connect repository with veeamconfig options and trying to configure job via veeamconfig....
am I missing sth?

[ortoscale]

ok, i think i'm missing correct license. Error: Free edition does not support cloud repositories.

[ortoscale]

Finally doing first test backup with veeam linux agent directly to veeam cloud connect REPO. Tired of rsync & company

[prewest]

Do I really need to manually install a license on all my future machines if I want to use CC?
Maybe an option to include a "point client installation to a B&R license server"

[Vitaliy S.]

That's a good question. If you use VAC (Veeam Availability Console) to manage Veeam Agent for Windows, then you won't need to do that, as we're planning to add VAL support in VAC this year.

[prewest]

Ok, now how do I change the license?
If I try via the GUI / commandline I get this error;

[Vitaliy S.]

If you want to change license key, then you should stop managing it from the Veeam B&R console first.

[prewest]

I`m not managing it anymore, I switched it to the B&R CC.
The "old" B&R server is also shutdown.

[PTide]

Hi Arnold,

Please execute on the Agent:

Code: Select all

veeamconfig vbrserver delete list
veeamconfig vbrserver delete --name <VBRNAME>

After that you'll be able to install local license either via UI or CLI.

Thanks

[prewest]

Ok, I was able to delete the license via the methode mentioned above.
Except it does not accept a new license now anymore, I get this error now when pointing to a valid license.


In the license info:
Expiration date=31/03/2018

[prewest]

Created a case number with support : 02459510

[prewest]

Created a case number with support : 02459510

Fixed, I used the wrong path, the wrong path had a old license file.
Everything works now.

The license uploaded in the server, will it auto update in the linux agent?

[prewest]

Do I need to manually update the license on the linux agent client everytime or does it auto-update?

[PTide]

Hi,

Sorry, I've missed the question in your last post somehow. Yes, local license is managed and updated after expiration manually. If the license is obtained via VBR then VBR will take care of license updates. To check license info (such as "license source", "mode", "expiration" and so on) execute veeamconfig license show.

Thanks

[prewest]

Ok, how can I make the installation managed with a VBR server and at the same time use CC?
By making a second simple job that connect with a VBR server?

[PTide]

Yes, you can create VBR job first so Agent consumes license from VBR and unlocks CC option, after that create second (CC) job pointed to Cloud repo.
Please note, that backup to CC is currently not available in "Managed Mode", so your Agent should stay in standalone mode while connected to VRB.

Thanks

[prewest]

Yes, you can create VBR job first so Agent consumes license from VBR and unlocks CC option, after that create second (CC) job pointed to Cloud repo.
Please note, that backup to CC is currently not available in "Managed Mode", so your Agent should stay in standalone mode while connected to VRB.

Thanks

This does not work, I need to have a Server License for multiple jobs.
How can I manage the license of this server via my BR server now using a workstation license?

[nielsengelen]

What Pavel is talking about is you can backup to the VBR server/repo and then leverage VBR Backup Copy Job to send data to a Cloud Connect repository.

If you want to use 2 jobs on the VAL server you will need to use a server license as it is not possible with a workstation license by default.

[prewest]

What Pavel is talking about is you can backup to the VBR server/repo and then leverage VBR Backup Copy Job to send data to a Cloud Connect repository.

If you want to use 2 jobs on the VAL server you will need to use a server license as it is not possible with a workstation license by default.

No, thats not possible.
On-Site at the customer, there is only the Veeam Endpoint on the Linux Machine installed, I need it to backup directly to the Veeam Cloud Connect.
There is no B&R server on-site @ the customer.

So:

Linux Agent -> WAN -> CC Provider
What I want:
CC Provider -> License -> WAN -> Linux Agent

[Vitaliy S.]

I need to have a Server License for multiple jobs.

Yes, that's correct. For workstations Pavel's trick would not work. On a side note, when VAC introduces support for VAL, you would be able to achieve your goal.

[prewest]

Ok, do you know the estimated date when VAC supports VAL?

[Vitaliy S.]

Currently we're working on prototypes and design diagrams to make sure we do not lose anything in scalability. There is no strict date for the release, but we're planning to release it this year.