BR Update3 - Protected Group

[suklje]

Hi,

Using the latest update with central agent management, BR creates one mess of a folders on destination repository - something along the line of "VeeamAgentUser8c2f4b39-8fe5-11e6-925b-4a0c7201808f". Any way to clean that up?

Best regards

[Vitaliy S.]

Do these folders have any files inside?

[suklje]

Yes.

I have 5 workstations added to a protection group, let's call it "Test Prot 1", with a computers called PC1-5. Creating a backup job with a protected group creates 5 folders (VeeamAgentUser...) on a destination repository, and each one of these folders contains a folder named "Test_Prot_1-PC1(-5) Job".

While am at it, how can I remove workstations from "Manually added" from Inventory - Physical & Cloud Infrastructure ?

Thank you

[Dima P.]

Hi suklje,

VeeamAgentUser8c2f4b39-8fe5-11e6-925b-4a0c7201808f

Looks like you've created ‘managed by agent job’. In such case each agent creates a folder based on its personal certificate.

I remove workstations from "Manually added" from Inventory - Physical & Cloud Infrastructure ?

It's not required. Go to Inventory tab, right click the host and use ‘Move to protection group’ option.

[HMwkr]

I also need to delete two hosts from "Manually added" - I do not have the "Move to Protection Group" for either.

[Dima P.]

HMwkr,

To move computer from manually added to custom protection group try this:

- Right click manually added protection and click properties. Go to Computers step, select the desired host and hit Remove
- Open desired custom protection group and add the host by IP or host name.
- Rescan this protection group, it should find the host.

Let me know how it goes.

[Helferlein]

Hi all.

I have created a new Protection Group. Now I tried to move a VM from the 'Manually added' to that new protection group just as you suggested in the last post.
But now it give the following error:

'... cannot be deleted, because it is used as the source for one or more backup jobs'.

What can I do?

[HMwkr]

To move computer from manually added to custom protection group try this:

- Right click manually added protection and click properties. Go to Computers step, select the desired host and hit Remove
- Open desired custom protection group and add the host by IP or host name.
- Rescan this protection group, it should find the host.

Ah, the old "if right-clicking the thing you're trying to change doesn't work, right-click everything else you can see" tactic. Thanks!

I had more of a battle with hosts which were showing in Manually Added and also in a Protection Group; one was showing in both places as FQDN; the other showing in one as FQDN and the other as NETBIOS. I got there eventually ...

Regards
William

[Dima P.]

What can I do?

Remove the host from backup job, then remove it from Manually Added protection group. Then add this host to the desired protection group.

I had more of a battle with hosts which were showing in Manually Added and also in a Protection Group; one was showing in both places as FQDN; the other showing in one as FQDN and the other as NETBIOS. I got there eventually ...

It depends on how you add hosts to ‘IP based’ protection group. If via IP address - likely you will see NetBIOS name. If via FQDN – then you will see a FQDN as name in Veeam B&R console. Last approach is recommended.

[HMwkr]

It depends on how you add hosts

I didn't add the hosts, Veeam added them itself, during the upgrade process. It'll be a while till the next upgrade so I'm not going to worry about it

[Dima P.]

Understood. I’ll double check this behavior with QA. Thank you!

[Helferlein]

Hi Dima.

When I remove the hosts from the backup job and add them (the same) later from the protection group, will I loose the backup chain?

[Helferlein]

OK.. I just tried it with a backup job and can say that I did NOT loos the backup chain

[DaStivi]

you're not loosing it.. instead ah new chain will be started... the old one remains intakt, but also didn't get cleaned up.. and the initial full for the new chain will took also the full, full-space it needs!!
physical-cloud-f49/migrating-agents-to- ... 47725.html
physical-cloud-f49/moving-from-agent-ma ... 47669.html