backing up replicated db's

I have all the publishers on a emc san with 2gb fiber cards. My backups
are all done across the san as well, so speed is very fast. However, I
am running into contention backing up the databases that are publishing.
Those db's are taking 8hr's + to backup when the non published db's are
taking less then 5min.
What is the best/fastest way to backup db's that are publishing.
Thanks,
-comb
Could it be that the log reader agent is not running for the published
databases? If the logreader agent is not running, then the replicated
transactions will not be cleared from the transaction log, and could result
in huge transaction log files. Are the backup and transaction log files
unusually big?
You can verify if the replicated transactions are being picked up, using
DBCC OPENTRAN. See SQL Server Books Online for more information.
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"combfilter" <asdf@.adsf.com> wrote in message
news:MPG.1d5064e3790e4ad69896ae@.news.newsreader.co m...
>I have all the publishers on a emc san with 2gb fiber cards. My backups
> are all done across the san as well, so speed is very fast. However, I
> am running into contention backing up the databases that are publishing.
> Those db's are taking 8hr's + to backup when the non published db's are
> taking less then 5min.
> What is the best/fastest way to backup db's that are publishing.
> Thanks,
> -comb
|||In article <uAMOURjkFHA.3968@.tk2msftngp13.phx.gbl>,
answer_me@.hotmail.com says...
> Could it be that the log reader agent is not running for the published
> databases? If the logreader agent is not running, then the replicated
> transactions will not be cleared from the transaction log, and could result
> in huge transaction log files. Are the backup and transaction log files
> unusually big?
> You can verify if the replicated transactions are being picked up, using
> DBCC OPENTRAN. See SQL Server Books Online for more information.
>
they are semi big, but nothing really out of control. I will see the
log reader sometimes have the error of "cannot run sp_replcmds on
pubsliher". usually i just lower the transaction count and it will
solve it. Timeouts are already set really high. I just think the
backup software and replication fight for the control of the db.
thx comb
sql