Activity overview
Latest activity by rrogersiii
Some follow-up information on this thread....
If we stop & start SQL Server, both of our SQL Backup jobs start working again ... but then the problem restarts after 2-3 days, jobs fail, and backups are not run. / comments
Some follow-up information on this thread....
If we stop & start SQL Server, both of our SQL Backup jobs start working again ... but then the problem restarts after 2-3 days, jobs fail, and backups...
- is this a default or named instance
....default - the SQL Server instance is not named
- is the SQL Backup Agent logging in to SQL Server using Windows authentication, or SQL Server authentication
....can't remember how we set it up - is there any where I can look?
- does the owner of the SQL Server Agent backup job have the SQL Server sysadmin fixed server role
.....the owner for the both SQL Server Agent jobs that SQL Backup created is the administrator account for the local Win2K server (not SQL Server) ... in turn, SQL Server lists BUILTIN/Administrators as a login member of the fixed sysadmin role, so... yes: I'd say that the owner of the jobs have the sysadmin fixed server role / comments
- is this a default or named instance
....default - the SQL Server instance is not named
- is the SQL Backup Agent logging in to SQL Server using Windows authentication, or SQL Server authenticatio...
- is server a cluster node
NO
- amount of memory on server, any memory switches used e.g. /3GB etc
4GB RAM - no spectial switches
- operating system version and service pack level (32-bit, 64-bit, Itanium?)
win2k server ("normal" version - not enterprise, etc.), 32-bit
- SQL Server version and service pack level (32-bit, 64-bit, Itanium?)
32bit
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
- MDAC version (see http://support.microsoft.com/?kbid=301202)
MDAC 2.8 SP1 on Windows XP SP2
- average size of trx log file
avg size of SQL Backup files (after compression): 0.5-1MB (every 15 minutes)
- scheduling agent (SQL Server Agent or others)
(just SQL Server Agent)
- aside from the backup script, are there any pre or post backup tasks performed?
delete backup files older than 5 days
- are the backups made to a local or remote drive
files are actualy written to SAN, which appears as local drive to OS / comments
- is server a cluster node
NO
- amount of memory on server, any memory switches used e.g. /3GB etc
4GB RAM - no spectial switches
- operating system version and service pack level (32-bit, 64-bit, ...
they're all listed as SQLDMO_### - for example:
- SQLDMO_489
- SQLDMO_490
- SQLDMO_491
etc...
Any ideas about why the jobs are failing, in the first place? That's our primary concern, at this point. / comments
they're all listed as SQLDMO_### - for example:
- SQLDMO_489
- SQLDMO_490
- SQLDMO_491
etc...
Any ideas about why the jobs are failing, in the first place? That's our primary concern, at this point.
backup jobs failing - *LOTS* of DB connections lying around
After two weeks of running SQL Backup 4.1, our backup jobs recently started failing.
Log backups run every 15 minutes - full backups of our production database run 1x/day - old backup files are del...