Link to home
Start Free TrialLog in
Avatar of hscast
hscast

asked on

Arcserver 11.1 DB location

OK here is my problem.  I have a Backup server setup with Windows 2003 server.  I have installed Arcserve 11.1 on it.  It backs up all my other servers overnight.  I currently have it setup to store the information on my SQL server that is on another box.  So I set it as a Remote and Arcserve 11.1 put the data into the DB just fine.  But DB pruning does not work.  According to CA's site this is a known issue with Remote SQL server.  This Backup server is also set for a hot spare for our SQL box so if anything happens to the SQL box then I can start the SQL services on here.  Meaning I have it installed but turned off cause of Licensing.  So I can't put the DB local.  

My question is does anyone know if you can run Arcserve's own DB and move it to another Drive?  My C: where Arcserve is isntalled isn't really large enough to house the databse that Arcserve builds for itself.

Or does anyone know a fix to get DB Pruning to work on a Remote SQL server?
Avatar of dovidmichel
dovidmichel
Flag of United States of America image

The VLDB database has to be local. The only exception is if ARCserve is running on another system it can be setup for a Central Database, which will not work for you.

I have to check into a problem with DB Pruning on a remote SQL server.

Just in case you have not installed it alreay here is the URL for 11.1 SP1.
http://supportconnectw.ca.com/premium/storage/downloads/nt/111/basb111-patchmenu.asp
QO63594 119 MB 01/27/05 NT -BAB R11.1 SERVICE PACK 1 - ENGLISH

Also this should be installed.
QO64538 31.2 MB 02/17/05 NT -DISCOVERY SERVICE SECURITY VULNERABILITY  
Avatar of hscast
hscast

ASKER

I have SP1 installed.  The security patch isn't installed yet, but I'll do that.

Its a very odd problem.  I thought the prunning might have something to do with my tape library not working like it should.  Its says insert one of the following tapes in the drive, but it never goes out and gets the tapes.  It use to work fine before I changed servers and moved the DB remote.  Just hoping.
11.0 had the problem where the prune job would just hang. A patch was released to fix it and should have been rolled into 11.1.
A number of different things could cause a job to fail to take the correct tape.

For example if there are multiple jobs running at the same time one job might take the tape requested by the other. The job should end up taking one of the other tapes in the scratch set.

Another thing that can cause this is if the inventory is not correct.
Avatar of hscast

ASKER

I have only 1 job.

Tapes appear correctly in the save set and scratch set as the inventory on the tape library.  I've had it redo inventory as well.
This is getting a little confusing so lets detail things.

It seems like you are bringing three different problems.
1) Can VLDB be located on remote?
2) Problem with DB Prune job.
3) Problem with jobs use the right tape.

1) This one seems to have been taken care of.

Which job is not running the one for # 2 or # 1?
Avatar of hscast

ASKER

Sorry should have started another question.  Your right to many things going on here.  

there are 3 problems like you said.

1) Taken care of
2) DB prune job will not run if I have it set on a remote server.  I moved the Database to the local SQL server and it runs just fine. (can't leave it there due to licencing, but for testing it works).  Re-run the bconfig.exe and point the DB back to the remote server DB Prun job will not run.  Just sits there.
3) If there is a blank tape the job runs fine.  If there are no blanks it will not pick one of the tapes from the scratch set like it should.

Hope this helps clear the mud. :)
2) Based off the description it seems that the 11.0 fix was not included into 11.1. I'll see what else I can find out.
3) There are too many possibilities, give all the details.
Avatar of hscast

ASKER

2) thanks

3) Dell Powervault 20 tape LTO library. I have a single backup job set as GFS. 5 Day rotation each day is a Full backup.  Backup runs fine untill all the blank tapes are used up.  Then on the next backup it asks to put in 1 of 4 tapes or a Blank tape.  The 4 tapes are all shown and listed in the media pools and if you look at the device you can see them as well.  Backup then fails.
Is this enough?  Not sure how else to describe it.
2) I did some matching up on file dates and it does look like this one was missed from 11.1. So your only option there is to open an issue with CA.

Are you sure the tapes are in the Scratch set?
How many tape are there?
With that configuration you will need 21 tapes.
Oh, on problem # 2 here is something I just came across.
In the ARCserve Server Admin, Configuration, Database tab, there is a check box for Enable Remote BrightStor ARCserve Backup Database.
This option is used only when ARCserve is installed on this remote sysystem, so if that is checked it could be causing this problem.

Avatar of hscast

ASKER

Ok I'll give that check box a try for problem 2.

Any ideas on Problem 3?  I'm It happened again this Friday.  It didn't use one of the old weekly tapes. And just now it happened when I tried to run the scheduled backup for tonight.  

Here are some pictures of the request for tape, the devices showing you the tapes are in the library, and the media scratch set showing they are listed in there.

http://www.hscast.com/images/shane/arcserve/devices.jpg
http://www.hscast.com/images/shane/arcserve/media%20pool.jpg
2) You only want to use that checkbox if ARCserve is installed on the other system.
In your case it seems that only SQL is on the other system so you do not want to check that option.

Short on time now, I'll get to # 3 later today.
2) so if that check box is already not checked then we are back to your having to open an issue with CA.

3) From the pics it looks like the Tape Engine has correctly identified all the tapes, and the requested tapes are in the scratch set.

So that leads to either a DB problem or a communication problem between the DB and Tape Engines.
DB corruption is not very common with MS SQL but I guess it would not hurt to reindex and run a consistancy check.
For the Tape Engine end any other application that addresses the tape drive or library has the potential for causing problems.
The most common cuplprit there is the Windows OS tape device and media changer drivers.
Both should be disabled from within the Windows Device Manager and the system restarted.
Avatar of hscast

ASKER

2) I may have to now.  Its still not working correctly.

3) Well I went though SQL and checked the DB and indexed.  Everything looked OK.  I then disabled the devices in device manager like you suggested.  I also went into Database within Brightstore Manager and removed all the Media records that were not needed or incorrect.  I ran a couple test backups and its re-using the tapes as it should.  Now I'm not sure if it was the database that fixed it or device manager.  The database should be cleared out by the pruning correct?  So it could all be related.

Shane
ASKER CERTIFIED SOLUTION
Avatar of dovidmichel
dovidmichel
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial