Backup failed...Catalogs\SM2F057.SM...File in use.

[TotalEclypse]

Using Backup Exec 9.0 4454 on Windows 2000 servers we regularly get failed backups due to a SMABC123.SM file being 'in use'. Most files that are 'in use' are skipped, however, when this file is encounted the backup always fails. This is happening on various different remote backup servers, seemingly randomly, with increasing frequency.

Does anyone know how to fix this problem (as it is virtually a daily occurance on one or more of our 95 servers?) Any suggestions greatly recieved.

Regards,

Christopher

ICT Secondline Support

[priya_khire]

Hello,

What does this file correspond to? Since when did the problem begin? When the backups fail, what is the exact error you receive? Are you using the Advanced open file option during backups?

It will be a good idea to upgrade to backup exec 9.1 which is a free upgrade from 9.0. It addresses many issues and enhancements from an earlier versions and Build of Backup Exec v9.0. Refer the following technotes:

Title: VERITAS Backup Exec (tm) 9.1 for Windows Servers revision 4691.1 (Single .ZIP download)
http://seer.support.veritas.com/docs/264658.htm


Title: VERITAS Backup Exec (tm) 9.1 for Windows Servers General Information
http://seer.support.veritas.com/docs/262414.htm


Note: 1. BEWS 9.1 is a free downloadable upgrade inclusive of previously installed agents and options from Backup Exec 9.0 for Windows Servers agents and options.

2. Update all agents/options on all remote systems.

Do also install SP 3 for 9.1 after this from the following link:

VERITAS Backup Exec (tm) 9.1 for Windows Servers revision 4691 - Service Pack 3
http://support.veritas.com/docs/278302

Hope tihs helps. If the issue persists, revert with details to the above questions.


Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.

Regards.

[TotalEclypse]

Hi Priya, thanks for your advice. However, we need to consider carfully before taking the upgrade route to 9.1 as we have in the region of 95 backup servers.

You asked what error we get:
Within Backup Exec 9.0
The backup fails with
"Job ended: 13 September 2005 at 19:17:45
Completed status: Failed
Final error code: 00002b18 HEX
Final error description: 0x 2b18 (11032)

Final error category: Other Errors"

Also in Event Viewer on the W2k server:
Event ID: 57860
"An error occurred while attempting to log in to the following server: "DSKIN01\BKUPEXEC".
SQL error number: "4818".
SQL error message: "Login failed for user 'DS\$Backupexec'."

followed by:
Event ID: 34113
"Backup Exec Alert: Job Failed
(Server: "DSKIN01") (Job: "Daily Backup") Daily Backup -- The job failed."

Note the backups work sucessfully as normal, unless the following appears in the job log of skipped files:
"Unable to open the item C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\SM92F4A2.SM - skipped."

As far as I can tell this is a tmp file, so I guess for the short term I can just setup the backup job to exclude *.SM files within the above directory?

Any suggestions greatly appreciated.

Regards,

Christopher

ICT Secondline Support

[Renuka_-]

Hello,
C:\Program Files\VERITAS\Backup Exec\NT\Catalogs\SM92F4A2.SM - skipped."
This is a catalog files of backup exec itself, you may skip the backup exec database files rom the backup since these are backed up during the database maintenance schedule of backup exec.
http://support.veritas.com/docs/260639

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.

[TotalEclypse]

Hi, thanks for that. I checked that the Backup Exec maintenance task was not due to run at the same time as the backup. That was OK.

I've setup exclusions on every server to exclude C:\...\Catalogs\*.SM files. However, the backups still appear to be periodically failing, so maybe it isn't specifically related to the *.SM temp files. Short of upgrading all 94 remote backup servers to 9.1, I'm running out of ideas.

P'haps someone might know what Event Viewer; Event ID 57860 & Event ID 34113 means? (I tried the 'more info' link but it didn't work).

Regards,

ChristopherMessage was edited by:
Total Eclypse

[priya_khire]

Hello Christopher,

You had mentioned earlier that the backup fails on several servers, and not just one. Since when did the problem begin occuring? What are you backing up in this job?

Regarding error 57860, check if the following technotes apply to your environment. If yes, you can follow the steps in the technotes below and check if that helps.

Title: In the event viewer, Event ID: 57860 "An error occurred while attempting to log in to the following server... SQL error number: "0011"" is seen when backing up a server with SQL installed.
http://support.veritas.com/docs/264616

Title: Event ID 57860: "An error occurred while attempting to log into the following server..." is reported in the Event Viewer while a backup or restore job containing SQL Server data is run.
http://support.veritas.com/docs/251942

In any case, as i had already said, 9.1 is a free upgrade and resolves several issues present in the earlier versions. So you can try that too.

Get back to the forums in case of any more queries on this.

Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.

Regards.