====== Troubleshooting Ahsay Backup ======

See also **[[https://www.sonoracomm.com/wiki/doku.php?do=search&id=ahsay|Other Ahsay pages in this wiki]]**

http://thinkbackup.net/dynamic_content.php?id=76

===== License =====

**Permit 203.186.85.237** to the Ahsay OBS server.

===== Configuration Folder =====

The main client configuration folder is found here:

<file>
notepad C:\Program Files\AhsayOBM\home.txt
#or
notepad C:\Program Files\AhsayACB\home.txt
</file>

===== Roaming Profiles and Multiple Machines =====

Only the OBM backup client can support multiple machines on the same backup account.

Use separate Windows accounts (separate profile directories) on each machine to run OBM.

We generally use:

  * The AD Domain Administrator account on the primary file server
  * The local Administrator account on each subsequent machine in the domain

===== Missed Backups =====

https://www.ahsay.com/blog/2017/08/22/top-8-reasons-for-missed-backups-when-using-ahsay-backup-software

==== Common Causes of Missed Backups ====

  - Adjust **host names** in OBS web UI to match actual
  - 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 ====

<file>
cat /usr/local/obm/home.txt
cat /root/.obm/log/Scheduler/debug.log
cat /usr/local/obm/log/Scheduler/info.log
ll /usr/local/obm/ipc/Scheduler/running
ps ax|grep ob
</file>

==== Windows ====

<file>
notepad C:\Users\Administrator\.obm\log\Scheduler\debug.log
</file> 

or

<file>
notepad \\DC1\Redirected$\administrator\.obm\log\Scheduler\debug.log
</file>

and

<file>
notepad C:\Program Files\AhsayOBM\log\scheduler\info.log
</file>

==== Both ====

If the ''info.log'' says ''another scheduler is running'':

  - Stop the 'online backup scheduler service'
  - Delete the ''running'' file
    * ''C:\Program Files\AhsayOBM\ipc\scheduler\running''
    * ''/usr/local/obm/ipc/Scheduler/running''
  - Then re-start the service
  - Check the log files again to see if they are current

The other problem could be that there may be multiple entries in your ''C:\Program Files\AhsayOBM\home.txt'' file.  If it has multiple entries then it has multiple profiles and will cause problems. Correct the ''home.txt'' file and mark it as read only and follow the above steps again

===== Cannot Open Backup Device =====

Check and or change the temporary backup location.

===== No *.edb Found for Database =====

http://forum.ahsay.com/viewtopic.php?t=6043

  * Disable any other backup software
  * Run a full Exchange backup

===== Missing User =====

If an Ahsay backup user disappears from the management console "All Users", check:

  * Log into Ahsay server
  * cd /mnt
  * check obs_homes_1, 2 and 3
  * The user data folder exist on the server
  * If it does, check the ''db\Profile.xml'' file
  * If you suspect the file is corrupt, perhaps you can rename a ''.xml.1'' file to ''.xml''

===== Validate User Data =====

https://help.ahsay.com/openArticle.aspx?aid=2632&p=16 

===== Disk Space =====

==== Move a Backup Account to a new User Home ====

https://help.ahsay.com/openArticle.aspx?aid=2709&p=16 

  - Stop OBSR
  - Move the user to the new User Home
  - Restart OBSR

<file>
service obsr stop

mv /opt/obs/user/[username] /mnt/obs_homes_1/

service obsr start
</file>

Moving to a different server is slightly different.

  - Stop OBSR on original server
  - Move the user to a temporary folder
  - Restart OBSR on original server
  - Stop OBSR on new server
  - Rsync (copy) the user folder to the new server
  - Start OBSR on new server
  - Delete temporary folder

==== Replication of a Moved User Account ====

https://help.ahsay.com/openArticle.aspx?aid=2311&p=16 

===== Processes =====

==== Windows ====

http://forum.ahsay.com/viewtopic.php?t=4410

=== Restart OBM Services ===

:!: If you need CDP, restart ''OBCDPService'' too.

<file>
net stop "OBScheduler"
net stop "OBAutoUpdate"
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>

=== Continuous Data Protection ===

:!: This process uses a lot of RAM and runs whether you use CDP or not.

http://forum.ahsay.com/viewtopic.php?p=22911

You may see in Task Manager a process CDPService.exe which may use a lot of memory and CPU.  For clients not using CDP, disable that service like this:

<file>
sc config "OBCDPService" start= disabled & net stop OBCDPService
</file>

==== Linux ====

<file>
/etc/init.d/obmaua stop
/etc/init.d/obmscheduler stop
/etc/init.d/obmscheduler start
/etc/init.d/obmaua start
</file>

===== Databases =====

==== Microsoft SQL ====

See also **[[computing:windows:mssql_backup|Microsoft SQL Server Backup]]**

http://msdn.microsoft.com/en-us/library/ms190190.aspx

Microsoft System databases such as 'master', 'msdb' and 'model' must remain set to the SIMPLE recovery model.  Therefore, you can only do Full backups on these databases reliably (no Transaction Log backups).

For other databases, particularly larger databases, you can also use Transaction Log backups.  Set the recovery mode of each database to FULL (not SIMPLE) with the OBM client.

:!: To change the database recovery mode from within Ahsay OBM, **right-click on the database name in Backup Source** to change.

==== MySQL ====

http://www.ahsay.com/jsp/en/home/index.jsp?kw=&pageContentKey=ahsay_products_mysql_benefits

Exclude ''MySQL/information_schema'' if you get an error backing it up.  New versions won't...

===== Outlook =====

{{ :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. 

https://help.ahsay.com/openArticle.aspx?aid=2556&p=16

==== CloseOutlook.cmd ====

<file>
TASKLIST | FIND "OUTLOOK.EXE"
if errorlevel 1 goto end
if errorlevel 0 taskkill /im outlook.exe /F
:end
</file>

===== Exchange =====

If you see something like:

<file>
The writer vetoed the shadow copy creation process during the backup preparation state.
(VSS_WS_FAILED_AT_PREPARE_BACKUP)
</file>

See: https://help.ahsay.com/openArticle.aspx?aid=2863

http://www.altaro.com/blog/sbs-2011-backups-failing-vss-error-0x800423f3-event-id-8230-spfarm-spsearch/

==== Disable Circular Logging ====

http://msdn.microsoft.com/en-us/library/aa579094%28v=exchg.140%29.aspx

http://technet.microsoft.com/en-us/library/bb331968%28EXCHG.80%29.aspx

===== Stop Running Backup From Server =====

Suspend the account that is running.  Let job stop then re-enable.

===== Local Copy =====

==== 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>\<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