Virtual Architects Support Wiki

User Tools

Site Tools

You are here: start » computing » backup » ahsay_troubleshoot
Trace:
computing:backup:ahsay_troubleshoot

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
computing:backup:ahsay_troubleshoot [2015/06/01 09:34]
gcooper 		computing:backup:ahsay_troubleshoot [2024/01/23 17:52] (current)
gcooper
Line 4: Line 4:
  
 http://thinkbackup.net/dynamic_content.php?id=76 http://thinkbackup.net/dynamic_content.php?id=76
 +
 +===== License =====
 +
 +**Permit 203.186.85.237** to the Ahsay OBS server.
  
 ===== Configuration Folder ===== ===== Configuration Folder =====
Line 11: Line 15:
 <file> <file>
 notepad C:\Program Files\AhsayOBM\home.txt notepad C:\Program Files\AhsayOBM\home.txt
 +#or
 +notepad C:\Program Files\AhsayACB\home.txt
 </file> </file>
  
Line 22: Line 28:
  
   * The AD Domain Administrator account on the primary file server   * The AD Domain Administrator account on the primary file server
-  * The local Administrator account on each subsequent machine+  * The local Administrator account on each subsequent machine in the domain
  
 ===== Missed Backups ===== ===== 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 ==== ==== Common Causes of Missed Backups ====
Line 35: Line 39:
   - Verify **sufficient temporary disk space** or change location   - Verify **sufficient temporary disk space** or change location
   - The SQL Service Account does not have **rights to the "Temporary Directory for storing backup files"**   - 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 ==== ==== Linux ====
Line 142: Line 150:
  
 === Restart OBM Services === === Restart OBM Services ===
 +
 +:!: If you need CDP, restart ''OBCDPService'' too.
  
 <file> <file>
Line 151: Line 161:
 </file> </file>
  
-:!: If you need CDP, restart ''OBCDPService'' too.+== 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>
  
 === Continuous Data Protection === === Continuous Data Protection ===
Line 234: Line 287:
 Suspend the account that is running.  Let job stop then re-enable. 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: The index files can be found in the following directory of the Local Copy destination:
  
 <file> <file>
-Local_Copy_Destination\server_name\username\files\backup_setID+<local_copy_destination>\<servername>\<username>\files\<backup_set_id>\
 </file> </file>
 +
 +The indexes will be rebuilt during the next backup.
  
 ===== Client Debug Mode ===== ===== Client Debug Mode =====
  
 https://forum.ahsay.com/viewtopic.php?f=117&t=10377&p=39615 https://forum.ahsay.com/viewtopic.php?f=117&t=10377&p=39615
computing/backup/ahsay_troubleshoot.1433172887.txt.gz · Last modified: 2015/06/01 09:34 by gcooper

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki