2017-09-10 15:45 GMT+02:00 Andreas Tscharner <[email protected]>:
> [...] > Today I wanted to restore two files from a one of the Windows clients > (backed up with Bareos 15.x). The files should be written to the /tmp > directory of the Linux server. It looked all OK > [...] Let's see if it's really ok :-) In the transcript file you attached, I see: cd Weekly > cwd is: C:/Users/bruno/Documents/BackupMaschinen/Maschine Dorf/Weekly/ > $ add * > 2 files marked. > $ lsmark > **FullDorf.BCK* > **FullDorf.LST* > $ done > It looks great..... But only if you're OK in knowing that your backup contains, for such a folder, only the _TWO_ files mentioned. So, first point: *if you need to restore one of those file.... than it's OK and let's step forward.* It you're searching for something else.... than you have a BIG problem (whose solution is out of scope of this answer) :-) Ok. So you need one of those two files. Let's see how BareOS handled the restore. Again, from you "transcript": 10-Sep 15:10 server-dir JobId 1096: Bareos server-dir 16.2.4 (01Jul16): > Build OS: x86_64-pc-linux-gnu debian Debian GNU/Linux > unstable (sid) > JobId: 1096 > Job: RestoreFiles.2017-09-10_15.09.34_33 > Restore Client: buero-pc2-fd > Start time: 10-Sep-2017 15:09:36 > End time: 10-Sep-2017 15:10:10 > Elapsed time: 34 secs > *Files Expected: 2 * > *Files Restored: 2* > Bytes Restored: 388,190,320 > Rate: 11417.4 KB/s > FD Errors: 0 > FD termination status: OK > SD termination status: OK > Termination: Restore OK > Wonderful! BareOS is telling us that it succesfully restored _TWO_ files. Exactly what we were expecting. So we simply need to get them. But... from *WHERE*? Let's see. When you launched the restore, you were prompted with this: JobName: RestoreFiles > Bootstrap: /var/lib/bareos/server-dir.restore.10.bsr > Where: /tmp/bareos-restores > Replace: Always > FileSet: Linux All > *Backup Client: buero-pc2-fd* > *Restore Client: buero-pc2-fd* > Format: Native > Storage: USBDisk > When: 2017-09-10 15:09:29 > Catalog: TscharnerMechanikCatalog > Priority: 10 > Plugin Options: *None* > OK to run? (yes/mod/no): yes > As you can see, BareOS correctly recognized the client from where the backup come from (the blue line). But, as you can see, the very same client (buero-pc2-fd) is also *WHERE* the restore will be performed (the red line). So I bet that if you search inside "*buero-pc2-fd*" for a */tmp/bareos-restores** folder*.... you'll find what you're searching. Based on what you wrote: > Nothing helped; the files just did not appear (or had length 0 if I > touched them before the restore). > [...] > root@*server*:/tmp/bareos-restores/C/Users/bruno/Documents/BackupMaschinen/Maschine > Dorf/Weekly# ls -l > total 0 > it looks you're searching for such files on BareOS server.... and NOT on buero-pc2-fd. Am I write? A final note: I really wonder _HOW_ the restore process will handle the unix-style path naming style (/tmp/bareos-restores) when restoring on a remote windows-based FD (buero-pc2-fd). Should you have problems... you could simply repeat the "restore" job by changing the "where" and choosing a linux-based FD. Please: I'm not saying that it doesn't work in windows. I'm simply saying that... I don't know how the translation will happen :-) HTH and.... happy BareOS to all :-) Bye, DV -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
