Somebody help me; I noticed that

[vagner76]

Somebody help me;

I noticed that in the database directory I have many database files, like:
ASTPSDAT.000 with 374 MB
ASTPSDAT.001 with 256 MB
ASTPSDAT.002 with 152 MB
ASTPSDAT.033 with 0 MB
ASOBJECT.000 with 24 MB
ASOBJECT.001 with 37 MB
ASOBJECT.002 with 7 MB
ASOBJECT.016 with 0 MB
ASTAPE.000 ~ASTAPE.0023
RDM.CHK with 12MB

Furthermore, on the activity Log there are many messages like: [CAT] Invalid session signature (DDDD)

My backups job has been spending a lot of time on "Connect to Media..".

What can Ido?

Any help would be much appreciated.

 

[TheLad]

Ok, help us. What version of Arcserve (inc. Serice Packs) and what operating system (inc. Service Packs) etc..... -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ARCserveGuru]

The files you have described are the database files. They will be big unless you prune and pack them regularly.

If you wish to start from scratch, then you can initialse all database (but you will lose media pool information). But first, please tell us what TheLad asked for to properly troubleshoot.

Thanks

g

 

[vagner76]

I have an ArcServe 2000 with sp4 installed on a Win2000 Server with sp2 and 2 Overland Libraries (DLT 40/80) with 10 Tapes each.

My "DB Prunning" has been running everyday with "Prune records older than 3 days". I already have been cleaned my databases but the problem was not solved.

Thanks

ps.: Sorry for my poor English

 

[ARCserveGuru]

Can we get an idea of the number of files your backing up? Or at least the number of gig?

Thanks,

g

 

[vagner76]

Something like:
Total Size............ 22Gb
Total Files........... 3,301
Total Directories..... 92

Thanks,

Vagner76

 

[jabus]

The number of GB backed up has nothing to do with the size of the database--it's strictly the # of files that causes the database to grow. With such few files, it sounds like it grew before the prune days was changed from the default of 30 to 3.

As far as the lengthy Connect to media, with DLT's, it is common to take several minutes to connect to the media (or session), as it has to load the tape, determine which tape it is, and seek to the appropriate part of the tape (even longer for appending).

I have not seen the Invalid Session Signature error. However, a couple of things to think about/try are:
- is it possible that one or two tapes are the only ones getting the error?
- have you tried doing a full erase of the tapes?
- are you doing a quick erase, or quick erase plus?
- do you have the latest driver/firmware for the devices?

 

[vagner76]

Thanks!!!!!!! I'll try to do it!!!!!!!

But, does anyone knows why I have multiple files: as*.000; as*.001; as*.002; as*.003

Thanks

 

[jabus]

It's just the way the Raima/Velocis database works. I don't know the internal workings as to why, but I do know that it is completely normal.