Network Drives cannot be used - Some comments/suggestions
I am aware that Acronis Backup 11.5 does not support mapped network drives as locations for backup/recovery and this causes us real problems.
The path we need to browse to is an extremely long path and this can cause problems, apart from the fact that it is time consuming to traverse the folder structure (or to type it in) it also possible to run into the Windows maximum path length limit of 260 characters (which is a limitation of the Windows API)
If there are no plans to add this feature to use network drives back in (it was possible in Version 10) then may I suggest something that may help.
Would it be possible to add a form of 'Favourites' to the interface where users can save commonly used locations for quick selection?
This would help with the problem of having to type of traverse deep within a folder structure (of course it will not help with the maximum path length issue)
Are there any plans to add network drive support back in?
Thanks
Steve
OK, thanks for your comments
I have some questions, on our server we run the Acronis license server, then on 4 desktops in our company we run the management console. The purpose of these 4 consoles is to recover a single image of a hard drive for one of our products. There is only 1 master image (a .tib file) and this is currently stored on our server. Each of these 4 consoles will use this master image to recover to a hard drive temporarily connected to there machine for this purpose.
The question is how do I use vaults in this scenario. If I run the management console on my machine and select Vaults -> Centralized there are none, and I cannot create any. Do I need a centralized vault? If so will the other consoles be able to recover from it?
Do I need to create a 'Personal Vault' ? but if I do will this be a vault that only I then can recover from...or can any of the other 3 consoles recover from or write to?
Any advice appreciated.
Clarifying terminology - console itself and where it is run is pretty much irrelevant. What is important is what it is connected to - Managed Machine (Agent) or Management Server. Vaults are not stored in the console too, they belong to Management Server (centralized, they are propagated to agents that this server manages) and Agent (personal).
In your scenario where on of the set of master images are frequently restored (and AMS-Agent relationship is probably broken after restore) you might consider other product instead - Acronis SnapDeploy.
Hi
Thanks for your comments. I guess the problem is we use Acronis in an unusual manner. I have already had many conversations with Acronis about the best product for us and snap deploy was not acceptable. I can already use Acronis Backup 11.5 for my requirements and can recover a master .tib image from our network from each console....I just have to browse deep into a directory structure each time to find the .tib file. We are not in a position to change products and was just hoping there was (or may be in the future) a simple solution to this problem.
Should (and can I with the product I have) install management server, will I then be able to create the centralized vault (unmanaged?) and then register the 4 consoles with the server to enable them to connect to the vault and recover from it? If I can, do I install the management server program directly on to our server?
Thanks
Steve
Should (and can I with the product I have) install management server, will I then be able to create the centralized vault (unmanaged?) and then register the 4 consoles with the server to enable them to connect to the vault and recover from it?
Again, you don't 'register' console anywhere. It may sound as nitpicking, but the same console can connect to and manage Management Server as well as Agent. If you have License Server then you have Advanced edition and you can install Management Server on some machine (e.g. on the machine with License Server) and register agents in it and they will get centralized vaults to recover from. What will happen when you restore some of your images on this machine? If the image was created before registering the machine in Management Server, then in the image agent state is 'not registered on AMS'. You will need to go to 'menu->machine options' and provide address of Management Server again.
OK...I think I am getting there....sorry for so many questions
Maybe I should give it a go. One final question however (I hope!).
Does the computer running management server have to be on all the time, or is all of the relevant information about the vault stored within the vault (maybe as metadata). The reason I ask this is that I only like to install programs onto our server if there is no other viable option. If the machine that has management server installed on, has to be powered on all the time (for possible communication with other agents) then I will have to install it on the server, if it does not, then I will install it onto a desktop machine that has the management console installed.
Thanks again
Agents can function without connection to Management Server. Once they receive information about unmanaged vaults, they can use them without interaction with AMS. So you need to turn on AMS in your scenario only to deploy vaults or register a new machine. Desktop machine is OK if it is not a Home edition of Windows. Professional and above is ok.