Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 Backup Troubles

Author  Topic 

John_Idol
Starting Member

39 Posts

Posted - 2007-04-18 : 08:34:54
Hi all,

the system I am working on was upgraded recently from SQL2000 to SQL2005, and it's generating strange issues after then.

The maintenace plan stopped working (the job was going to run forever if I didn't stop them), and I was able after some tests to understand the cause: It's impossible to backup two of the databases I have on the server.

If I try to di it manually I got this:
ERROR 3026
"Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized (...)"


You could think it's because someone is using the DBs at the same time, but I tried to Execute the Plan at night and the morning before it was still there running since 12 hours. If I cut from the maintenance plan these two databases the job runs just fine.

A strange thing, maybe a relevant clue, is that when I go to the tasks-->Backup and the SQL Server suggests a name for the new bak file instead of having a .BAK file (as for the others DBs I have there - something like 10) It tries to put the backup in a .TRN file (the sequence number seems to be correct - I have myDB_backup_200704181200.TRN instead of myDB_backup_200704181200.BAK); what makes me think this is a clue is that all this happens only for these two databases I cannot backup.

Ring any bells?

Thanks in advance,

Cheers,

Giovanni

John_Idol
Starting Member

39 Posts

Posted - 2007-04-18 : 09:34:26
Error is 3023,
Sorry!
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2007-04-18 : 09:39:20
ummm, get away from maint plans altogether?

http://weblogs.sqlteam.com/tarad/archive/2007/02/26/60120.aspx



Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx

Add yourself!
http://www.frappr.com/sqlteam



Go to Top of Page

John_Idol
Starting Member

39 Posts

Posted - 2007-04-18 : 09:49:01
Hi Brett,

thanks for link it's really interesting.
I am going to delete Maint Plans (which I didn't do) once I understand how to backup my DBs.

The Log Backup is fine, differential and full backups are throwing the error above.
One of the DBs says in properties Available space: 0.00 MB. It doesn't make sense to me (people's using it as usual).

Thanks again,

Giovanni
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2007-04-18 : 10:03:17
Do you have drive partitions? Are you backing up to a limited C: drive that may be out of space?



Brett

8-)

Hint: Want your questions answered fast? Follow the direction in this link
http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx

Add yourself!
http://www.frappr.com/sqlteam



Go to Top of Page

John_Idol
Starting Member

39 Posts

Posted - 2007-04-18 : 10:11:54
I have drive partitions C: 35 GB - 2 GB free, F: 110 GB - 27 GB free.
I am backing up to F.

Thanks,

G
Go to Top of Page

John_Idol
Starting Member

39 Posts

Posted - 2007-04-18 : 10:18:26
I just noticed this thing I wrote (below) is not a rilevant clue (actually it's nothing), as SQL Server takes the last file in the folder as suggestion.

####
A strange thing, maybe a relevant clue, is that when I go to the tasks-->Backup and the SQL Server suggests a name for the new bak file instead of having a .BAK file (as for the others DBs I have there - something like 10) It tries to put the backup in a .TRN file (the sequence number seems to be correct - I have myDB_backup_200704181200.TRN instead of myDB_backup_200704181200.BAK); what makes me think this is a clue is that all this happens only for these two databases I cannot backup.
####
Go to Top of Page

Abbas Gadhia
Starting Member

1 Post

Posted - 2009-07-03 : 10:22:19
open a query window on the db that REFUSES to get 'backed up' as it was in my case

type in

sp_who2 'active'

check the rows that indicate some form of connection to the db that is the villian here.
pick up the id of that row (in my case it was 119)

and fire this query

kill 119
Go to Top of Page
   

- Advertisement -