The Active Log was never more than 2% full, and yes, I have an Archive
Failover Log, which was never written to and remained empty. Q DB F=D
shows blanks for Last Database Reorganization, which means it has never
been done? Hopefully never just since the last reboot. At any rate, DB
reorg was not w
We had the same issue until going to v6.3. DB reorgs were frequently the
cause of the problems. We had the ALLOWREORGTABLE server option off to
help prevent this, although there's a long-term performance hit from
that as well.
If you look in your TSM instance directory, you'll find a
db2dump/db2d
Could the active log also be filling because the archive log was full?
There are known issues with DB backup triggers in 6.2.2. (although we're
Windows, I think the problem is the same)
We've seen cases where the server would just fire db backup after db backup
after dbbackup, because the activ
TSM server 6.3.3 on Win2K8
Exchange 2010, 4 servers in a DAG config
TSM Client 6.4.0
TDP for Exchange 6.4 installed on a server with passive data bases only
VSS backups, no VSS Instant Restore
Backups run OK, can do mailbox restores, mailbox history is enabled.
Now, to restore individual mailbox i
The Archive Log got to 80% full, so it triggered a full TSM DB backup.
So far, so good.
However, as the first one was finishing, and before it could empty the
Archive Log, a second full TSM DB backup was triggered. For a short
while, there were two full TSM DB backups running. This second backup
w
I would like to know the licensing cost of TSM-TDP client for SQL
Could not find any links on the web.
Thanks in Advance.
Satish
+--
|This was sent by satish.vergh...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcen
