Search results for query: *

IntelliSync seems to link everything to an XDA - not sure whether it will work for you. cdav

DebiJo, I assume you are talking about RAID5 - if not please ignore. Is it your C: drive on the Raid set that you are trying to restore? If so, we have come across a similar problem on NT4. When you delete and recreate the C: drive during the DR, it leaves 8 Mb of 'odd' space in front of the C...

I use the NT version. If it works the same, access the Database, look at the media view, and check for 'Destroyed' tapes. Delete these out of the media view, and this should help you considerably without initialising the database. Hope this is useful (and relevant!) cdav

1) Order of backup - try modifying the 'source priority'. It is a button that comes up on one of the final windows when you schedule a job. This allows you to change the order that things are backed up to tape. 2) Getting a job to start after the first one has finished - schedule them for about...

We have had a similar problem. In our Pre batch file, we stop and start the Arcserve Tape engine. This gives it a kick, forces it to inventory the tapes, and hey presto! it finds the tape for the backup. Cdav

I have certainly had this type of problem with the RAIMA databases. I am currently setting servers to use VLDB databases, with the intention of testing the corruption problems. I will let you know how I get on. cdav

I have no experience with Sybase, but if you can't see something when trying to set up the backup, it is usually because the Arcserve agent for that product either is not loaded at all, or was installed before the service was installed. Eg if you have SQL loaded on a server and try to back up...

My experience is that this is a transient message, assuming that it is the Arcserve database that is not backing up. I would suggest a stop and start of the engine, and monitor for a couple of days. Sorry if you've already done this.

I don't know much about moving the database - I've never tried that, although I believe that it expects the database to be wherever the Arcserve software is (Don't quote me on that, though) Another approach: What is your database prune interval set to? It defaults to 30 days ie it will delete...

When I get "Unable to position media", it is either a duff tape or, more likely, a faulty tape drive. I would suggest our normal procedure (if you haven't done this already) 1) clean tape drive thoroughly 2) get a new tape (out of the packet) and use this to do your next backup. If you...

It is worth stopping and starting the engines - this will sometimes cause the job to kick off within a couple of minutes. I haven't come up with a reason why it does this, but I always try this first when a job has not run and there are no apparent problems. Hope this helps.

In my experience, this is a tape drive problem. It may simply be a case of cleaning the drive and using a new tape, but you are likely to need to swap out the drive. Hope this is of some use - if a little late! cdav

I agree with cichlid - that's the way we do it as well. cdav

Just a thought - have you tried changing the priority of the backups ie backing up the e: drive first, or even doing a 'special' backup and back up the e: drive alone? This may at least give you an idea whether it is specifically to do with the e: drive, or whether this is a coincidence. I have...

Don't think you need a reinstall for this - and besides, I don't think it will make any difference to this problem. Try the database initialise - it sound as if there may be some corruption there.

What does it actually say? If it just says "Stopping...." and never actually stops, even after stopping and starting the engines, I have had to reboot the server to get out of this! After getting the job finally stopped, it may well be worth checking the start of the database. If there...

Progress guys! I don't know whether you are backing up individual drives, or backing up the whole server through Arcserve. We back up individual drives and Exchange (not bricks level) and, when we investigated further, we found that we could back up Exchange alone, then we could also back up...

If it is any help, when we get the error E8604 Failed to start backup. (DBNAME=dbaexch, EC=Backup Agent Error -- (331) "Insufficient privilege. Please check user privileges".) on our exchange servers, it is because we have not entered the exchange service account details in the...

Was the tape engine running? If it was, try stopping and starting the tape engine before doing a backup - this sometimes kicks it into life. If this doesn't work, we need some more information.

I've had this myself - it sometimes means that the database has got itself confused! I have found that stopping the engines (database and/or job) will often stop the job and clear the problem. Please let me know if this works for you.