TSM client for SCO Open Server Release 5.0.6

2001-05-02 Thread Kim McCubbin
Is anyone using TSM to back up a Sco Open Server Release 5.0.6 client? I checked the ftp site but could only find a SCO Unixware 7 client. Where can I get the client? Thanks, Kim McCubbin Server Support Specialist Publishers Printing 100 Frank E. Simon Ave. Shepherdsville, KY 40165 Phone

Re: Expire Inventory

2001-04-19 Thread Kim McCubbin
Upgrade to 3.7.4.3. We had the same problem. [EMAIL PROTECTED] 04/19/01 01:14PM Recently upgraded from ADSM 3.1 to TSM 3.7.2. I believe there is a problem with Expire Inventory not updating the database correctly. Anyone else experience this or know of any problems ?? Thanks in advance

Missing MAC Headers after upgrading to Tivoli

2001-03-12 Thread Kim McCubbin
Volume on NT 4.0 Service Pack 6 server running Tivoli client 3.7.2.19. The NT server gets backed up by Tivoli 3.7.4.3 running on AIX 4.3.2 server. The files go straight to 3494 tape library and are kept on tape for 26 months. Any help will be greatly appreciated. Thanks, Kim McCubbin [EMAIL

Re: Missing MAC Headers after upgrading to Tivoli

2001-03-12 Thread Kim McCubbin
what I find out. Thanks, Kim McCubbin [EMAIL PROTECTED] 03/12/01 04:40PM I have been backing up Mac files on NT servers since the ADSM 3.1 days. This has been one of those problems that has been fixed and resurfaced many times throughout my upgrade processes. I am currently at 4.1.2

Groupwise Restore Problems??

2001-01-12 Thread Kim McCubbin
I am upgrading the hardware on my GroupWise 5.5.2 secondary domain this weekend. Is anyone aware of any problems I may run into after performing a backup of the old system and a restore to the new system via TSM? Our TSM server is version 3.7.4.2 and the Novell Client is version 3.1.0.7.

No Backup Copygroup

2000-10-26 Thread Kim McCubbin
I am seeing ANS5128E errors on an NT node that is incrementally backed up daily. The error says "no backup copy group". That error shows up in the Event Viewer on the NT station. In the actual dsmerror.log it gives the same error message with a different error number: "ANS1105E Management