Differences

This shows you the differences between two versions of the page.

--- computing:backup:ahsay_troubleshoot [2014/12/10 10:25]
gcooper
+++ computing:backup:ahsay_troubleshoot [2024/01/23 17:52] (current)
gcooper
@@ Line 4: / Line 4: @@
 http://thinkbackup.net/dynamic_content.php?id=76
+===== License =====
+**Permit 203.186.85.237** to the Ahsay OBS server.
 ===== Configuration Folder =====
@@ Line 11: / Line 15: @@
 <file>
 notepad C:\Program Files\AhsayOBM\home.txt
+#or
+notepad C:\Program Files\AhsayACB\home.txt
 </file>
 ===== Roaming Profiles and Multiple Machines =====
-FIXME I think we need to use a dedicated account or the local administrator account, then perform the configurations and backups as that user.
+Only the OBM backup client can support multiple machines on the same backup account.
-Since Ahsay OBM uses an in-profile location for its configuration folder, you will run into problems due to multiple machines using the same .obm configuration folder.
+Use separate Windows accounts (separate profile directories) on each machine to run OBM.
-:!: The solution is to modify all subsequent machines added to the same Ahsay backup account.
+We generally use:
-Copy the initially created .obm folder to a location on the subsequent machine rights to the "Temporary Directoryto a location not in the redirected folders or roaming profile.  For example:
+  * The AD Domain Administrator account on the primary file server
+  * The local Administrator account on each subsequent machine in the domain
-From:
-<file>
-\\DC1\Redirected$\administrator\.obm
-</file>
-To:
-<file>
-C:\Users\administrator.FF\.obm
-</file>
-Then edit the ''home.txt'' file on the subsequent machine to point to the new location:
-<file>
-notepad 'C:\Program Files\AhsayOBM\home.txt
-</file>
-<file>
-C:\Users\administrator.FF\.obm
-</file>
-Restart the OBM services:
-<file>
-net stop "OBScheduler"
-net stop "OBAutoUpdate"
-net stop "OBCDPService"
-net start "OBScheduler"
-net start "OBAutoUpdate"
-</file>
-:!: If you need CDP, restart "OBCDPService" too.
 ===== Missed Backups =====
-http://forum.ahsay.com/viewtopic.php?t=6772
+https://www.ahsay.com/blog/2017/08/22/top-8-reasons-for-missed-backups-when-using-ahsay-backup-software
-https://support.c4l.co.uk/index.php?/Knowledgebase/Article/View/43/0/backup-job-that-is-scheduled-to-be-perform-is-not-starting-missed-backup
 ==== Common Causes of Missed Backups ====
@@ Line 68: / Line 39: @@
   - Verify **sufficient temporary disk space** or change location
   - The SQL Service Account does not have **rights to the "Temporary Directory for storing backup files"**
+  - Multiple administrators have run the OBM client
+    * This creates a ''.obm'' folder in each user's home directory causing confusion
+    * Delete all duplicate ''.obm'' folders in all home directories
+    * Verify the contents of ''C:\Program Files\AhsayOBM\home.txt''
 ==== Linux ====
@@ Line 173: / Line 148: @@
 http://forum.ahsay.com/viewtopic.php?t=4410
+=== Restart OBM Services ===
+:!: If you need CDP, restart ''OBCDPService'' too.
 <file>
@@ Line 179: / Line 158: @@
 net stop "OBCDPService"
 net start "OBScheduler"
+net start "OBAutoUpdate"
+</file>
+== RestartOBM.bat ==
+If you see the **error** ''Another scheduler is running!'' in the ''info.log'', try this script:
+<file>
+rem ----------------
+rem Stop Services
+rem ----------------
+net stop "OBscheduler"
+net stop "OBAutoUpdate"
+rem ----------------
+rem kill tasks if hung
+rem ----------------
+taskkill /F /IM Aua.exe
+taskkill /F /IM AuaJW.exe
+taskkill /F /IM bJW.exe
+taskkill /F /IM Scheduler.exe
+taskkill /F /IM bschJW.exe
+taskkill /F /IM SystemTray64.exe
+rem ----------------
+rem Delete rogue files from hung processes
+rem ----------------
+cd "%ProgramFiles%\Ahsay OBM\ipc"
+del /s /q running
+del /s /q stop
+del /s /q start
+cd \cd "%userprofile%\.obm
+del /s /q running
+del /s /q stop
+del /s /q start
+rem ----------------
+rem start services
+rem ----------------
+net start "OBscheduler"
 net start "OBAutoUpdate"
 </file>
@@ Line 225: / Line 249: @@
 ===== Outlook =====
-{{ :computing:backup:closeoutlook.png?direct&300|Close Outlook Pre-Command}}
+{{ :computing:backup:closeoutlook.png?direct&450|Close Outlook Pre-Command}}
 Use a pre-backup script to close Outlook.  This is probably very useful with Terminal Servers.
@@ Line 263: / Line 287: @@
 Suspend the account that is running.  Let job stop then re-enable.
-===== Local Copy - Index Corrupted =====
+===== Local Copy =====
-Delete the corrupted index files ''index.bdb'' and ''r-index.bdb'' from the Local Copy data.
+==== Destination Unavailable ====
+Use the Command Line Tool to add ''Pre'' and ''Post'' commands:
+<file>
+net use z: \\DOMAIN\Server /user:DOMAIN\backupadminuser backupadminpass
+net use z: /d /y
+</file>
+===== Index Corrupted =====
+Cancel the problematic backup job if it is running.  You may have to stop the ''obsr'' service in some cases.
+Delete the corrupted index files ''index.bdb'' and ''r-index.bdb'' (and lock files) from destination data.
+==== Online Copy ====
+The index files can be found in the following directory of the server:
+<file>
+/mountpoint/<username>/files/<backup_set_id>/
+</file>
+Start a single user rebuild (file validation option) with verify checksum enabled.
+Once the rebuild job has completed, check the user log for any errors such as corrupted files.
+==== Local Copy ====
 The index files can be found in the following directory of the Local Copy destination:
 <file>
-Local_Copy_Destination\server_name\username\files\backup_setID
+<local_copy_destination>\<servername>\<username>\files\<backup_set_id>\
 </file>
+The indexes will be rebuilt during the next backup.
+===== Client Debug Mode =====
+https://forum.ahsay.com/viewtopic.php?f=117&t=10377&p=39615

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools