Following the Feb SBS users group meeting...
We had a great meeting the other week and covered a lot of ground. The PowerPoint deck will shortly be available for download on the www.sbsusers.net site (go to the meetings page).
We had a discussion about some issues being experienced with Backup Exec on SBS. Andrew (one of my team) has covered this ground several times and came up with the goods - in particular how to get jobs that get to 99% to complete successfully rather than just sit in a pending state.
Turns out David from the Sydney SBS group has the same frustrations, so for all of you with Backup Exec woes, get ready to smile...
How to configure VERITAS Backup Exec (tm) to automatically respond to media alerts, including when a backup hangs at 99%, until the user responds to a tape eject prompt
Identified by looking in Event Viewer – Applications: Event ID 58061 is shown
http://seer.support.veritas.com/docs/192055.htm
That should do it! And for some more little gems Andrew has found...
OFO: Initialization failure on: "Shadow?Copy?Components" Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). VSS Snapshot error. Unexpected provider error.
Identified by looking in Event Viewer – Applications: Event ID 34113 is shown. Often also associated as being a METADATA error
http://seer.support.veritas.com/docs/265927.htm
And be aware of ports in use when installing Backup Exec 10
After a reboot or restarting the Backup Exec services, the Backup Exec Server Service fails to start with the following error: "An internal error (-14) occurred in object 10."
Identified by looking in Event Viewer – Applications: Event ID 57802 is shown.
http://seer.support.veritas.com/docs/275017.htm
You will need to use netstat –a to find what ports are open
Refer to “netstat /?“ for full usage details
Another topic discussed was clearing out badmail folder entries where there are HEAPS of them present. Opening the folder in Windows Explorer, or even a command prompt, can be unsuccessful when there are thousands of entries. So, Microsoft have a VBscript to deal with this (again thanks to Andrew for finding this one). Smply visit http://support.microsoft.com/?kbid=867642
Finally, if you find an Exchange server that's being used as an open relay and want to get it cleaned up, visit http://support.microsoft.com/?kbid=324958
Of course you're better of not being an open relay in the first place.
Right - time to get back to work. Oh, that reminds me, details for the March SBS users group meeting need to be posted here...stay tuned...