Re: [Bacula-users] Problem when restoring to a networked drive.
Thanks Bob,
We have decided that running the restore using the Director as the
client, is the best way forward. However, the issues have not changed :(
The following Job definition still saves to the remote client, using
C:\E\backup:
Job{
Name =CLIENT01-Restore
Type=Restore
Client =DIRECTOR
FileSet =CLIENT01
Storage=DIRECTOR-sd
Pool =CLIENT01
Messages =Standard
Where =\\E\\backup\\restored-files\\CLIENT01\\
}
...
If I exclude the leading \\'s the files are saved in
C:\WINDOWS\system32\E\backup
...
If I try E*:*\\backup... (nb. the colon)... I receive the following
error:
15-Feb 09:17 DIRECTOR-dir JobId 208: Start Restore Job
CLIENT01-Restore.2008-02-15_09.17.31
15-Feb 09:17 DIRECTOR-dir JobId 208: Using Device FileStorage
15-Feb 09:17 DIRECTOR-sd JobId 208: Ready to read from volume
CLIENT01-0006 on device FileStorage (E:\backup).
15-Feb 09:17 DIRECTOR-sd JobId 208: Forward spacing Volume
CLIENT01-0006 to file:block 0:209.
15-Feb 09:20 CLIENT01-fd JobId 208: Error: E: is not a valid drive
15-Feb 09:20 CLIENT01-fd JobId 208: Error:
../../findlib/create_file.c:223 Could not create
E:\backup\restored-files\CLIENT01\C\Documents and
Settings\CLIENT01\Local Settings\Application
Data\Microsoft\Outlook/Outlook.sharing.xml.obi: ERR=The system cannot
find the path specified.
15-Feb 09:20 CLIENT01-fd JobId 208: Error:
../../findlib/create_file.c:223 Could not create
E:\backup\restored-files\CLIENT01\C\Documents and
Settings\CLIENT01\Local Settings\Application
Data\Microsoft\Outlook/~last~.sharing.xml.obi: ERR=The system cannot
find the path specified.
15-Feb 09:20 CLIENT01-fd JobId 208: Error:
../../findlib/create_file.c:223 Could not create
E:\backup\restored-files\CLIENT01\C\Documents and
Settings\CLIENT01\Local Settings\Application
Data\Microsoft\Outlook/Outlook.pst: ERR=The system cannot find the path
specified.
=
Why does it use the remote client as the FD client, even though the
director is names as the client?
Thanks for your time
Dan
Bob Hetzel wrote:
In regard to your attempts to restore to a UNC path... in order to get
that to work you'll need to run the bacula-FD process as a user that
has permissions on both the destination where that UNC path resides
and where the bacula-fd process is running.
I believe it's going to be more fruitful to just change the
destination client name when you create the restore job and put it in
a folder local to that destination.
Bob
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problem when restoring to a networked drive.
[EMAIL PROTECTED] wrote:
Thanks Bob,
We have decided that running the restore using the Director as the
client, is the best way forward. However, the issues have not changed :(
The following Job definition still saves to the remote client, using
C:\E\backup:
Job{
Name =CLIENT01-Restore
Type=Restore
Client =DIRECTOR
FileSet =CLIENT01
Storage=DIRECTOR-sd
Pool =CLIENT01
Messages =Standard
Where =\\E\\backup\\restored-files\\CLIENT01\\
Quoting from
http://www.bacula.org/en/rel-manual/Configuring_Director.html#SECTION001411
-
If you are entering Windows file names, the directory path may be preceded by
the drive and a colon (as in c:). However, the path separators must be
specified in Unix convention (i.e. forward slash (/)).
-
If I recall correctly, the '\\' syntax worked in 1.38, but not in 2.x. Trying
using a Where line something like this:
Where = e:/backup/restored-files/CLIENT01
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problem when restoring to a networked drive.
[EMAIL PROTECTED] wrote: Hi Guys, I thought I had this game sorted. But, I found a bonus level. :) We have decided to save restored files onto a storage device attached to the Director Machine rather than putting them straight onto the original client. My problem is that while I can restore files for the Director machine, a restore job for remote clients prints a success report but will not actually write the file! I have defined the location to write the restored files in the restore job, as shown below: Where= MACHINE01\\E\\backup\\restored-files\\REMOTE01\\ ... After running the restore job, I check the result with 'Status' and it summarises the job as complete: --- Jodid Files Bytes Status Finished Name 1814365.7 M OK 14-Feb-08 12:21 REMOTE01-Restore However, the folder is still empty! :( Are you looking on the correct client? Compare the Job output that was emailed to you. Or the job output in the log file in the Director's working directory. Perhaps the file is on another Client or on the Director Perhaps it is in a different directory, say /tmp/bacula-restores instead. You'll have to look at the job to know. -- Dan Langille - http://www.langille.org/ BSDCan - The Technical BSD Conference: http://www.bsdcan.org/ PGCon - The PostgreSQL Conference:http://www.pgcon.org/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Problem when restoring to a networked drive.
Thanks Dan :) I have now triple checked my paths, and visually confirmed that the REMOTE clients FD monitor is lit up green with a 'Running' status. I have provided the console printout, and the Job log. It all seems to confirm I am pointing to everything correctly. One possibility that I am trying to eliminate: While I can browse to the networked drive, and edit files from the client machine (REMOTE01). I did not have the option for 'Write' permissions when I applied the share status to the E drive. Would this have any effect on the daemons' write ability? How can I test this? This is a simplified copy of the bconsole printout: == *restore To select the JobIds, you have the following choices: 5: Select the most recent backup for a client Select item: (1-12): 5 Defined Clients: 4: REMOTE01 Select the Client (1-9): 4 Automatically selected FileSet: REMOTE01 +---+---+--+-+-+--+ | JobId | Level | JobFiles | JobBytes | StartTime | VolumeName | +---+---+--+-+-+--+ | 8 | F | 5 | 363,679,791 | 2008-02-06 13:27:59 | REMOTE01-0006| +---+---+--+-+-+--+ You have selected the following JobIds: 8,25,48,67,85,103,129,147,165 Building directory tree for JobId 8 ... 1 Jobs, 4 files inserted into the tree. cwd is: / $ mark * 6 files marked. $ done Bootstrap records written to C:\Documents and Settings\All Users\Application Data\Bacula\Work\/MACHINE01-dir.restore.34.bsr The job will require the following Volume(s) Storage(s) SD Device(s) === REMOTE01-0006 MACHINE01-sd FileStorage 6 files selected to be restored. The defined Restore Job resources are: 4: REMOTE01-Restore Select Restore Job (1-9): 4 Using Catalog "REMOTE01" Run Restore job JobName: REMOTE01-Restore Bootstrap: C:\Documents and Settings\All Users\Application Data\Bacula\Work\/MACHINE01-dir.restore.34.bsr Where: \\esiteprod01\E\backup\restored-files\REMOTE01 Replace: always FileSet: REMOTE01 Backup Client: REMOTE01 Restore Client: REMOTE01 Storage: MACHINE01-sd When: 2008-02-14 13:04:23 Catalog: REMOTE01 Priority: 10 OK to run? (yes/mod/no): yes Job queued. JobId=184 After running the Job, it is shown as successful in the FD monitor. I run status for a better report: *status Status available for: 1: Director 2: Storage 3: Client 4: All Select daemon type for status (1-4): 3 The defined Client resources are: 4: REMOTE01 Select Client (File daemon) resource (1-9): 4 Connecting to Client daniels at 10.0.0.130:9102 MACHINE01-fd Version: 2.2.7 (24 December 2007) VSS Linux Cross-compile Win32 Daemon started 04-Feb-08 14:17, 23 Jobs run since started. Heap: heap=0 smbytes=228,419 max_bytes=295,547 bufs=82 max_bufs=103 Sizeof: boffset_t=8 size_t=4 debug=0 trace=0 Running Jobs: Director connected at: 14-Feb-08 13:14 No Jobs running. Terminated Jobs: JobId Level Files Bytes Status Finished Name == 184 5 365.7 M OK 14-Feb-08 13:08 REMOTE01-Restore This agrees with the FD monitor. I then view the log file and confirm that everything agrees. Directors LOG FILE: 14-Feb 13:04 MACHINE01-dir JobId 184: Start Restore Job REMOTE0101-Restore.2008-02-14_13.04.22 14-Feb 13:04 MACHINE01-dir JobId 184: Using Device "FileStorage" 14-Feb 13:04 MACHINE01-sd JobId 184: Ready to read from volume "REMOTE01-0006" on device "FileStorage" (E:\backup). 14-Feb 13:04 MACHINE01-sd JobId 184: Forward spacing Volume "REMOTE01-0006" to file:block 0:209. 14-Feb 13:05 MACHINE01-sd JobId 184: End of Volume at file 0 on device "FileStorage" (E:\backup), Volume "REMOTE01-0006" 14-Feb 13:05 MACHINE01-sd JobId 184: End of all volumes. 14-Feb 13:05 MACHINE01-dir JobId 184: Bacula MACHINE01-dir 2.2.7 (24Dec07): 14-Feb-2008 13:05:06 Build OS: Linux Cross-compile Win32 JobId: 184 Job: REMOTE01-Restore.2008-02-14_13.04.22 Restore Client: REMOTE01 Start time: 14-Feb-2008 13:04:29 End time: 14-Feb-2008 13:05:06 Files Expected: 6 Files Restored: 5 Bytes Restored: 365,711,407 Rate: 884.1 KB/s FD Errors: 0 FD termination status: OK SD termination status: OK Termination: Restore OK -- warning file count mismatch 14-Feb 13:05 MACHINE01-dir JobId 184: Begin pruning Jobs. 14-Feb 13:05 MACHINE01-dir JobId 184: No Jobs found to prune. 14-Feb 13:05 MACHINE01-dir JobId 184: Begin pruning Files. 14-Feb 13:05 MACHINE01-dir JobId 184: No Files found to prune. 14-Feb 13:05 MACHINE01-dir JobId 184: End auto prune. === I have also searched all drives on both computers for the test file, with no success. Best Regards, Daniel Simeoni Support Coordinator
Re: [Bacula-users] Problem when restoring to a networked drive.
I apologise, please disregard the last post.
After another search, with a bit more sense than I used the first time.
I have found that the file was in-fact restored to the following local
(Clients') directory::
C:\MACHINE01\E\backup\restored-files\REMOTE01\C\Documents and
Settings\REMOTE01\etc...etc
Instead of the remote (Directors') directory as defined in the job
definition:
Job {
Name = "REMOTE01-Restore"
Type = Restore
Client = REMOTE01
FileSet = REMOTE01
Storage = MACHINE01-sd
Pool = REMOTE01
Messages= Standard
Where =
"MACHINE01\\E:\\backup\\restored-files\\REMOTE01\\"
}
Can I make Bacula obey the path, rather than assuming \\ =
C:\MACHINE-name\ or must I try the other option...
I have already tried mapping the Remote drive to E: locally but this
prints the error below. Suggesting that I need to find a way to escape
the '/' which is automatically added to the save path. I have not been
able to accomplish this as yet.
Job REMOTE01-Restore.2008-02-14_16.43.24
14-Feb 16:43 MACHINE01-dir JobId 186: Using Device "FileStorage"
14-Feb 16:43 MACHINE01-sd JobId 186: Ready to read from volume
"REMOTE01-0006" on device "FileStorage" (E:\backup).
14-Feb 16:43 MACHINE01-sd JobId 186: Forward spacing Volume
"REMOTE01-0006" to file:block 0:209.
14-Feb 16:47 REMOTE01-fd JobId 186: Error: E: is not a valid drive
14-Feb 16:47 REMOTE01-fd JobId 186: Error:
../../findlib/create_file.c:223 Could not create
E:\backup\restored-files\REMOTE01\C\Documents and
Settings\REMOTE01\Local Settings\Application
Data\Microsoft\Outlook/Outlook.sharing.xml.obi: ERR=The system cannot
find the path specified.
14-Feb 16:47 REMOTE01-fd JobId 186: Error:
../../findlib/create_file.c:223 Could not create
E:\backup\restored-files\REMOTE01\C\Documents and
Settings\REMOTE01\Local Settings\Application
Data\Microsoft\Outlook/~last~.sharing.xml.obi: ERR=The system cannot
find the path specified.
14-Feb 16:47 REMOTE01-fd JobId 186: Error:
../../findlib/create_file.c:223 Could not create
E:\backup\restored-files\REMOTE01\C\Documents and
Settings\REMOTE01\Local Settings\Application
Data\Microsoft\Outlook/Outlook.pst: ERR=The system cannot find the path
specified.
Thanks again.
Dan
[EMAIL PROTECTED] wrote:
Thanks Dan :)
I have now triple checked my paths, and visually confirmed that the
REMOTE clients FD monitor is lit up green with a 'Running' status.
I have provided the console printout, and the Job log. It all seems to
confirm I am pointing to everything correctly.
One possibility that I am trying to eliminate:
While I can browse to the networked drive, and edit files from the
client machine (REMOTE01). I did not have the option for 'Write'
permissions when I applied the share status to the E drive. Would this
have any effect on the daemons' write ability? How can I test this?
This is a simplified copy of the bconsole printout:
==
*restore
To select the JobIds, you have the following choices:
5: Select the most recent backup for a client
Select item: (1-12): 5
Defined Clients:
4: REMOTE01
Select the Client (1-9): 4
Automatically selected FileSet: REMOTE01
+---+---+--+-+-+--+
| JobId | Level | JobFiles | JobBytes | StartTime |
VolumeName |
+---+---+--+-+-+--+
| 8 | F | 5 | 363,679,791 | 2008-02-06 13:27:59 |
REMOTE01-0006|
+---+---+--+-+-+--+
You have selected the following JobIds: 8,25,48,67,85,103,129,147,165
Building directory tree for JobId 8 ...
1 Jobs, 4 files inserted into the tree.
cwd is: /
$ mark *
6 files marked.
$ done
Bootstrap records written to C:\Documents and Settings\All
Users\Application Data\Bacula\Work\/MACHINE01-dir.restore.34.bsr
The job will require the following
Volume(s) Storage(s) SD Device(s)
===
REMOTE01-0006 MACHINE01-sd FileStorage
6 files selected to be restored.
The defined Restore Job resources are:
4: REMOTE01-Restore
Select Restore Job (1-9): 4
Using Catalog "REMOTE01"
Run Restore job
JobName: REMOTE01-Restore
Bootstrap: C:\Documents and Settings\All Users\Application
Data\Bacula\Work\/MACHINE01-dir.restore.34.bsr
Where: \\esiteprod01\E\backup\restored-files\REMOTE01
Replace: always
FileSet: REMOTE01
Backup Client: REMOTE01
Restore Client: REMOTE01
Storage: MACHINE01-sd
When: 2008-02-14 13:04:23
Catalog: REMOTE01
Priority: 10
OK to run? (yes/mod/no): yes
Job queued. JobId=184
After running the Job, it is shown as successful in the FD monitor. I
run status for a better report:
*status
Status available for:
1: Director
2: Storage
3: Client
4: All
Select daemon type for status (1-4): 3
The defined Client resources are:
4:
