Search results for query: *

This sounds like the kind of behaviour you get when administering Arcserve manager through a Windows 2000 Terminal Services session. You dont say which Arcserve service pack you are using. You need SP4 to fix the Terminal Service problem.

The only workaround I have found so far is that once the GFS job has run click the name of the tape in the destination tab. You have to do this every day on every server. Great 'n it. CA say this is by design. If you look in the laundry list of SP4 fixes it says "custom jobs will no longer...

I had same problem. Arcserve with SP4 will no longer append a custom job to a tape that has been GFS labelled.

Modify the job. Click the filter button. Exclude files of type: C:\winnt\system32\perflib_perfdata_*.dat Click add. Resubmit your job. No more problem.

I have seen this before, something to do with the arcserve database. You could try the command line DBFIX but this could take several hours or several days depending on the size of the database. I reinitialized the database and it was OK. http://support.ca.com/techbases/as2000/as2k-1521.html

I had this problem. I used the filter to filter out files of type %SystemRoot%\System32\Perflib_Perfdata*.dat