moving files between repositories - SessionID error

[ejenner]

hi all,

Sometimes when I want to move backup files from one repository to another (for free space management) I'll get an error like this and won't be able to complete the process.




Does anybody have any idea what is causing that?

[DGrinev]

Hi,

It's very hard to troubleshoot through the forum, kindly contact the support team and let them take a look.
Do not forget to share the case id for reference. Thanks!

[ejenner]

It's not a big enough issue to worry about logging a support ticket. I just wondered if anybody had seen it before.

[Dima P.]

EJ,

I'll pass your feedback to QA folks (to start with - we need a human readable error here to let you know what's wrong). Thanks for your post!

[c2nathan]

This error is still here, still a little unreadable to (my) human eyes.

As per advice above, I will log a case if some quick troubleshooting I try off my own bat, first, doesn't work.... but just thought I'd add a quick note here in case you want to give the corresponding task in your QA queue a nudge.

[chris.childerhose]

Did you copy the files first from the other repo the job was pointing at? After you do that you can select the new repo and then map the backup job to the new location. This may be due to not moving the files over. The other way around it would be the clone the backup job and then direct it to the new repo but that leaves the files on the old one as well for cleanup later.

[Dima P.]

Nathan,

Can you share your case ID please? Thank you!

[Regnor]

Did you copy the files first from the other repo the job was pointing at? After you do that you can select the new repo and then map the backup job to the new location. This may be due to not moving the files over. The other way around it would be the clone the backup job and then direct it to the new repo but that leaves the files on the old one as well for cleanup later.

Just had this error when moving some jobs to a scale-out repository.
Normally I would have said that mapping isn't necessary but from 16 jobs 4 had this error.
Support did use the map backup feature and afterwards saving the configuration with the scale-out repository worked.

[Dima P.]

Max, can you please share your case for a review? Thank you!

[Regnor]

@Dima: Case ID is #05823298. But those jobs were all VMware-Jobs (just noticed I'm in the agents forum section) and had transaction log backup enabled.