Skip to main content

Backup format error when switching backup location

Thread needs solution

Hello,

I'm setting up a node and I now need to upgrade all my plan (we used sftp storage before).

But when I want to switch backup location and set node, I have this error:

image 543

My backups are all tibx format. (and I have no option to set backup format anyway)

I don't want to recreate all my backup, what can I do please?

 

0 Users found this helpful

Hello Germain!

What activity produces this error? Sounds like you are trying to move your tibx archive into a deduplicating location, which as the activity says don't support v12 format that tibx uses.

You'll need to use replication (esentially recreate) to move your tibx backups into the deduplicated location.

-- Peter

Hi,

This error happens when I try to change backup location on a protection plan.

Backups are on a ftp server, and I want to use a node instead.

I don't care if my old backups stay on ftp, I cant start from scratch on the node.

 

 

Hello Germain!

What's preventing you from recreating? Storage space, resources time? Also what's your aim in switching to a managed location?

-- Peter

 

This is a waste of time for me.

I cant neither just "clone" the plan, same error ...

 

Acces to ftp backup location via acronis management console is way too long and our VM cpu was at maximum , so we decided to migrate to a node.

You *can* clone a plan, it's just what you are doing isn't considered a clone.

What is "way too long"? I'm not sure you'll gain much performance if it was slow with an ftp location, but rather your VM is undersized for the task. Management server should be more sensitive to IO throughput than CPU or Memory. What are your VM specs?

There's also this document about performance considerations: https://dl.acronis.com/u/pdf/AcronisCyberBackup_12.5_BP_en-US.pdf