Update licenses

[bacula/docs] / docs / manual / win32.tex

diff --git a/docs/manual/win32.tex b/docs/manual/win32.tex
index c26bb95f3b4145c48bdfaf9161f76968e6f3f3c0..aa21045485133c93c75327162bad6d0b1fd8286b 100644 (file)
--- a/docs/manual/win32.tex
+++ b/docs/manual/win32.tex
@@ -246,6 +246,34 @@ trace=1 on a setdebug command in the Console, Bacula will write the debug
 information to the file {\bf bacula.trace} in the directory from which Bacula
 is executing. 
 
+If you are having problems with ClientRunBeforeJob scripts randomly dying, 
+it is possible that you have run into an Oracle bug.  See bug number 622 in
+the bugs.bacula.org database.  The following information has been
+provided by a user on this issue:
+
+\footnotesize
+\begin{verbatim}
+The information in this document applies to:
+ Oracle HTTP Server - Version: 9.0.4
+ Microsoft Windows Server 2003
+ Symptoms
+ When starting an OC4J instance, the System Clock runs faster, about 7
+seconds per minute.
+ 
+ Cause
+ 
+ + This is caused by the Sun JVM bug 4500388, which states that "Calling
+Thread.sleep() with a small argument affects the system clock". Although
+this is reported as fixed in JDK 1.4.0_02, several reports contradict this
+(see the bug in
+http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4500388).
+ 
+ + Also reported by Microsoft as "The system clock may run fast when you
+use the ACPI power management timer as a high-resolution counter on Windows
+2000-based computers" (See http://support.microsoft.com/?id=821893)
+\end{verbatim}
+\normalsize
+
 \label{Compatibility}
 \subsection*{Windows Compatibility Considerations}
 \index[general]{Windows Compatibility Considerations }
@@ -396,13 +424,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 +467,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 }