Jump to content
Sign in to follow this  
dlebaron

OPEN FILE PROBLEM!!!!!!!

Recommended Posts

I am running a backup of a computer that services goldmine for 6 users. I keep getting this error message when running backups. I checked to make sure open file was enable, it is. Any ideas would be great.

 

File "C:\MSSQL7\Data\ASAT.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\ASAT_log.LDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\BETA.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\BETA_log.LDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\LocalTrans.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\LocalTrans_log.LDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\master.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\mastlog.ldf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\model.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\modellog.ldf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\Pershing.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\Pershing_log.LDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\Support.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\Support_log.LDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\TEMPDB.MDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\TEMPLOG.LDF": can't read, error -1020 (sharing violation)

 

Share this post


Link to post
Share on other sites

Ummm.... I think that Open File Backup doesn't work on SQL.... I think that Dantz makes you buy the SQL agent/add-on too.

 

Of course, Robin or Amy will jump in here in a minute and straighten this all out.

Share this post


Link to post
Share on other sites

Open File should work on a server that does not contain the SQL Agent (although the SQL Agent is ideal for MS SQL servers, and the most reliable approach)

 

If you watch the backup of the server, Retrospect should make an attempt to "wait for open file backup" at the beginning of copy. Do you see this happening?

 

What other text appears in the log? Can you provide the entire log entry for that client?

Share this post


Link to post
Share on other sites

This is the full log

 

 

5/20/2003 12:00:10 PM: Connected to LPL

* Resolved container LPL to 1 volumes:

Hp_pavilion (C:) on LPL

 

- 5/20/2003 12:00:00 PM: Copying Hp_pavilion (C:) on LPL

File "C:\MSSQL7\Data\ASAT.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\ASAT_log.LDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\BETA.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\BETA_log.LDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\LocalTrans.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\LocalTrans_log.LDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\master.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\mastlog.ldf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\model.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\modellog.ldf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\Pershing.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\Pershing_log.LDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\Support.mdf": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\Support_log.LDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\TEMPDB.MDF": can't read, error -1020 (sharing violation)

File "C:\MSSQL7\Data\TEMPLOG.LDF": can't read, error -1020 (sharing violation)

File "C:\QUICKENW\Qdata2.QDF": can't read, error -1020 (sharing violation)

File "C:\QUICKENW\QW.RMD": can't read, error -1020 (sharing violation)

MapError: unknown Windows error -2,147,024,809

VssWEnumWriterMetadata: UDisableWriterClasses failed. Aborting writer exclude., winerr -2147024809, error -1001

5/20/2003 12:10:45 PM: Snapshot stored, 11.8 MB

5/20/2003 12:10:51 PM: Comparing Hp_pavilion (C:) on LPL

5/20/2003 12:11:07 PM: 18 execution errors

Completed: 162 files, 8,362 KB, with 56% compression

Performance: 5.5 MB/minute (2.9 copy, 37.6 compare)

Duration: 00:11:06 (00:08:07 idle/loading/preparing)

 

 

Share this post


Link to post
Share on other sites

If you watch the backup of the server, Retrospect should make an attempt to "wait for open file backup" at the beginning of copy. Do you see this happening?

 

Share this post


Link to post
Share on other sites

If you check the services control panel, is the Retrospect Launcher Service still running?

Share this post


Link to post
Share on other sites

Check the computer to confirm that the roff.sys file has been installed.

 

 

 

C:\WINNT\system32\drivers\roff.sys

 

 

 

What operating system is the client and server running?

Share this post


Link to post
Share on other sites

1 client is running Windows 98 and the other XP home. I assume the Open file option is not supported by 6.5 client when using Win 98????

Share this post


Link to post
Share on other sites

From the User's Guide:

 

 

 

Requirements for Open File Backup

 

Retrospect Small Business Server, Single-

 

Server, or Multi-Server

 

 

 

License code for Open File Backup. Open

 

File Backup must be purchased separately.

 

Click Configure>Licenses to view your

 

current licenses or purchase new ones.

 

 

 

The volume being backed up must be

 

running Windows NT 4.0 Server or

 

Workstation with Service Pack 6; Windows

 

2000 Professional, Server, or Advanced

 

Server with Service Pack 2; or Windows

 

XP. To back up open files on a Windows XP

 

computer, it must have an NTFS volume.

 

 

 

If the volume being backed up is a client, it

 

must be running Retrospect Client 6.0 or

 

greater.

 

 

 

 

 

Is the XP running under NTFS?

Share this post


Link to post
Share on other sites

Requirements for Open File Backup

Retrospect Small Business Server, Single-

Server, or Multi-Server

 

License code for Open File Backup. Open

File Backup must be purchased separately.

Click Configure>Licenses to view your

current licenses or purchase new ones.

 

I purchased OFB separately at 6.0 level and upgraded to 6.5. I received a separate 6.5 level OFB license code from Dantz Customer Service when upgrading. My Retrospect Multi-Server *does* show that I am licensed for OFB.

 

The volume being backed up must be

running Windows NT 4.0 Server or

Workstation with Service Pack 6; Windows

2000 Professional, Server, or Advanced

Server with Service Pack 2; or Windows

XP.

 

The volumes being backed-up are in a system running Windows 2000 Advanced Server with Service Pack 3 applied.

 

By the way, every server in my office is running Windows 2000 Advanced Server with Service Pack 3 applied. Every workstation in my office is running Windows 2000 Professional with Service Pack 3 applied.

 

To back up open files on a Windows XP

computer, it must have an NTFS volume.

 

Not applicable. However, every drive in every server and workstation in the office is running NTFS.

 

If the volume being backed up is a client, it

must be running Retrospect Client 6.0 or

greater.

 

So far, we havent' tried to run OFB on any client. Our OFB problem is limited to one server backing up its own local (not mapped) drives to its own local (not mapped) drive.

 

Is the XP running under NTFS?

 

We're not running XP on anything anywhere.

Share this post


Link to post
Share on other sites

Curiously, I purchased OFB in the same manner as you--bought both products, and then received upgrade codes for both. I didn't attempt to use OFB with version 6.0 of the software, so I don't know if it was functional or not. I'm also receiving my error when backing up local drives to a local tape drive, though my OS is plain W2K server, not Advanced.

 

I'm receiving a different OFB error (-1019), though, so I doubt the license codes used have any affect.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×