Vault 4.1 database backup failure

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
vmgbritt
Posts: 6
Joined: Tue Jan 06, 2015 2:05 pm

Vault 4.1 database backup failure

Post by vmgbritt » Wed Jul 08, 2015 1:00 pm

Hi,

I'm attempting to backup my vault databases before I upgrade versions.

I'm running Vault 4.1.4.18402. The server is on a Win Server 2003 box.

The client is connecting properly to the databases and allowing me to checkin/checkout files as appropriate.

When I run the backup from the admin web client I get a failure. Looking at the logs it cannot open the sgvault database. Any suggestions on how to recover. Log is attached.

I do have a successful SQL backup of the database from January which was untouched until this week when I made a series of changes to source [which is still on my client device].

Appreciate any guidance.

Britt
Attachments
VaultLog.txt
Log file
(28.69 KiB) Downloaded 308 times

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Re: Vault 4.1 database backup failure

Post by mskrobul » Wed Jul 08, 2015 2:10 pm

The Vault Admin backup UI is basically just a wrapper for SQL server backup. The Vault Admin UI is there for convenience, but since the long backup process is done via a web request it can have issues for large databases etc. The Admin UI backup output is exactly the same as a normal SQL server backup.

So if the Admin Tool isn't backup isn't working, you can just backup your sgvault and sgmaster databases using SQL Server.
Mary Jo Skrobul
SourceGear

vmgbritt
Posts: 6
Joined: Tue Jan 06, 2015 2:05 pm

Re: Vault 4.1 database backup failure

Post by vmgbritt » Wed Jul 08, 2015 2:18 pm

Thanks for the quick response.

I've tried a direct sql backup of those databases but get a similar error so it is on the SQL side.. any ideas on how to recover?

C:\Documents and Settings\Administrator\Desktop>"C:\Program Files (x86)\Micro
t SQL Server\90\Tools\Binn\sqlcmd.exe" -Q "exec export_backups"
Processed 224 pages for database 'sgmaster', file 'sgmaster' on file 8.
Processed 2 pages for database 'sgmaster', file 'sgmaster_log' on file 8.
BACKUP DATABASE successfully processed 226 pages in 0.152 seconds (12.146 MB/
).
Device dropped.
Msg 3271, Level 16, State 1, Server DT3, Procedure export_backups, Line 22
A nonrecoverable I/O error occurred on file "F:\sqlserver\Data\sgvault.mdf:" 1(I
ncorrect function.).
Msg 3013, Level 16, State 1, Server DT3, Procedure export_backups, Line 22
BACKUP DATABASE is terminating abnormally.
Device dropped.
Processed 600 pages for database 'FYDDistRun', file 'FYDDistRun' on file 8.
Processed 1 pages for database 'FYDDistRun', file 'FYDDistRun_log' on file 8.
BACKUP DATABASE successfully processed 601 pages in 0.345 seconds (14.270 MB/
).
Device dropped.
Processed 166968 pages for database 'VPPTesting', file 'VPPTesting' on file 8
Processed 1 pages for database 'VPPTesting', file 'VPPTesting_log' on file 8.
BACKUP DATABASE successfully processed 166969 pages in 67.359 seconds (20.306
/sec).
Device dropped.

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Re: Vault 4.1 database backup failure

Post by mskrobul » Wed Jul 08, 2015 3:16 pm

Do you have enough disk space to perform the backup?

The sgvault database can be rather large.
Mary Jo Skrobul
SourceGear

vmgbritt
Posts: 6
Joined: Tue Jan 06, 2015 2:05 pm

Re: Vault 4.1 database backup failure

Post by vmgbritt » Thu Jul 09, 2015 7:38 am

There is 85 GB free and the sgvault DB should be 1GB or less so don't think diskspace is the issue.

Britt

jclausius
Posts: 3621
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Re: Vault 4.1 database backup failure

Post by jclausius » Thu Jul 09, 2015 8:05 am

I cannot seem to find 'export_backups' job. This might be a job created on your SQL Server instance. Can you look at it for line 22?

Also, a search on 'A nonrecoverable I/O error occurred on file' may provide you with more clues.

Finally, one other thing you could try are the following commands:

BACKUP DATABASE sgmaster TO DISK='DRIVE_LETTER:\A\Valid\Backup\Path\sgmaster.bak' WITH DESCRIPTION = 'sgmaster manual backup', INIT
GO

BACKUP DATABASE sgvault DISK='DRIVE_LETTER:\A\Valid\Backup\Path\sgvault.bak' WITH DESCRIPTION = 'sgvault manual backup', INIT
GO
Jeff Clausius
SourceGear

