We do plan to expose the RO file system via API. This is not yet scoped, but I hope to get it in within the year. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary On Thu, Dec 1, 2016 at 3:07 PM, Victor Jose Acosta <vic.ad94@gmail.com> wrote:
yes can cause corruption, but i don't want to modify file system externally, i just want to read it and then copy to the production host by agent/scp or something
On 01/12/16 09:43, Yaniv Dary wrote:
I understand, you mean a single file restore use case. This is usually done by a agent in the VM and not externally, since changing the file system externally can cause corruption.
Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109
Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary
On Wed, Nov 30, 2016 at 3:47 PM, Victor Jose Acosta <vic.ad94@gmail.com> wrote:
Ok ok
When you make a full restore you have a whole new VM, but what if you just need just one directory? "/etc/puppet/environments" for example
So there is where granular backup works, because if you don't have that option you will have to restore the whole VM, copy that directory, then delete the restored VM
I don't know if my english is good enough to explain perfectly, but do you understand my point?
On 30/11/16 10:36, Yaniv Dary wrote:
I believe that both full and granular restore can be done via the API as we support offset uploads, can you give more details on the different between these options?
--
--
