Unable to restore the data from backup: The agent is not suitable for this data type
Hi,
We are using Acronis12.5 Build 14330..
We are unable to restore some old backups, which shows the error message " The agent is not suitable for this data type.
The agent installed on machine 'XXXXXXX' cannot recover data of type ''. Please select another machine to browse from.
How to resolve this issue? Your help is highly appreciated.
Hello Binu,
welcome to Acronis forums!
Please make sure that you selected the right Agent to perform recovery from:
In my example, I selected VA (Virtual Appliance) Agent to recover MS SQL data which led to the error "The agent is not suitable for this data type".
Péter Szatmári wrote:Hi Thomas!
Could you share some details?
- Backed up machine OS
- Backup format (11 or 12)
- Backup type (file / disk / entire machine / application etc.)
Also have you tried a recovery with the Bootable Media?
-- Peter
Hi Peter,
- Backed up machine OS : Win Server 2012 R2
- Backup format (11 or 12): Automatic selection (12)
- Backup type (file / disk / entire machine / application etc.) : File Backup & Disk Backp
I am unable to see any details of the backup file as attached.
Maria Belinskaya wrote:Hello Binu,
welcome to Acronis forums!
Please make sure that you selected the right Agent to perform recovery from:
In my example, I selected VA (Virtual Appliance) Agent to recover MS SQL data which led to the error "The agent is not suitable for this data type".
Dear Maria,
I had tried different agents.. I had tried 14330, 14280,11010.. For all agents i am getting this notification & i am not able to see any details of the backup file except the size. This is happening after i upgrade the management server & Agents to the newest version.(14330). These backups are taken last year's on Tape drives. Any way to resolve this issue?
Hello Binu!
I have some more questions which might help:
- Have you tried recoverying with a bootable media?
- Is it possible that you have more SQL agents installed than you have licences for?
- Which version of acronis did you use for this tape backup from last year?
-- Peter
Péter Szatmári wrote:Hello Binu!
I have some more questions which might help:
- Have you tried recoverying with a bootable media?
- Is it possible that you have more SQL agents installed than you have licences for?
- Which version of acronis did you use for this tape backup from last year?
-- Peter
Dear Peter,
I did not understand what you mean by recovering with bootable media.. I am Trying to restore only files/documents which was backed up from our file server.
There is no SQL agents involved as this is only file backup.
I was using 11010 version to take backup last year..
Hello Binu,
this probably won't help you, but just in case:
We started to get this error message when we updated to v13440 from v11010. It was happening only for a few specific user accounts (others aren't getting this error) and it didn't matter what Agent we were using for browsing the Location (all versions behaved the same).
Eventually we found out that when the user is a Unit admin of more than one Unit, he will start getting these error messages in all Units, except for one (for some reason, one randomly selected Unit always works, other shows Agent error).
When we found out this, we also found temporary workaround - when user like that needs to access backups in Unit, where he is getting this error, "all" you need to do is to remove him from all Units except for the one, where the storage node, you need to access, is assigned to.
It's not nice, but at least it doesn't affect many of our users (only like 3 out of 50) and Acronis was able to replicate this issue on their side and promised to have it fixed in the next patch.
So, if you are browsing these archives with user account that is a admin member of more than one Unit (if you even have more than one Organization Unit), try to temporarily remove him from other Units, log off, log on and try it again.
Lukas
Brose wrote:Hello Binu,
this probably won't help you, but just in case:
We started to get this error message when we updated to v13440 from v11010. It was happening only for a few specific user accounts (others aren't getting this error) and it didn't matter what Agent we were using for browsing the Location (all versions behaved the same).
Eventually we found out that when the user is a Unit admin of more than one Unit, he will start getting these error messages in all Units, except for one (for some reason, one randomly selected Unit always works, other shows Agent error).When we found out this, we also found temporary workaround - when user like that needs to access backups in Unit, where he is getting this error, "all" you need to do is to remove him from all Units except for the one, where the storage node, you need to access, is assigned to.
It's not nice, but at least it doesn't affect many of our users (only like 3 out of 50) and Acronis was able to replicate this issue on their side and promised to have it fixed in the next patch.So, if you are browsing these archives with user account that is a admin member of more than one Unit (if you even have more than one Organization Unit), try to temporarily remove him from other Units, log off, log on and try it again.
Lukas
Dear Lukas,
Thanks for the response..
The "unit" means backup Location (vault) ? Please confirm.
Hello Binu,
no, by that I mean Units/Groups you see if you go to Administrators menu. There you can create and manage different Units which have their own admins, storage nodes, Agents etc.
It's very useful for company like ours, where we have dozens of storage nodes in different locations managed by different users.
Dear Brose,
We have not created any Units yet since its a small organization with very few storage nodes. Do i have to remove the admin account and try with other one?
Dear Binu,
no, in that case this is most probably different problem than we had and you should wait for response from Acronis (or create an incident for this, that could be faster).
Lukas
Hello Binu.
I had tried different agents.. I had tried 14330, 14280,11010.. For all agents i am getting this notification & i am not able to see any details of the backup file except the size
I do not mean to try an agent of another build. I mean to change the agent type. Please look at my screenshot above: you should click on Change and select that Agent that was used for creating the backup you need to restore.
Dear Maria,
Yes i changed the agent type as you said. it worked for only few backup files. Many backup files are still showing the same notification.
I guess the problem is with the agent type only. For Hyper-V Host machines, i reinstalled the agent version from 11010 to 14330 directly while updating the Management server Build from 11010 to 14280 then to 14330. Hyper-v Guest Machines are still having 11010 agent installed. I doubt If i update the agent in Hyper-V guests, will this issue happen for all the old backup files which was taken backup using 11010 agent?
had the same issue after upgrade from 11010 to 14330.
here is how I solved it:
1. do not go to "backups", go to "DEVICES" directly.
2. Stand on the device you want to restore or get access to it's backup.
3. Select restore point if you have many than 1.
4. Select the day of backup (you also will see the backup size). Choose backup file, press "Restore".
I don't have any changes in "Organization" settings, but I added one AD security group to the Acronis Administrators' group.
Hello SCH,
thanks for your clear instructions.
1. do not go to "backups", go to "DEVICES" directly.
2. Stand on the device you want to restore or get access to it's backup.
The way you described does not give any chance to make a mistake and select incorrect Agent: when the client goes to Devices and selects the exact device he needs to restore, then certainly the correct Agent will be selected.
Мария, этот метод работает только для физических машин.
автор этого топика товарищ Binu, судя по скриншотам, работает с виртуалками и поднимает ранее созданные образы ОС на новые виртуалки (клонирует). ему такой способ, наверное, не подходит.
ему подойдёт способ:
1. загружаешь guest OS с помощью acronis boot CD
2. выбираешь вручную ранее сохранённый образ (чистый образ ОС или другой типовой)
3. размечаешь вручную диск и ждёшь окончания развёртывания.
Well, this way also works for virtual machines.
Follow Devices -> Hyper-V (or VM ware) -> select the machine which backup is going to be restored -> Recovery:
The only disadvantage of this method is that this backup will be restored to the original machine.
In case if Binu wants to restore these files to another location, then he needs to follow the first method that I described in my first reply: follow Backups -> Locations -> select the machine (i.e. virtual machine) which Agent could browse the target location (e.g. if the target is Hyper-V VM, then a Hyper-V host could be selected on this stage).
Мария, добрый день!
в любом из случаев, что пробовал товарищ Binu, что описываете вы - везде будет выскакивать сообщение "this agent is not suitable for this data type". это людей и пугает, поэтому у них и вопросы.
раньше таких сообщений не было, поэтому люди привыкли, делая бэкап сервера А, иметь возможность восстановить данные сервера А на сервер А. а тут такое сообщение - сразу-же возникает вопрос - а совместимы ли ранее созданные бэкапы с новой версией агента 14330?
я понимаю причину этого сообщения - раньше была возможность восстановить бэкап рабочей станции на сервер, где стоит Акронис (по-умолчанию, выбран он) при условии, что сначала заходишь в "Резервные копии", а потом выбираешь дату восстановления. один из моих коллег один раз так и сделал - не выбрав "куда восстановиться", зашёл в бэкапы, выбрал дату и нажал "восстановить". спасло то, что зашли быстро в iLO и отменили операцию. поэтому с тех пор восстановление мы делаем так - сначала заходим в Устройства, затем выбираем дату бэкапа.
ваше новое сообщение при восстановлении заставляет людей думать перед восстановлением, но и заставляет сомневаться в совместимости версий.
я бы пометил красным прямоугольником область, где нужно указать "устройство, куда будет восстановлена резервная копия". и пока она не выбрана - не делал бы кнопку "восстановить" активной. примерно так, как вы сделали, например, с установкой расписания "последняя" + "пятница". без выбранного "последняя", но выбранной "пятница", бэкап работать не будет.
я я бы дождался ещё ответа товарища Binu, а то он что-то молчит.
Hello SCH.
The error "This agent is not suitable for this data type" is not new for Build# 14330, such behavior is natural since the previous version of the software - Acronis Backup 11.7: it also did not allow to restore specific backups with non-native Agents.
If you have not encountered this situation early means that you were pretty accurate with the Agents.
точно не было в 11010, с которого я сделал апгрейд до 14330. сейчас есть и видно каждый раз, когда заходишь в раздел резервных копий или в ленточные накопители.
если честно, у меня тоже по-началу стал возникать вопрос о совместимости. попробовал восстановление - вроде норм.
причина надписи - вы по-умолчанию в качестве агента "куда восстанавливать" воспринимаете сервер, на котором стоит web-console. если вы это уберёте и сделаете обязательным выбор компьютера или сервера, куда требуется восстановление (select machine), при этом кнопка RESTORE будет недоступна до этого выбора компьютера или сервера, то и надпись можно не выводить.
в 11010 надписи не было - можно было зайти в резервную копию рабочей станции и нажать восстановить - сразу начинается восстановление бэкапа рабочей станции на сервер, где стоит веб-консоль Акронис.
Hello SCH.
I've got your point. When Restore was not available under non-native Agent, our users were puzzled and started to contact Acronis Support Team. This message was added for information purposes in recent Update 4.