Learn More Download Free Trial Pricing & Buy

Posts Tagged ‘backup’


Optimize backup strategy on a Terminal Services farm

Last week a client (a multinational corporation) contacted us with the following request:

[...]
I would like to determine optimal time for backing-up our databases.

The problem the client was facing was that his users were connecting from different continents and different time zones. So the usual “best practice” of backing-up databases during night could not be applied in this case.

The solution for this problem was really simple. Terminal Services Log was already installed, so we analyzed the gathered data and here are the results. The first step was to analyze weekl activities and to determine weekdays when the server was least used.

As shown in the picture above, the server is least used on Tuesdays and Wednesdays (due to the nature of  business this company does on weekends). Daily activity report revealed that the optimal time for backup is 1AM – 6AM (GMT).

Our reports clearly show that the best time for performing backups, so in case this customer needed to plan a day or two for weekly backups he should probably choose Tuesday or Wednesday night when this farm is least used.


How to use TSL to track logged users when backup job is starting?

Our client had a problem with one of the servers in their farm. The backup job could not be run if someone was trying to access certain files on the computer. If a file was opened the backup would fail.

Although most modern backup programs are able to backup an open file, our customer  backups is a very old database format, and even a modern backup program cannot handle it.

This is the error we were receiving: Backup could not be performed due to inability to lock the database.

Performing Backup jobs on a Terminal Sever can be complicated. An automated script is going to log-off all users at midnight. Users cannot login 12:00AM – 3:00AM. to prevent them from accessing the server and opening a databases that is being backuped.To ensure everything works smoothly we used our product Terminal Services Log to analyze user activities on the server and checked if there were any no active sessions (if a user was not included in the log off script).

By using Users and Sessions report we were able to locate what the users that were still active in backup time. For these ‘problematic users’ we change idle logoff timeout and included them in the midnight auto log off script.

After correct configuration backup is running normally :) .