Plase add a command line option to: ignore the access_keys.properties (if i’m doing a bare metal restore there is no access_keys.properties)
i fiddled around nearly 4 hours for this…
please also add an option to continue restore on errors… if i restore a linux client into a fresh “running” system there will be always errors
PS: How is the Pathmapping supposed to work? i can’t figure it out
just to be clear here…
i figured it out what was missing…
you have to run a backup first. that will generate the access_key.properties.
then you can start a restore with RESTORE=server-confirms
Will test it this evening with restoring the system from a live cd…
would -p root --map-from / --map-to /tmp/restore/ work too?
aaaand the next one…
urbackupclientctl restore-start -b 450 -d / --map-from / --map-to /restore/ -n
map does not work…
it simply ignores it and restores the files to /root/
and in the middle of restoring it switches to / and kills the installation again…
doing subdirs does not work either…
server tells it cant find /bin
i think it just removes the root/
what i have found until now:
directory symlinks do not work on restored… they are restored as directories and not as links.
think the same applies to file symlinks…
there is no continue on error function. if it runs into an error the server stops sending data and the client sits there forever waiting.
as that server is essential to me i’m willing to test everything you can throw at me to restore it…
i think the most important thing is that the server handles backed up symlinks correct on restore.
where it actually restores does not matter as long its a subdirectory on the client where i can mount the filesystem
2016-06-08 11:35:19: ClientService cmd: #IgBscp4XCLEwZysPRdwvJ#FILE RESTORE client_token=bK/+HYM9FIbQxrh7Xaw0NlMDZOoNWNCmkE1FWRADg5u3OP9Ib0KFH4nOkHcvJUWL47Pr5xhndmIg&server_token=D3mrcNC8jJcaW60huSLV&id=8&status_id=7&log_id=10&restore_path=root%2Fglftpd&single_file=0&clean_other=1&ignore_other_fs=1&tgroup=0&clientsubname=
terminating with uncaught exception of type CryptoPP::HashVerificationFilter::HashVerificationFailed: HashVerificationFilter: message hash or MAC not valid
Nevermind… fixed it… crypto++ was not installed…
had to run the client in gdb to see the error… nothing was logged at all. just crashed silently…