re: moving single 'volume' backup job agent to multiple volume backup job

[edison5000]

case# 05597535

All of our agents are backed up in workstation / managed by agent mode.

User wants to add additional *internal* windows pc volumes to their backup.

Right now, we have a backup job containing a number of OU's in a protection group, that all get their single C: volume backed up, including this user.

I want to be able to add this user's volumes to some kind of job such that it does not force a new full, if possible.


Since there's no current way for a user agent to add volumes themselves, to their own machine, in this manner, I figure the options are

1. add additional volumes to the current job they are in.
This seems like a bad idea, because I suspect it would force the job to hunt for additional volumes on every other agent in that protection group.

2. (seems most likely?) create a new 'volume' job and new protection group which contains only that user, and add C: + any additional volume(s) they want. I am hoping by doing this, Veeam won't have to redo a full backup on their system, and just add new volumes to their backup chain. True?

I know I can create a new job containing a protection group that backs up 'whole computer' - but am pretty sure this will start over an active full, and make them unable to access their previous C: backup chain.

thanks veeamers. : )

[RomanK]

Hello edison5000,

Why not create a new job with a computer (or protection group) with any additional volume(s) they want?

However, in any case above you would get an additional job. Some collisions are expected. There is nothing wrong but when the first job backs up drive C: the second job is waiting for it to backup drive D:.

If you don't like all of these options, you may ask Support about mapping. It has some complications but could be technically possible.

Thanks

[edison5000]

I am 95% sure you cannot have 2 jobs backing up a single agent, that I am aware. We tested that several times when we first built the server. If you have agents in multiple jobs (at least, workstation-managed-by-agent), whichever one was created first will work, but the new additional jobs containing the agent(s) will tell you in plain english in the error section, that all the agents in the new job already belong to another job. Not that we want 2 jobs for the same system. : )

But yes, your suggestion was included in my #2 'most likely' idea. Which is move the single user to their own new job AND own protection group. My question again is: if an agent is part of a workstation managed by agent job, that does volume: C-only backup - if i move that agent to its own protection group, and create a new job for it - will it continue the same chain it had from the other C-only job, or create a new chain?

If it is going to create a new one, I might as well just move that agent into a 'whole computer' backup job group that already exists. Point being, I was trying to avoid them having to do an entire new full.

[RomanK]

Hello edison5000,

Ah, yes, you are right. The workstation allows only one job per agent, I've missed that.

move that agent to its own protection group, and create a new job for it

New chain.

Again, if you already have a support case opened, ask an engineer if it would be possible to map the current chain to the new job.

Thanks

[edison5000]

Veeam Agent Support person working on this case #, tested it in lab. Instead of just adding another volume to the 'volumes' job, switched to 'entire computer' , and even there, with new volumes presented, it did not start a new chain. Which is cool, but not what I expected. I will certainly find out when we do it as well, and report back to double confirm.