>>We had a situation yesterday where 2 VE backups were causing the VM's to go
>>unresponsive. No response to ping, unable to RDP, etc. As soon as the
>>backup finished (or was killed in one case), the servers picked back up where
>>they left off. They never rebooted, but you can actually see
Rick,
This all began after a recent audit revealed many systems either had missed
backup schedules, excessive retention, or no backups at all, which led to the
question of how we can better account for them on a day-to-day basis. Of
course then the usual finger pointing ensued and management a
Our Oracle backups have three scenarios.
1) Home grown scripts are scheduled via cron on the Oracle server,
copy/compress the db to local disk, then pushed the db backup to TSM via a dsmc
backup of the backup disk area.
2) RMAN backups are scheduled via cron which push data to TSM via LanFr
I assume someone has dealt with this I would like to hear how they handled it.
The issue:
DB2 and/or Oracle database backups that are dependent on completion of external
processes.
Currently our DBA's utilize a variety of methods to initiate DB2 and Oracle
database backups (CRON, external sched
First, many thanks to Wanda & others who have been so helpful in answering my
previous VE questions!
We had a situation yesterday where 2 VE backups were causing the VM's to go
unresponsive. No response to ping, unable to RDP, etc. As soon as the backup
finished (or was killed in one case), t
