-----BEGIN PGP SIGNED MESSAGE-----
Marek Marczykowski-Górecki wrote:
> On Fri, Jan 30, 2015 at 02:30:45AM +0400, Oleg Artemiev wrote:
>> clarification: the backupping fails only when symlinks has been
>> made by root.
>> If the symlink is owned by the user that owns the image - image
>> size to backup is still displayed incorrectly as size of
>> symlink, but backup works okay.
> And the backup contains only a *symlink*, not the actual file... So
> for now you need to backup your HDD manually. Perhaps we will solve
> this problem in the future, but simply following the symlinks isn't
> the best option, because we need to properly backup symlinks in
> some places (at least icon.png).
Maybe I'm misunderstanding you, Marek, but I just tried restoring one
of my backed up AppVMs, the directory of which was symlinked to a
secondary drive at the time of the backup, and the restored AppVM
contains all of my user data. (So, it appears the backup was not only
a symlink; rather, it contained my actual data). Does the issue you
are describing arise when only the private.img file is symlinked
(rather than the whole AppVM directory being symlinked)?
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----