Discussion Locked

NT Backup locking & Crashing the server

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am using NT4 Service Pack5 and NT Backup.
I have a RAID 5 installed with 4x 16.9GB H/D. They are partitioned into 2 volumes the first being 2Gb for the operating system, the remaining volume for Data.
I have a problem that whenever a backup isrun over the operating system volume it gets to certain files and locks. No error messages are generated (V. Frustrating!) and the only way out of it is to reboot the server. If I delete the files in question the backup works. I dont know what caused this but the files are duplicated in other directories accross the network and deleting one instance of the file is not enough, All files of that name have to be deleted. This leads me to think that it is File Linking.
The files in question are:-
A2560di.sy_
ibmfedg.sy_
ibmfedg.sys
ds16gt.dll

8 replies

by biccarfa

Windows NT supports the backup of local files that are exclusively locked by the operating system, such as event logs and registry files;however, another type of skipped file that Windows NT Backup
encounters is that which is in use and locked by another process.

In this kind of event, Windows NT Backup displays a "Skip Open Files Wait Time" dialog box. An internal timer is then started and Windows NT Backup waits 30 seconds for the file to become available. During that time, Windows NT Backup continuously attempts to access the
locked file. If the file does not become available during the 30-second waiting period, Windows NT Backup skips the file, places its name in the backup log file (if the log is enabled), marks it as skipped inthe log, and continues to the next file. You have the option to choose the Cancel button in the dialog box and immediately move to the next file, logging the skipped file as previously described. If the file becomes available before the 30-second time-out
period, Windows NT Backup backs up that file and continues with the rest of the backup.

If the file has an attached alternate data stream that is locked,Windows NT waits 30 seconds for the stream to become available. If the stream does not become available in that time, Windows NT Backup makes an entry in the log (if enabled) indicating that the file was corrupt.

You can modify the following registry entries to adjust the skipped files options:
HKey_current_user\Software\Microsoft\Ntbackup\User Interface

Name: Skip open files
Type: REG_SZ
Default: 0
Definition:
0 = do not skip, wait
1 = skip files that are opened unreadable
2 = wait on open files for "Wait time"

Name: Wait time
Type: REG_SZ
Data: 30

by mcltech

The file names appear to be installation files for 'IBM' soft/hardware. So it would be unlikely that they are open. Have you done an 'Error Check' for that particular volume to ensure that all file tables, etc. are OK? You will have to reboot once again to do this when you have set it up. That would be my first step - especially since you are seeing the same file names randomly being placed about the drives.

Cal

by rick_b

This files are associated with IBM 100/10 PCI Ethernet Adapters in Windows NT.

Check Event Viewer for Error regarding NIC.
If card was removed, reove these entries from the registry.

If you have several of these cards in PC's and you are using a Backup Agent for the client, this will cause problems with the backup.

Check out http://www-1.ibm.com/support/
for more help

Hope this steers you in a helpful direction
Take Care
Rick

by cjw

Problem was with a Anti-Virus DAT file. soz for the delay, did'nt realise I had left it open.

This discussion is closed to new replies.