Skip to main content
  • EN

Hey there,

 

we need Offsite-Backups of our Unstructured Data. Since the Backup Files are roughly 3,5 TB in Size, its impossible to get that Data to the Site directly due to slow Internet Connections. So i first configured a Secondary Target NAS for the Backup Job Onsite to get that Backup Copy onto it. I then moved that NAS to the Offsite Location, changed it’s IP and added it back into Veeam as a new Repository. Did a Rescan of that new Repo and Veeam found the Backup Data and added it.

 

I now added that new Repo to the secondary Target in the Veeam File Backup Job and removed the first one (which was the same NAS with the Onsite IP which is now invalid). I then restarted the actual Backup Job. It created some data, finished teh Job and the new Backup Copy Job started.

 

But here’s the problem: It completely ignores the Backup Copy already in existence on that (now) Offsite NAS and instead starts creating a whole new Backup Copy. This is absolutely inacceptable.

 

How can i tell Veeam, that it has to use the already exisiting Backup Copy on that NAS? Which has a different Backup Copy Job Name now?

 

Many thanks for your help

Steffen

When you created the new File Backup job did you not see the “Map backup” option when selecting the repository like below?  That should allow you to remap the backup and continue the chain.

 
 
 

The “map backup” button is not available for file backup copy jobs.

To remap a file backup copy job, follow these steps:

  1. Disable backup copy job
  2. Remove backup copy backup from configuration
  3. Move the backup to a new repo (should be already there in your case)
  4. Rescan new repo
  5. Remove old repo in backup copy job, add new repo to the copy job
  6. Copy job should automatically be re-enabled, next run will continue the existing copy chain

The “map backup” button is not available for file backup copy jobs.

To remap a file backup copy job, follow these steps:

  1. Disable backup copy job
  2. Remove backup copy backup from configuration
  3. Move the backup to a new repo (should be already there in your case)
  4. Rescan new repo
  5. Remove old repo in backup copy job, add new repo to the copy job
  6. Copy job should automatically be re-enabled, next run will continue the existing copy chain

Thanks for the clarity Matt.

The “map backup” button is not available for file backup copy jobs.

To remap a file backup copy job, follow these steps:

  1. Disable backup copy job
  2. Remove backup copy backup from configuration
  3. Move the backup to a new repo (should be already there in your case)
  4. Rescan new repo
  5. Remove old repo in backup copy job, add new repo to the copy job
  6. Copy job should automatically be re-enabled, next run will continue the existing copy chain

Thanks for this reply. I did it exactly like this, but with the exception, that i havent disabled the Backup Copy in the first place. I disabled it now and reactivated it; added the Repo and now it created a New Backup Copy Job with the correct Name again and on the NAS i can see that it modifies Data inside the existing Folder. So it seems that this did the trick now.

 

I report back if it fully worked once its done.

 

But so far: Thank you guys for your fast replies!

Steffen

Hi guys,

 

i wanna get back to you as promised. The Copy Job has picked up the existing Backup Copy again. It was really working. So the Solution provided by @MattM is the real deal here. Thank you very much!

 

Post-Processing of that Backup Copy Job took quite some time though and i really have no clue what it does in these Post-Processing Stages, but it eventually ended and now the Unstructured Data Backup along with its Offsite-Copy is done in a reasonable amount of time and can be used for the purpose.

 

Again: Thank you guys and all the best to you.

Steffen

Thanks for the update!

Good to know that it works as designed (although maybe not as intuitive as you’d expect in this case) ;-)

Great to hear the steps provided helped you with your issue.  Hopefully others can reference this post now too.  😎

Comment


Terms & Conditions