ARCServe Logs eat disk space

[Goid]

ARCServe 11.5. If a backup job sits waiting for a tape, tskjob####.log will write entries until the drive is full. I am wondering if anyone knows how to limit this log size? I've tried limiting tape log to 100 MB, but obviously that does nothing. I'd rather not sit through ARCServe support on this one as they never seem to know anything relevant.

Thanks

 

[davidmichel]

I think it is one of these
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\BrightStor ARCserve Backup\Base\Task\Common
TraceOperation
TraceMisc
TraceTSI
1 = enable
0 = disable

and Job Engine in debug.

 

[Goid]

those are the settings in question, however it seems that arcserve just does whatever it wants. I have 2 servers both running 11.5 SP4, one of them fills the c drive with logs, the other doesn't. All settings are the same on both servers, one fills up the drive, one doesn't.

Long story short, ARCServe is the worst software ever produced. They should just close up shop.

 

[davidmichel]

The older I get, the more the saying, "people create their own hell", is shown to be true.

Making those kind of statements about any product is unprofessional to say the least.

 

[Goid]

Look, I in no way insulted you, unless you are ARCServe. If you can honestly tell me that ARCServe is not the buggiest backup software on the market, then I will take your last point as valid. However, you would think that after producing backup software for the 6 years I have been involved with it, they would sort out an issue like this. It is a setting that renders servers useless when not monitored and differs from install to install. It has been there since ARCServe 11.1 and I am running on 11.5 SP4.

You can say I create my own hell, yes this is true, because I am still using the product.

Thanks

 

[davidmichel]

This as a forum for professionals, not further explanation should be necessary.

I've worked with backup products since the early 90s. I've worked with ARCserve, Backup Exec, Yosemite, mainly but others as well. I've been monitoring this and other forums for years on my time. I can honestly say they all have problems, they have all had their good times and their bad times. For the most part the biggest players maintain the best product, and those are ARCserve and Backup Exec. Since version 12 has come out there are a lot fewer questions being posted than there used to be. I've read that since ARCserve 12 CA's sales, # of clients, and market share have all gone up.

Now as for your problem, if it is a bug how come you are the only one with it? Sorry I've taken way too much of your time and certainly too much of mine. This is my spare time and so when it used up thats it. See most people don't help others , they don't even try. So I find plenty for me to do, and usually more than I have time for.

 

[Goid]

Just so it is on record. I phoned ARCServe on this and they have no solution for it. We went through disabling each trace via the registry, but there were no gains. I asked the helpdesk person how I can have one default install out of the box cause this issue and another on the exact same version doesn't, he didn't know. So his solution was to install ARCServe 12. Unfortunately ARCServe 12 will not work in my environment at this time because we run SQL 2008 express on these servers. When installing ARCServe 12, you must install some form of SQL 2005. There are compatibility issues with SQL 2005 and 2008.

 

[davidmichel]

Why not look at one of those logs to see what it filling it up, perhaps that will give a clue.

ARCserve 12 does not require SQL 2005.
As per the online compatibility matrix it is compatible with MS SQL 2008 Express except for I64 platform.