Try to recover Backup Image using Bootable media : Unable to view the recovery image

Recover of the whole machine in step 2 requires reboot to the linux-based environment very similar to the bootable cd used in step 3, so if recover in step 2 actually worked, network adapters and other hardware was successfully detected and should work fine in step 3 too. can you post a couple of screenshots of your actions on step 3 ? (In 'Advanced' editions it's possible to connect to the bootable media from the desktop Management console, otherwise you have to use a digital camera).
If you store your backups in managed vault, you need to point to the Storage Node that manages this vault, not a network folder where vault is located.

Hi, actually there is a difference between the two pratice, because using the AMS to make the recovering means that all order are sent from the AMS and received by the local client. By using the bootbale CD the Interface is not the same.

My issue is that by making some backup with AMS, the format of the backup is different than making it with bootable CD. Indeed, the tree of folder created with AMS is much more complicated (more powerful for sure), but this tree is then no well recognized by the bootable CD. For Example, when I try to map the backup file that I want to restore from the bootbale CD and using the network, I can see an "Archive", the name of the backup, but with 0 Bytes data. Even when I look at it with the AMS everything appears as normal... So I don't understand the difference.

As requested, I put you some screen shot from my issue enclosed. the first print screen show you the backup made with AMS and seen from the AMS, everything look like normal and I can restore de file. By using the bootable CD (second print screen) from the remote station (in case of afull crash), I can see some file but impossible to recover.

You missed the screenshots.

Here above updated

The backups in a centralized unmanaged vault created as a result of execution of a centralized backup plan
have the same strcuture as created in a personal vault or using bootable media. Here it looks like
access permissions or network connectivity issue where .tib files can't be read. At this point I'm about to
suggest you to contact the support, as I don't see obvious errors here, but you can check my suggestion above - if you copy the backups
(tib and xml files) from the centralized vault to the local disk of machine to be recovered, and
browse them there from the bootable media - will it work?

I tried to make the test by using a removable Hard drivre.

I copied all the backup files & folders from my AMS to a removable hard drive and tried to recover them from the bootable media on the dedicated workstation.

Result is the same. No data can be seen.

See screen shot :

- Hard driver screen shot : The document that have been copied from AMS to the hard drive. We can see that .TIB file are present.

- Bootable media : In the same level of the tree no data can be seen

Any ideas ? Again, if I make the same process by using a backup that has been made from the bootable media, everything can be seen without issue from the bootable media (which seems to be normal). However, the backup made from the bootable media cannot be seen from the AMS.

So the issue is on both ways :

backup made With bootable Media ==> Recover possible from bootable media (not possible using AMS)
backup made with AMS ==>Recover possible from AMS only (not possible using bootable media)

For information, the backup as been made on the AMS using backup plan and "Managed vault" and not "unmanaged" as you said above. Does it make a difference ??

How is it possible to get connect from AMS to bootable media as you said above ? Even the network as been configured on the workstation with bootable media (ping to AMS ok) I cannot get connected to it using AMS ->Connect->New connection-> Manage this machine...

Could you please explain the process to follow ?

Thanks

On on_removable_disk_.jpg is folder structure of a managed vault, and you using it in a wrong way. It is supposed to be used only being attached to a storage node, and from bootable media you need to enter path like bsp://StorageNodeNameOrIp/VaultName to get access to archives. If you need to create a backups and carry them on a usb disk, use an unmanaged vault (or personal vault, accessible only from one agent). Archives in an unmanaged vault can be read directly by agent (or bootable media which is an agent too)

>For information, the backup as been made on the AMS using backup plan and "Managed vault" and not "unmanaged" as you said above. Does it make a difference ??

Yes, it makes a huge difference.

How is it possible to get connect from AMS to bootable media as you said above ? Even the network as been configured on the workstation with bootable media (ping to AMS ok) I cannot get connected to it using AMS ->Connect->New connection-> Manage this machine...

You need to create a bootable media with 'allow remote connection' option enabled (is offered on some step), and use Connect->'Manage remote machine' menu in management console.

It works perfectly !!! Thank you very much !!

For Managed Vault and backup made with AMS : it's needed to use the "Storage node" with bsp://StorageNodeNameOrIp/VaultName ==> Works !

For the Remote connection, to allow it from the AMS : It's needed to create the bootable media with Remote settings including "User" and "Password" otherwise it's not possible to get connect to it, the "OK" button remain inactive.

Thank you very much for your support !