See also Other Ahsay pages in this wiki

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

Permit 203.186.85.237 to the Ahsay OBS server.

The main client configuration folder is found here:

notepad C:\Program Files\AhsayOBM\home.txt
#or
notepad C:\Program Files\AhsayACB\home.txt

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

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

1. Adjust host names in OBS web UI to match actual
2. Verify sufficient temporary disk space or change location
3. The SQL Service Account does not have rights to the “Temporary Directory for storing backup files”
4. 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

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

notepad C:\Users\Administrator\.obm\log\Scheduler\debug.log

or

notepad \\DC1\Redirected$\administrator\.obm\log\Scheduler\debug.log

and

notepad C:\Program Files\AhsayOBM\log\scheduler\info.log

If the info.log says another scheduler is running:

1. Stop the 'online backup scheduler service'
2. Delete the running file
   • C:\Program Files\AhsayOBM\ipc\scheduler\running
   • /usr/local/obm/ipc/Scheduler/running
3. Then re-start the service
4. 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

Check and or change the temporary backup location.

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

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

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

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

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

1. Stop OBSR
2. Move the user to the new User Home
3. Restart OBSR

service obsr stop

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

service obsr start

Moving to a different server is slightly different.

1. Stop OBSR on original server
2. Move the user to a temporary folder
3. Restart OBSR on original server
4. Stop OBSR on new server
5. Rsync (copy) the user folder to the new server
6. Start OBSR on new server
7. Delete temporary folder

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

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

If you need CDP, restart OBCDPService too.

net stop "OBScheduler"
net stop "OBAutoUpdate"
net stop "OBCDPService"
net start "OBScheduler"
net start "OBAutoUpdate"

If you see the error Another scheduler is running! in the info.log, try this script:

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"

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:

sc config "OBCDPService" start= disabled & net stop OBCDPService

/etc/init.d/obmaua stop
/etc/init.d/obmscheduler stop
/etc/init.d/obmscheduler start
/etc/init.d/obmaua start

See also 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.

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…

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

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

If you see something like:

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

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/

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

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

Use the Command Line Tool to add Pre and Post commands:

net use z: \\DOMAIN\Server /user:DOMAIN\backupadminuser backupadminpass

net use z: /d /y

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.

The index files can be found in the following directory of the server:

/mountpoint/<username>/files/<backup_set_id>/

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.

The index files can be found in the following directory of the Local Copy destination:

<local_copy_destination>\<servername>\<username>\files\<backup_set_id>\

The indexes will be rebuilt during the next backup.

https://forum.ahsay.com/viewtopic.php?f=117&t=10377&p=39615