Tweak upload and Windows chapter

diff --git a/docs/manuals/en/main/win32.tex b/docs/manuals/en/main/win32.tex
index f36dc8a24ed82df7a15d2b8a21cedefbfa53a4b8..c1d74cc3a48dba6a9061614cd3c9abce4a0a249d 100644 (file)
--- a/docs/manuals/en/main/win32.tex
+++ b/docs/manuals/en/main/win32.tex
@@ -12,15 +12,16 @@ speak of the Windows version of Bacula below, we are referring to
 the File daemon (client) only. 
 
 The Windows version of the Bacula File daemon has been tested on WinXP,
-Win2000, Windows Server 2003, Windows Server 2008, Vista, and Windows 7
-systems.  The Windows version of Bacula is a native Windows port, but there
-are very few source code changes to the Unix code, which means that the
-Windows version is for the most part running code that has long proved
-stable on Unix systems.  When running, it is perfectly integrated with
-Windows and displays its icon in the system icon tray, and provides a
-system tray menu to obtain additional information on how Bacula is running
-(status and events dialog boxes).  If so desired, it can also be stopped by
-using the system tray menu, though this should normally never be necessary.
+Win2000, Windows Server 2003, Windows Server 2008, Vista, Windows 7, and
+Windows 2012 systems.  The Windows version of Bacula is a native Windows
+port, but there are very few source code changes to the Unix code, which
+means that the Windows version is for the most part running code that has
+long proved stable on Unix systems.  When running, it is perfectly
+integrated with Windows and displays its icon in the system icon tray, and
+provides a system tray menu to obtain additional information on how Bacula
+is running (status and events dialog boxes).  If so desired, it can also be
+stopped by using the system tray menu, though this should normally never be
+necessary.
 
 Once installed Bacula normally runs as a system service. This means that it is
 immediately started by the operating system when the system is booted, and
@@ -66,9 +67,9 @@ Some users have attempted to install logged in as a domain administrator
 account and experienced permissions problems attempting to run
 Bacula, so we don't recommend that option.
   
-\item Simply double click on the {\bf bacula-win32-5.xx.0.exe}  NSIS install
-   icon. The  actual name of the icon will vary from one release version to 
-   another. 
+\item Simply double click on the {\bf bacula-win32-5.xx.0.exe} NSIS install
+   icon.  The actual name of the icon will vary from one release version to
+   another.
 
 \includegraphics{\idir win32-nsis.eps}  bacula-win32-5.xx.0.exe  
   
@@ -123,31 +124,42 @@ Bacula, so we don't recommend that option.
 \ 
 \end{itemize}
 
-That should complete the installation process. When the Bacula File Server is
-ready to serve files, an icon \includegraphics{\idir idle.eps} representing a
-cassette (or tape) will appear in the system tray
-\includegraphics{\idir tray-icon.eps}; right click on it and a menu will appear.\\
-\includegraphics{\idir menu.eps}\\
-The {\bf Events} item is currently unimplemented, by selecting the {\bf
-Status} item, you can verify whether any jobs are running or not. 
+That should complete the installation process.  
 
-When the Bacula File Server begins saving files, the color of the holes in the
-cassette icon will change from white to green \includegraphics{\idir running.eps},
-and if there is an error, the holes in the cassette icon will change to red
-\includegraphics{\idir error.eps}. 
+\section{Tray Icon}
+\index[general]{Tray Icon}
+
+Note: this section does not apply to all Windows versions 
+later than Windows XP, since in those later versions Microsoft
+explicitly prohibits a system service such as Bacula from interacting
+with the user.
+
+On Windows XP, when the Bacula File Server
+is ready to serve files, an icon \includegraphics{\idir idle.eps}
+representing a cassette (or tape) will appear in the system tray
+\includegraphics{\idir tray-icon.eps}; right click on it and a menu will
+appear.\\ \includegraphics{\idir menu.eps}\\ The {\bf Events} item is
+currently unimplemented, by selecting the {\bf Status} item, you can verify
+whether any jobs are running or not.
+
+When the Bacula File Server begins saving files, the color of the holes in
+the cassette icon will change from white to green \includegraphics{\idir
+running.eps}, and if there is an error, the holes in the cassette icon will
+change to red \includegraphics{\idir error.eps}.
 
 If you are using remote desktop connections between your Windows boxes, be
-warned that that tray icon does not always appear. It will always be visible
-when you log into the console, but the remote desktop may not display it. 
+warned that that tray icon does not always appear.  It will always be
+visible when you log into the console, but the remote desktop may not
+display it.
 
 \section{Post Windows Installation}
 \index[general]{Post Windows Installation}
 \index[general]{Windows!Post Installation}
 
-After installing Bacula and before running it, you should check the contents
-of the configuration files to ensure that they correspond to your
-installation.  You can get to them by using:
-the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item.
+After installing Bacula and before running it, you should check the
+contents of the configuration files to ensure that they correspond to your
+installation.  You can get to them by using: the {\bf Start\-\gt{}All
+Programs\-\gt{}Bacula} menu item.
 
 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
 is running as a process (not an Application) with User Name SYSTEM. If this is 
@@ -155,6 +167,13 @@ not the case, you probably have not installed Bacula while running as
 Administrator, and hence it will be unlikely that Bacula can access
 all the system files.
 
+\section{Windows FD Restrictions}
+\index[general]{Windows FD Restrictions}
+In recent versions of Windows, Microsoft has implemented
+Volume Mount Points, Encrypted Volumes, and Deduplicated Volumes.
+Current versions of the Windows File daemon do not support
+any of these special Volume formats.
+
 \section{Uninstalling Bacula on Windows}
 \index[general]{Windows!Uninstalling Bacula}
 \index[general]{Uninstalling Bacula on Windows}
