Restore job may be executed on an unexpected server when using IP addresses


A restore job may be executed on an unexpected server when IP addresses are used for multiple servers instead of computer names or FQDN.

This issue is observed with restore jobs of SQL databases but not limited to.

Consider the following scenario:

1) Get a backup of SQL databases from IP address

2) Get a backup of SQL databases from IP address

3) Both SQL server has the same database name "testdb".

3) Create a restore job of "testdb" for
   This job is unexpectedly executed on the server IP address which has the latest backup set regardless of IP address.


To work around this issue, perform either A) or B)

A) Use computer name or FQDN instead of IP address.

B) Choose a backup set specifically as below.

1) Open the job history of the backup job which is to be restored.

2) Write down the Start Time of the backup set. Figure 1

Figure 1


3) Create a restore job

4) Choose To a backup set time that I select or To an individual backup set that I select from all available backup sets this database. Figure 2

Figure 2


5) Select the backup set which has the start time of step #2. Figure 3

Figure 3 


 A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.

Backup Exec 2012 Rev 1798 Service Pack 3 (TECH205351).

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)