Always the Worker Thread

I received the following msg resulting from a backup: (partial) "increase th
e
maximum worker threads for the SQL Server SQLSRVR\SSDDWP_SQL2. Or decrease
the maximum number of databases to backup concurrently". There is a anothe
r
full backup at a different time of day on this server that succeeds. This
instance is on a cluster server. I do not receive this msg throughout the
day. I do have 400 or so connections throughout the day. My threads are se
t
to the default of 255. I have 4 CPUs in each server. How can I accommodat
e
this backup? Would the idea be to run the dbcc sqlperf(UMSSTATS) at the sam
e
time the backup is occurring?One other question on the dbcc sqlperf(UMSSTATS). So my "work queued" at 0
or 1 and idle workers should be close to the same number as num workers?
thanks
"RomM" wrote:

> I received the following msg resulting from a backup: (partial) "increase
the
> maximum worker threads for the SQL Server SQLSRVR\SSDDWP_SQL2. Or decrease
> the maximum number of databases to backup concurrently". There is a anot
her
> full backup at a different time of day on this server that succeeds. This
> instance is on a cluster server. I do not receive this msg throughout the
> day. I do have 400 or so connections throughout the day. My threads are
set
> to the default of 255. I have 4 CPUs in each server. How can I accommod
ate
> this backup? Would the idea be to run the dbcc sqlperf(UMSSTATS) at the s
ame
> time the backup is occurring?
>