July 24, 2009 at 8:57 am
I really don't know how to solve this issue wich (of course) is happening randomly.
We run SQL Server 2000 on a dedicated Server with Win2003 Server Standard Ed. 64 bit (SP2).
The server is not exposed to the internet and it's in LAN with the Web Server.
The server is a Intel Pentium D CPU 1.8Ghz and has 4GB Ram (even if SQL Server uses 3 if I'm not wrong).
We run around 15 very small databases on the server, ranging from 12MB to a max of around 360MB (250MB when backup).
All the databases use the SIMPLE recovery model with thos options:
- Auto update statistics - Auto close - Auto shrink - Auto create statistics
We used to run daily complete backups (with verify integrity upon completion) for all DBs with some optimizations applied to them (now moved to once a week in different times from backups and from themselves):
- Reorganize data and index page (change free space per page percentage to 10%)
- Check database integrity (include index)
We don't backup transaction logs since we use the SIMPLE model.
In the last month we experienced several "random" server crashes wich required physical server reboots. Finally I managed to "isolate" the problem and it seems it's tied to the backup of a single 350 MB db.
No SQL logs are reported. No mainentance logs are written to disk, or well a 0Kb file is created. The DB backup stopped at around 65 MB and the server hangs.
I pointed the backup to an external USB device instead of doing it on the same disk of the DB but this didn't solve. We have 350 free GB on that HD and 200 Gb free on the system disk where backups where before (and server used to hang as well).
In the Server application logs i have:
at 24/07/09 - 0.00.46 - This instance of SQL Server has been using a process id of 1376 since 10/07/2009 9.55.03 (local) 10/07/2009 7.55.03 (UTC).
at 24/07/09 4.00.09 - 18264 : Database backed up: Database: terninretead, creation date(time): 2008/10/25(01:31:56), pages dumped: 979, first LSN: 73604:119:1, last LSN: 73604:121:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\Db\Backupameame_db_200907240400.BAK'}).
And then where the second backup should start right after this one nothing more...
The maintenance plan backup used the same options described above. If I run a manual backup at any time, it works perfectly (only backup no index or shrink) and it takes around 1 minute to execute.
Any hint?...... thanks in advance.
July 27, 2009 at 4:33 am
Any hint or test we can do to try solve the problem? Did anyone experience similar behaviour even with a relatively small db like ours?
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply