How can we help you today? How can we help you today?
APT-1
Activity overview Badges (0) Posts (1) Comments (2)

Activity overview

Latest activity by APT-1

Firstly, I must apologise for forgetting my signature block. Running the Select statement in QA returned the correct result. After running the DBCC FREEPROCCACHE the backup is now working from the automated job and manually via SQL Backup 6. I will see what happens when the job runs early tomorrow morning. Thank you for your help and quick reply. Scott Koorey APT Business Solutions Canberra ACT, Australia / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Error 913 on SQL Backup of database(s) with new db's
Firstly, I must apologise for forgetting my signature block. Running the Select statement in QA returned the correct result. After running the DBCC FREEPROCCACHE the backup is now working from the ...
0 votes
I am now having the same problem. Last week I had to drop a database and then restore it from an earlier backup. This caused the DB ID to change. I have checked how the size is calculated with profiler: SELECT SUM(size) size FROM [Tiger]..sysfiles On this Server, I am using SQL Backup 6.4 and SQL Server 2000. Is there a solution to this problem? Details below: ERRORS AND WARNINGS 7/02/2011 10:11:06 AM: Backing up Tiger (full database) to: 7/02/2011 10:11:06 AM: [image] \FleetPlanner Backups\RedGate\Tiger 20110207_01.sqb 7/02/2011 10:11:06 AM: [image] \FleetPlanner Backups\RedGate\Tiger 20110207_02.sqb 7/02/2011 10:11:06 AM: [image] \FleetPlanner Backups\RedGate\Tiger 20110207_03.sqb 7/02/2011 10:11:09 AM: BACKUP DATABASE [Tiger] TO VIRTUAL_DEVICE = 'SQLBACKUP_2D00985B-9743-4EBC-BF47-E19CCF1A6E7E', VIRTUAL_DEVICE = 'SQLBACKUP_2D00985B-9743-4EBC-BF47-E19CCF1A6E7E01', VIRTUAL_DEVICE = 'SQLBACKUP_2D00985B-9743-4EBC-BF47-E19CCF1A6E7E02' WITH BUFFERCOUNT = 18, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'Database (Tiger), 7/02/2011 10:11:06 AM', DESCRIPTION = N'Backup on 7/02/2011 10:11:06 AM Server: FYBRSN14 Database: Tiger', FORMAT 7/02/2011 10:11:14 AM: Warning 167: Failed to get database size from server. 7/02/2011 10:11:14 AM: SQL error 913: Could not find database ID 52. Database may not be activated yet or may be in transition. 7/02/2011 10:11:14 AM: Backup data size : 114.125 MB 7/02/2011 10:11:14 AM: Compressed data size: 23.407 MB 7/02/2011 10:11:14 AM: Compression rate : 79.49% 7/02/2011 10:11:14 AM: Processed 13472 pages for database 'Tiger', file 'Tiger' on file 1. 7/02/2011 10:11:14 AM: Processed 1 pages for database 'Tiger', file 'Tiger_log' on file 1. 7/02/2011 10:11:14 AM: BACKUP DATABASE successfully processed 13473 pages in 4.255 seconds (25.937 MB/sec). / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Error 913 on SQL Backup of database(s) with new db's
I am now having the same problem. Last week I had to drop a database and then restore it from an earlier backup. This caused the DB ID to change. I have checked how the size is calculated with pr...
0 votes
Delay in Restoring from SQL Backup
  1. Community
  2. SQL Backup Previous Versions
We’ve recently installed SQL Backup Pro 4.6.0.815 onto a pair of identical 32-bit Windows 2003 servers, each with 32GB RAM. Each server is running SQL Server 2005 Enterprise Edition (SP2) with th...
1 follower 1 comment 0 votes
Total activity
4
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
1