Search results for query: *

I'm having the same issue with 4 out of 44 jobs. Reload from base is not an option for us since we use a CASO setup. So there's a central server which sets of the jobs for about 60 Managed Media Servers. I am not going to recreate the policies and jobs for 60 servers (it is scripted though). I...

You might have a bad tape. Does the problem occur on only one tape or several? And what if you make a new job doing the same thing using the same and a different tape? What does that do?

We discovered that the exeption error was caused by a discrepancy between the build level of the Arcserve 2000 base installation and the one of the Disaster Recovery Option (1100 vs 638). The difference was caused by the fact that we upgraded the base installation to SP4 for AS2000. The DRO...

We recently discovered a serious configuration problem in Arcserve 2000's DR process. When you use a Arcserve boot cd together with the server specific disk you might be interested in what's written here. During a Disaster Recovery the DR process at our site failed to create the partitions...

Hi. We are moving to BEX10 in a few months. Right now we are designing the new backup infrastructure. One of the open questions we have is how to delegate control of BEX10 to different support groups. We have a support group which should only be able to monitor and restore jobs and label...

That's not completely true, Lzcwsq. We are filtering out some files on Arcserve 2000 but it does doe the backup thanks to a patch we got from AS2000. It is also said to be included in SP5: PROB #: 28 FN: T36A015 FT: CJ8 DATE: 17 Oct 2002 STARTRAK PRODUCT NAME: ARCSNT (Star...

Hi there, we are stuggling with a locked out Arcserve 2000 system account. Ofcourse, E3073 messages are popping up everywhere in the arcserve log. However, we are still running succesfull backups, doing great restores and apparently are still able to do disaster recoveries. Does anyone know...

Does the arcserve.log file show a asterisk (*) before the Job ID number? If so, you have a corrupt Arcserve VLDB database.

I'd prefer using grep instead in combo with tail but unfortunately we run GNUtils on our Win32 servers and grep isn't included (yet).

Clues, anyone?

We do use the same hardware. Ofcourse, when an array controller fails, for example, we replace the faulty controller with a new one of exactly the same type. So hardware indifferencies won't be the cause of the problems.

Hi everybody! during a test recovery cases on a HP ML370 G1 we experienced a DR process crash during data restore with an error in a DR Application Exception Window. The job crashes at random moments during the DR restore. The error: Exception Time: Thu Aug 26 14.50:53 2004 Exception cause...

I am having a similar message during the DR process of a AS2000 machine. The DR restore stops with the exception error and then all I can do is reboot ending up with a corrupt system ofcourse. Maybe the dr.log can tell you more. You can start it by activating the DR logging during the DR...

The backup tape contains a full backup of the system.

Hi there, while doing a disaster recovery Arcserve did not see any sessions on the tape I used. When I merged the same tape on another Arcserve 2000 server it did show al the sessions on tape. So the sessions are on the tape but the DR program doesn't see them. Has anyone seen the same thing...

Or you can use some command line editing. I usually use the 'tail' command (GNU tool, also available for Windows, probable for free). Tail shows only the last lines of a particular file. You can tell tail :) how much lines must be shown. Start a command box on the server or via a remote command...

We also thought up an alternative with flag files placed at speficic locations on the filesystem and than do a backup without verify. After the job is completed we then start a Perl script which scans for these flag files to see if they are backed up properly.

We currently use the scan option verify on our Arcserve 2000 backups. We are a pretty large company and as you all probably know you have to work with tight schedules in which you can do your 'backup thing'. However, lately we cannot manage to get the backup and verify done within the set time...

We had this error on several hundreds of servers. All E6300 events in the arcserve.log. I had contact with Arcserve and they told me it was a conflict between the Compaq Storage Agents and the SCSI driver of the machine. For us the solution was to stop the Compaq Storage Agent (together with its...