Copy Job - Move to new Repository - Issue

[Berniebgf]

Hi All,

I have been moving some backup copy jobs to a new repository, all has been going OK but the last one I did is now in a bit of a mess.....

Here is what I have at the moment:

Copy job original repository - W:\Backups\JobName (This had the original VBK, VIK, VBM)

Copy job New Repository: V:\Backups\JobName (I have all of the files from the original repository to this one)
Re-pointed the copy job to the new repository....no problem
Deleted all files and folder from original location....

When the copy job ran again I now have the following

Copy Job Original Location - W:\Backups\JobName (New / latest VBK files are being put here...)

Copy Job New Location - V:\Backups\JobName (No New files are being placed here)
Copy Job New Location - V:\Backups\JobName_1 (This now has a new VBM but no backup files)

Backup copy job is complaining that it can not perform consolidation....

My question is, how do I piece this all together again?

Which VBM do I use and where do I put all the backups?

Thanks

Bernie

[foggy]

Strange behavior, indeed. I suggest contacting support so they could put their hands on your environment.

Btw, have you rescanned the new repository after copying existing backup files into it?

[Berniebgf]

Yes,

Rescanned performed, all the other jobs went through OK. Just this one that's a problem..

I have a call open ID#00620808, they have explained the process to move the files but not given me the answer on how I can clean this mess up. Waiting for a response.

If it means recreating the Job, I can do that however I would prefer to avoid doing that.

And before I go moving files around trying other things, I want to check with support.

Bernard

[foggy]

Does the new JobName folder contain VBM file copied from the old repository? What if you try to delete the JobName_1 folder, rescan the new repository, and try again?

[Berniebgf]

Hi Foggy, All.

The new folder had a new VBM, in backups there were now two entries for the Job (one with 2 x restore points (new) and one with 32 (old).

So basically I removed the new backups folder _1, deleted the backups (qt 2) (leaving the original backups there, edited the job and confirm it pointed to the new repository and then mapped it to the original backups. After that I rescanned the repository. Next backup run ran as normal with an incremental..... all good.

regards

Bernard.

[foggy]

Glad it is fine now, thanks for taking time to update the thread.