vmgbritt
Posts: 6
Joined: Tue Jan 06, 2015 2:05 pm

Re: Vault 4.1 database backup failure

Post by vmgbritt » Thu Jul 09, 2015 9:20 am

Thanks for the suggestions.

More detailed log:
2015-07-09 08:23:49.35 Server Server resumed execution after being idle 1359 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2015-07-09 08:23:49.73 Backup Database backed up. Database: sgmaster, creation date(time): 2008/03/05(13:02:10), pages dumped: 235, first LSN: 35:473:37, last LSN: 35:489:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'diskdump'}). This is an informational message only. No user action is required.
2015-07-09 08:24:14.54 Backup Error: 18210, Severity: 16, State: 1.
2015-07-09 08:24:14.54 Backup BackupIoRequest::WaitForIoCompletion: read failure on backup device 'F:\sqlserver\Data\sgvault.mdf'. Operating system error 1(Incorrect function.).
2015-07-09 08:24:14.54 Backup Error: 3041, Severity: 16, State: 1.
2015-07-09 08:24:14.54 Backup BACKUP failed to complete the command BACKUP DATABASE sgvault. Check the backup application log for detailed messages.
2015-07-09 08:24:14.54 Backup Error: 18210, Severity: 16, State: 1.
2015-07-09 08:24:14.54 Backup BackupIoRequest::WaitForIoCompletion: read failure on backup device 'F:\sqlserver\Data\sgvault.mdf'. Operating system error 1(Incorrect function.).
2015-07-09 08:24:14.59 Backup Error: 18210, Severity: 16, State: 1.
2015-07-09 08:24:14.59 Backup BackupIoRequest::WaitForIoCompletion: read failure on backup device 'F:\sqlserver\Data\sgvault.mdf'. Operating system error 1(Incorrect function.).
2015-07-09 08:24:14.95 Backup Database backed up. Database: FYDDistRun, creation date(time): 2009/02/17(14:14:14), pages dumped: 620, first LSN: 22739:473:37, last LSN: 22739:489:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'diskdump'}). This is an informational message only. No user action is required.
2015-07-09 08:24:14.98 spid51 Starting up database 'VPPTesting'.
2015-07-09 08:25:24.71 Backup Database backed up. Database: VPPTesting, creation date(time): 2009/03/06(16:54:49), pages dumped: 167007, first LSN: 2126:11333:37, last LSN: 2126:11349:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'diskdump'}). This is an informational message only. No user action is required.
2015


I then tried your manual backup job as follows:

1> BACKUP DATABASE sgmaster TO DISK='F:\VaultBackups\sgmaster.back' WITH DESCRIPTION = 'sgmaster manual backup', INIT
2> GO
Processed 224 pages for database 'sgmaster', file 'sgmaster' on file 1.
Processed 1 pages for database 'sgmaster', file 'sgmaster_log' on file 1.
BACKUP DATABASE successfully processed 225 pages in 0.112 seconds (16.457 MB/sec).
1> BACKUP DATABASE sgvault TO DISK='F:\VaultBackups\sgvault.back' WITH DESCRIPTION = 'sgvault manual backup', INIT
2> GO
Msg 3271, Level 16, State 1, Server DT3, Line 1
A nonrecoverable I/O error occurred on file "F:\sqlserver\Data\sgvault.mdf:" 1(Incorrect function.).
Msg 3013, Level 16, State 1, Server DT3, Line 1
BACKUP DATABASE is terminating abnormally.
1>

How is it possible for vault clients to appear to be functioning properly if their is a serious error with the sgvault database?


If this database is nonrecoverable what should I do?

I have all but sgvault backups working. I have an sgvault backup from January and fortunately the only source changes made were in the last 2 weeks and are on my local machine. Do I restore from that backup and then recheck in my source? What is the process to restore from that backup?

Britt

jclausius
Posts: 3621
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Re: Vault 4.1 database backup failure

Post by jclausius » Thu Jul 09, 2015 9:58 am

First things first.

You'll want to take a look at what's going on with the file. Run a consistency check on the database.

See help on the DBCC CHECKDB command for help on determining what is going on - https://msdn.microsoft.com/en-us/library/ms176064.aspx

If you're using an old version of SQL Server, you'll need to run a couple of different DBCC commands.

I think DBCC CHECKDB, DBCC CHECKALLOC and DBCC NEWALLOC will help. You can see the different commands on this link - https://technet.microsoft.com/en-us/lib ... 80%29.aspx for SQL Server 2000
Jeff Clausius
SourceGear

Post Reply