@@ -341,7 +360,7 @@ During backup, Bacula doesn't know about the system registry, so you will
 either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
 program specifically designed to make a copy or backup the registry. 
 
-In Bacula version 1.31 and later, we use Windows backup API calls by
+Bacula uses Windows backup API calls by
 default.  Typical of Windows, programming these special BackupRead and
 BackupWrite calls is a real nightmare of complications.  The end result
 gives some distinct advantages and some disadvantages.
@@ -418,27 +437,27 @@ message) } \\
 \\ \hline 
 \end{longtable}
 
-Note: with Bacula versions 1.39.x and later, non-portable Windows data can
-be restore to any machine.
-
+Note: Non-portable Windows data can be restore to any machine.  In
+addition, with recent Bacula versions, Bacula is able to extract data
+part from Windows backup streams when restoring on a non-Windows
+machine.
 
 \label{VSS}
 \section{Volume Shadow Copy Service}
 \index[general]{Volume Shadow Copy Service}
 \index[general]{VSS}
-Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
-a backup-solution for Windows, this is an extremely important step. VSS
-allows Bacula to backup open files and even to interact with applications like
-RDBMS to produce consistent file copies. VSS aware applications are called
-VSS Writers, they register with the OS so that when Bacula wants to do a
-Snapshot, the OS will notify the register Writer programs, which may then
-create a consistent state in their application, which will be backed up.
-Examples for these writers are "MSDE" (Microsoft database
-engine), "Event Log Writer", "Registry Writer" plus 3rd
-party-writers.  If you have a non-vss aware application (e.g.
-SQL Anywhere or probably MySQL), a shadow copy is still generated
-and the open files can be backed up, but there is no guarantee
-that the file is consistent.
+Microsoft added VSS to Windows XP and later systems.  From the perspective
+of a backup-solution for Windows, this is an extremely important step.  VSS
+allows Bacula to backup open files and even to interact with applications
+like RDBMS to produce consistent file copies.  VSS aware applications are
+called VSS Writers, they register with the OS so that when Bacula wants to
+do a Snapshot, the OS will notify the register Writer programs, which may
+then create a consistent state in their application, which will be backed
+up.  Examples for these writers are "MSDE" (Microsoft database engine),
+"Event Log Writer", "Registry Writer" plus 3rd party-writers.  If you have
+a non-vss aware application (e.g.  SQL Anywhere or probably MySQL), a
+shadow copy is still generated and the open files can be backed up, but
+there is no guarantee that the file is consistent.
 
 Bacula produces a message from each of the registered writer programs
 when it is doing a VSS backup so you know which ones are correctly backed
@@ -640,20 +659,21 @@ Thanks to Georger Araujo for the above information.
 
 If you restore files backed up from Windows to an alternate directory,
 Bacula may need to create some higher level directories that were not saved
-(or restored). In this case, the File daemon will create them under the SYSTEM
-account because that is the account that Bacula runs under as a service. As of
-version 1.32f-3, Bacula creates these files with full access permission.
-However, there may be cases where you have problems accessing those files even
-if you run as administrator. In principle, Microsoft supplies you with the way
-to cease the ownership of those files and thus change the permissions.
-However, a much better solution to working with and changing Windows permissions
-is the program {\bf SetACL}, which can be found at 
-\elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}. 
-
-If you have not installed Bacula while running as Administrator
-and if Bacula is not running as a Process with the userid (User Name) SYSTEM, 
-then it is very unlikely that it will have sufficient permission to
-access all your files. 
+(or restored).  In this case, the File daemon will create them under the
+SYSTEM account because that is the account that Bacula runs under as a
+service.  As of version 1.32f-3, Bacula creates these files with full
+access permission.  However, there may be cases where you have problems
+accessing those files even if you run as administrator.  In principle,
+Microsoft supplies you with the way to cease the ownership of those files
+and thus change the permissions.  However, a much better solution to
+working with and changing Windows permissions is the program {\bf SetACL},
+which can be found at
+\elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}.
+
+If you have not installed Bacula while running as Administrator and if
+Bacula is not running as a Process with the userid (User Name) SYSTEM, then
+it is very unlikely that it will have sufficient permission to access all
+your files.
 
 Some users have experienced problems restoring files that participate in
 the Active Directory. They also report that changing the userid under which

diff --git a/docs/upload b/docs/upload
index 0898378669923124471b49de303c8d181dc6b046..a3ea2f139b5c0a4d1a9507336db7eb01256f8a06 100755 (executable)
--- a/docs/upload
+++ b/docs/upload
@@ -28,14 +28,15 @@ dest=bacula:/var/www/bacula/5.2.x-manuals/${lang}
 echo "Sending to $dest"
 sendit $src $dest
 
-dest=bsweb:/var/www/docs/5.2.x-manuals/${lang}
-echo "Sending to $dest"
-sendit $src $dest
+# Community no longer on Bacula Systems server
+#dest=bsweb:/var/www/docs/5.2.x-manuals/${lang}
+#echo "Sending to $dest"
+#sendit $src $dest
 
 destdir=/home/frs/repo/htmldocs/${lang}/${ver}
 dest=bsweb:${destdir}
 ssh bsweb <<EOF
-mkdir -p ${destdir}
+mkdir -p ${destdir} 2>/dev/null 1>/dev/null
 EOF
 echo "Sending to $dest"
 sendit $src $dest