Moving To New Repository

[r.mckeon]

Rick, please review the steps required to change the backup repository in the beginning of this thread. Thanks.

Thanks I had a look in the forums beforehand for any similar topics but I must have missed this, sorry about that.

[foggy]

No problem, thanks for trying to search prior posting. Hope this one helps.

[r.mckeon]

So I did some testing after following the procedure written in this thread. Just to clarify, these are the steps I had to take:

Old PC/share: \\PC-Old\Share
New PC/share: \\PC-New\Share

1. Move the external hard drive to the new PC
2. Add new repository in Veeam as \\PC-New\Share
3. Go to existing backup job, and with \\PC-Old\Share still selected as the backup repository, click Map Backup
4. Map to backup to the same job
5. Now change the backup repository in the job to \\PC-New\Share and I could see the backup files listed
6. Click next, next, next and Finish
7. Job ran normally!

[TomPioreck]

We're experiencing server growth, which is causing us to address hardware storage issues within our repository environment. All in all, not a bad issue, it's by design for increased usage of Veeam, specifically the use of backup copy jobs for its GFS abilities for our retention policies.

I've been able to change the target location without issue within Veeam and I've been manually moving the repository folder from one location to the other, prior to changing the target within the job(s) themselves. I just want to confirm that this is the best method or if there's another way that I should be migrating the destinations for these jobs.

It's likely that I'll need to migrate the jobs at least one or two more times before our upgrades are complete.

Thanks.

[veremin]

Hi, Tom,

Your post has been merged into existing discussion regarding similar matter. Please, check the answers provided above.

Thanks.

[Peter Faber]

how do i change the share folder location? (a NAS has a new IP)

[Shestakov]

Hello Peter,

Could you clarify the issue?
Do you have existing backup jobs mapped to the repository?

You can just add the repository, make rescan it and you will see all backup files and restore points on it. Then you can map there your existing jobs if you have any.

Thank you.

[Stabz06]

Hi guys!

I want to move my Backup Copy Repository to another partition on the same server.

change Backup Copy with path E:\VeeamCopy to path D:\VeeamCopy

I tryed this procedure http://www.veeam.com/fr/kb1729 but doesnt seems working. The backups files doesn't imported.

[foggy]

Please review the procedure outlined in this thread and feel free to contact technical support for assistance, if it does not work for you. Thanks.

[Brad.Morris]

Hi all,

We currently are running Windows 2012 servers for our Repository servers. We have Windows Dedup enabled and seeing good results.

We are now looking at upgrading these servers to Windows 2012R2. Is it as simple as building the new servers and moving the attached RDM's from the old servers to the new ones? Or is the a process out there that documents the steps required for replacing/upgrading the Repository servers?

Thanks,
Brad.

[veremin]

Hi, Brad,

You can either use the procedure described above or perform in-place upgrade to Windows Server 2012 R2.

Thanks.

[Brad.Morris]

That was what I thought as I have moved backup jobs around for space reasons. My biggest worry is copy jobs due to issues I am having now with moving them around. I am worried that I will move them and not be able to point the jobs to the new location.

[Shestakov]

Brad, backup copy jobs can be mapped as well as backup jobs.
Thanks.

[veremin]

Providing you follow the recommended steps, there should be no issues with that.

[Brad.Morris]

Thanks all. I will wait until patch #2 comes out with the fix for the re-mapping of copy jobs.

[veremin]

You can wait for patch#2, if there are GFS restore points in backup copy job chain. The patch#2 should address the issue related to mapping a backup copy job to a chain with GFS restore points.

However, if there are no GFS restore point in chain, feel free to migrate repository now.

Thanks.

[lando_uk]

Hi

I wish to move a job from an old repository to a new one, but this job has 2 copy jobs associated with it which I don't want to touch or restart. One is offsite with low restore points, and one is a long term retention copy. If I point the backup job to the new repository, will the copy jobs just carry on fine with the incrementals? or will they lose the CBT and trigger a full copy?

Thanks

[veremin]

Your post has been merged into existing discussion. Check this post for the detailed description of the required procedure. Thanks.

[lando_uk]

ok thanks, that explains a basic move, but I should have added more in my original post.

What about this scenario. My current repository is a large RAID6 and was too slow to transform backup chains into rollbacks each week for this one job, so that job has 4 or 5 full VBKs files (so its large) The new repository is RAID10 but smaller, but it'll be quick enough to run rollbacks now, so it means that the old files wont all fit. I don't mind starting a new chain using the new settings in the new location, but I don't want to start a new chain on the copy jobs, as I'm short of disk space in that copy job location.

[foggy]

If you perform repository change correctly, backup copy job should proceed fine with incremental runs even if you start the backup job from scratch (unless specific source repository is specified to look for restore points in).

[lando_uk]

So I'm worrying over nothing then, I just edit the job, tick on the rollbacks box and point it to the new location , keep all the copy jobs the same, and it'll just work?

[Shestakov]

Correct, if you chosen source "From jobs" in the backup copy job options, you don`t even need to change the job settings.
Thanks!

[lando_uk]

What will happen to the old backup files, will they just remain the original location and i'll have to tidy up manually once I'm happy with the new backup?

Will I end up having two lots of backups in the Disk section with the same name, but different creation times?

[Shestakov]

- If you decide not to move backups to a new repository, but leave them there, they will not be deleted automatically.
- Name of backup file includes the backup date, so names will differ.

[lando_uk]

Hi, I tried to set this up today, and when I change location, it wants me to copy the old files to the new location so I can't just change it.

Does that mean I have to clone the job and create a new one? If I do that, I presume I'll lose the copy job chains?

[foggy]

If you do not want to copy existing files, the procedure will look like this one.

[lando_uk]

If you do not want to copy existing files, the procedure will look like this one.

If I remove from backups and then start the new job, can I then import it again for other admins who may want to restore from it?

[foggy]

Sure, you can.

[gparker]

Hi, I've seen a few posts related to my question, but they are 12 months or more old, so I'm wondering what's the situation with the newer versions of Veeam:- I've got a client running Veeam on an old physical server and their backup repository is a SAN LUN that's mounted as a local disk to the server as a drive letter. They want me to re-install Veeam onto a brand new server that's got "tons" of internal disk capacity that will be setup as a new backup repository and they want me to migrate their backup job configurations/settings and to also move/relocate the repository. They then want me to decommission the old Veeam server and re-purpose the LUN as quickly as possible.

If there's no way to migrate the backup job settings/configuration database from the old Veeam server to the new one, it's no big deal for me to setup all the jobs again on the new server, but what's the best way for me to move/relocate the repository? I want to be able to restore from previous backups if required.

Your assistance is much appreciated.

George.

[PTide]

Hi,

If there's no way to migrate the backup job settings/configuration database from the old Veeam server to the new one

There is. You can perform config backup and import it on your new server.

but what's the best way for me to move/relocate the repository? I want to be able to restore from previous backups if required.

Please check this post.

Thank you.