File Copy to Backup Server not available anymore

[BostjanUNIJA]

Hi, can someone explain to me why did you change the ability to store a copy of configuration backup on a VBR server?
"You cannot use a backup server as a destination for file copy jobs."

We have environment where we are making configuration backups to offsite backup repository, because that's ideally if VBR server gets corrupted that we still have a copy of configuration backup somewhere else.
At the same time, we have a backup copy job, which takes that configuration backup from offsite backup repoistory and copies back to VBR server.
Now with thatl limitation that backup server can not be anymore destination for file backup copy job, I see that we would need to represent an additional 3rd server to store those copies of configuration backup.
Or is there any other alternative?

[Mildur]

Hi Bostjan,

I assume you’re still using a Windows-based backup server?

I’d recommend changing the workflow:
1.) Write your configuration backup to a repository on your backup server.
2.) Use a File Copy job to copy it to the offsite backup repository.

Best,
Fabian

[BostjanUNIJA]

Mildur I have tried your suggestion.
I have changed the backup configuration to primary onsite backup repository.
Since this repository is mounted over ISCSI, VBR server sees it as a local volume.
Then I have created a file copy job, where I have selected this local volume/folder, and destination (offsite backup repository / folder).
The file copy job task fails, as it says it cannot connect to VBR server on port 2500.
I have disabled firewall on VBR server.
I have even tried telnet localhost 2500, but nothing is listening on that port on VBR server.

[BostjanUNIJA]

I have opened a support case: # 08065498

[Mildur]

I ran a quick test on my Windows v13.0.1 backup server, and the File Copy job worked there.
Thanks for the case number. Let’s continue with our Support team for now.

Best,
Fabian