My experience tells me that you need to completely blow away the devcfg files in order for the target server to communicate to the library in a windows environment. This means you need to recreate definitions for the library, drives, and paths.
You can do this quickly by keeping a copy of...
We've recently implemented an IronPort C30 appliance for antiSPAM (BrightMAIL) and anti-virus (Sophos). In addition, we have McAfee Virus Scan (server) and GroupShield (info store) on the Exchange 2003 server. IronPort catches 98% of the SPAM and viruses so our Exchange server has plenty of...
Do you want to truly load balance or create an Exchange cluster? If the latter, be aware that the cluster maintenance is sometimes more work than having a warn spare server ready to go in the event of catastrophic failure.
Lastly kudos to Tivoli Storage Manager for being such a robust product!! Despite all of the hardware failures we encounter and the millions of drive errors, we were always able to restore data on demand.
STK has finally fessed up - the drive firmware is the root cause of the problem. Despite initial industry claims, LTO drives DO need to be cleaned on a regular schedule. After much back-and-forth with STK, we are now error free on a nightly basis.
** Warning: if you are in the Midwest US...
As mentioned above, STK created the CE role specifically for these tasks. If you're in dire straits, call support and ask to speak with the situation manager who's on call. Don't waste time with a level three engineer - talk to someone who can take action.
Agree with k111rh, need to know your hardware spec. For example, STK only certifies Maxell and FujiFilm on their L-class libraries. You WILL run into problems with anything else...
Approximately 18 months ago, I performed due diligence on the following enterprise backup software: Legato, TSM, Veritas, ARCServe and CommVault. Based on our internal criteria, TSM and CommVault scored the highest, with Veritas a close second. At the time, CommVault did not have very mature...
Thanks to all who have added to this thread. After much nudging, STK and Seagate have identified two core issues with the Seagate Viper 220 firmware. One of those issues/errors forces STK to look at our TSM activity logs. The specific sense data will usually indicate a Locate error. Prior...
Specific error from TSM activity log is:
ANR8302E I/O error on drive DRIVE5 (mt5.0.0.2) (OP=READ, Error Number=1117, CC=205, KEY=FF, ASC=FF, ASCQ=FF, SENSE=**NONE**, Description=SCSI adapter failure). Refer to Appendix D in the 'Messages' manual for recommended action.
This error can be...
L180 with 5 Seagate LTO G1 Viper 220 SCSI drives in place for about a year. Also have Crossroads 3400 fibre-to-SCSI bridge in place. Backup software is TSM 5.1.5 and very stable on Windows 2000 Advanced Server. STK has been assisting for 8 weeks - all drives, cables, and bridge replaced...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.