From 6156acd6f00ba8c4d44ea75391f6fe3d55a85ada Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Sun, 11 Jun 2006 14:47:28 +0000 Subject: [PATCH] Updates --- docs/developers/version.tex | 2 +- docs/manual-de/version.tex | 2 +- docs/manual/python.tex | 32 +++++++++++++++++++++++++++----- docs/manual/version.tex | 2 +- docs/manual/win32.tex | 29 ++++++++++++++++++++++------- 5 files changed, 52 insertions(+), 15 deletions(-) diff --git a/docs/developers/version.tex b/docs/developers/version.tex index b6045387..d690f26e 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -1.38.10 (04 June 2006) +1.38.10 (08 June 2006) diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex index b6045387..d690f26e 100644 --- a/docs/manual-de/version.tex +++ b/docs/manual-de/version.tex @@ -1 +1 @@ -1.38.10 (04 June 2006) +1.38.10 (08 June 2006) diff --git a/docs/manual/python.tex b/docs/manual/python.tex index ffed6bb6..64a702c0 100644 --- a/docs/manual/python.tex +++ b/docs/manual/python.tex @@ -33,11 +33,33 @@ runs in Bacula's address space, so even though it is an interpreted language, it is very efficient. When the Director starts, it looks to see if you have a {\bf -Scripts Directory} Directive defined, if so, it looks in that directory for -a file named {\bf DirStartUp.py}. If it is found, Bacula will pass this -file to Python for execution. The {\bf Scripts Directory} is a new -directive that you add to the Director resource of your bacula-dir.conf -file. +Scripts Directory} Directive defined (normal default {\bf +/etc/bacula/scripts}, if so, it looks in that directory for a file named +{\bf DirStartUp.py}. If it is found, Bacula will pass this file to Python +for execution. The {\bf Scripts Directory} is a new directive that you add +to the Director resource of your bacula-dir.conf file. + +Note: Bacula does not install Python scripts by default because these +scripts are for you to program. This means that with a default +installation with Python enabled, Bacula will print the following error +message: + +\begin{verbatim} +09-Jun 15:14 bacula-dir: ERROR in pythonlib.c:131 Could not import +Python script /etc/bacula/scripts/DirStartUp. Python disabled. +\end{verbatim} + +The source code directory {\bf examples/python} contains sample scripts +for DirStartUp.py, SDStartUp.py, and FDStartUp.py that you might want +to use as a starting point. Normally, your scripts directory (at least +where you store the Python scripts) should be writable by Bacula, because +Python will attempt to write a compiled version of the scripts (e.g. +DirStartUp.pyc) back to that directory. + +When starting with the sample scripts, you can delete any part that +you will not need, but you should keep all the Bacula Event and Job Event +definitions. If you do not want a particular event, simply replace the +existing code with a {\bf noop = 1}. \subsection*{Bacula Events} \index[general]{Bacula Events} diff --git a/docs/manual/version.tex b/docs/manual/version.tex index b6045387..d690f26e 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -1.38.10 (04 June 2006) +1.38.10 (08 June 2006) diff --git a/docs/manual/win32.tex b/docs/manual/win32.tex index c26bb95f..9c7dc002 100644 --- a/docs/manual/win32.tex +++ b/docs/manual/win32.tex @@ -396,13 +396,6 @@ Enable VSS = yes in your FileSet resource. -Important Note!! Under the current implementation, you may only -run a single job at a time in any Win32 File daemon that has VSS -active. Running multiple simultanous jobs in the File daemon -will most likely cause jobs to fail. This restriction does not apply -to the Director, Storage daemons, or any File daemons not running -VSS. - The VSS aware File daemon has the letters VSS on the signon line that it produces when contacted by the console. For example: \begin{verbatim} @@ -446,6 +439,28 @@ other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You a reports from each of the writer program. Here they all report VSS_WS_STABLE, which means that you will get a consistent snapshot of the data handled by that writer. +\subsection*{VSS Problems} +\index[general]{Problems!VSS} +\index[fd] {Problems!VSS} +\index[general]{VSS Problems} +\index[fd]{VSS Problems} +\addcontentsline{toc}{subsection}{VSS Problems} + +If you are experiencing problems such as VSS hanging on MSDE, first try +running {\bf vssadmin} to check for problems, then try running {\bf +ntbackup} which also uses VSS to see if it has similar problems. If so, you +know that the problem is in your Windows machine and not with Bacula. + +The FD hang problems were reported with {\bf MSDEwriter} when: +\begin{itemize} +\item a local firewall locked local access to the MSDE TCP port (MSDEwriter +seems to use TCP/IP and not Named Pipes). +\item msdtcs was installed to run under "localsystem": try running msdtcs +under networking account (instead of local system) (com+ seems to work +better with this configuration). +\end{itemize} + + \subsection*{Windows Firewalls} \index[general]{Firewalls!Windows } \index[general]{Windows Firewalls } -- 2.39.5