splitting a backup job without losing backup data

[bjdboyer]

I have a customer with a job that has 4 VM's in it. One of the VM's is 4.5TB in size and the repository space used just for it and their retention is about 14TB. They want to change the retention of that VM's backup but leave the other 3 VM's the same. Is there a way that I can take that VM out of the job and create another job with the lower retention policy and point it to the existing backup data in the repository? The repository is an SOBR and each extent is set up as per-VM. so I can see all the VIB and VBK files for that VM. I really don't want to have to try and back up the original 4.5TB VM all over again. That customer is over a firewall and throughput isn't all that great.

I thought I could just create a directory on each extent of the SOBR, move the VIB and VBK files to that directory, rescan and then map the new job to that directory?

Is this possible? I guess I could make a new job for the other 3 VM's and start them over, but 1 of them is still 2.4TB.

Thanks,
Bill

[csydas]

Hi Bill,

To my knowledge,this cannot be done. You would need a unique job to apply dedicated settings to it. Within any given job, retention is global, it seems.

[bjdboyer]

That's what I want to do. Create a new job for the 1 VM, but I want to be able to point that new job to the existing backup data without having to backup 4.5TB of new data that already exists in my SOBR, but in a different \Backup directory.

[bdufour]

the 'map backup' option in your job settings should allow you to do this - listed under backup repository.

[foggy]

Hi Bill, you should be able to do that provided you copy VBM file along with the backup files. Other VMs from the original job will also be displayed under the new one as obsolete and you will be able to remove these records using the remove missing restore points functionality.

[silvjo]

Hello,
I'm new in this forum.

I have a backup job with 5VMS.
I need to splis this job into 2 different jobs. Why? They are on different remote sites and I allready have 2 different backup proxies, 1 on each remote site.
All the files are on the same SOBR.
My problem is when I create the 2nd job, I can't map the backup files because it says that is used on the actual backup job.
I can't do full backups and want to have all the backup points.

What can I do?

Thanks a lot, thanks in advance for the support and sorry for my bad English.

[silvjo]

Hello all.

I need to split a backup job:
My job as 5vms from 2 remote sites.
Each site has his own backup proxy.
I want to split the remote sites in different jobs,
Can you tell me the best practices to do that?
Thansk a lot

Greetings from Switzerland

[veremin]

This seems like an easiest option to me:

- Exclude set of VMs from the existing job
- Point existing job to its site-specific proxy
- Create a new backup job for VMs excluded from the existing job
- Point the new job to its site-specific proxy

Thanks!

[silvjo]

Ok, and what if I want to keep restore points?

[Gostev]

Hello,

Unfortunately this is not possible to do without performing full backups.

However, I also don't really follow why you want to split the jobs. What are you trying to achieve? Most likely, it's possible to do without splitting.

Thanks!

[wishr]

Hello Joao,

In this case, you may utilize backup mapping.
This KB could also give a few hints.

Thanks

[foggy]

Just copy your backups twice and use mapping in both jobs. Entire VM data will be read during the next job run, however, you will keep the existing chain. See above for details.

[ansarvm]

Hi, I would like to split a backup job in to 3 different jobs with respective of applications.
Could anyone tell me if it's possible to do this, and would like to retain the restore points from each VM in the job. Is it possible?

[veremin]

Approach suggested above should for your case as well. Thanks!