Defragment Arcserve 2000 v7.0 Databases

[andychatfield]

I am running out of space on the C: of our NT server. I am trying to defragment the 2 largest databases (astpsdat and asobject) and have come across a couple of problems.

1. I am not sure whether this is a problem or not, but when the database pruning job starts it finishes almost immediately informing me it has been successful . When I look in the database window of Arcserve manager and there remains a very long list of Job and Media records dating back much longer than the 15 days pruning time. Should these have been removed?

2. VLDB Utilities.
I have successfully carried out the DBcheck utility on the 2 databases I am interested in but it goes a bit pear shape from there.
I believe the next stage is to run dbdefrag. Here's the command: dbdefrag -L arcserve;admin;secret Astpsdat.
When I try to run the following text appears:

DBSTAT result: Unable to open database Astpsdat
DBSTAT Completed

If I stop and restart the Database service and try again it seems to work and very quickly returns the following results ( sorry if this is a bit long):

DBSTAT Utility - Velocis 2.1.399 [09-Feb-2000]
Copyright (c) 1992-2000 Centura Software Corporation. All Rights Reserved.

###########################################################
Database(s) : astpsdat
Maximum blocksize is 8192.
Blocksize is 1024.
###########################################################
***********************************************************

Database astpsdat has been opened for analysis

***********************************************************
Checking data file astpsdat.000.


The following record types are in this file
Record type DETAIL_RECORD = 56 bytes.

Slot size = 56 bytes.
Page size = 4096 bytes.
Slots per Page = 73.
1024 18 16 1.56%
2048 36 32 1.56%
3072 54 48 1.56%
* 4096 73 8 0.20%
5120 91 24 0.47%
6144 109 41 0.65%
7168 127 56 0.78%
8192 146 16 0.20%


***********************************************************
Checking key file astpsdat.001.


The following key fields are in this file
Key field KEY_TAPEVIEW = 8 bytes.

Slot size = 20 bytes.
Page size = 4096 bytes.
Slots per Page = 204.
1024 50 24 2.34%
2048 101 28 1.37%
3072 153 12 0.39%
* 4096 204 16 0.39%
5120 255 20 0.39%
6144 306 24 0.39%
7168 357 28 0.39%
8192 409 12 0.15%


***********************************************************
Checking key file astpsdat.002.


The following key fields are in this file
Key field KEY_LONGNAMEID = 4 bytes.

Slot size = 16 bytes.
Page size = 4096 bytes.
Slots per Page = 255.
1024 63 16 1.56%
2048 127 16 0.78%
3072 191 16 0.52%
* 4096 255 16 0.39%
5120 319 16 0.31%
6144 383 16 0.26%
7168 447 16 0.22%
8192 511 16 0.20%


***********************************************************
DBSTAT Completed

What does all of this mean? Has the database been defragmented?

The next thing I've tried is the Keybuild command:
keybuild -k -L arcserve;admin;secret astpsdat

This returns the following error:
Error: Invalid option flag '-K'
Also displays the usage information but i'm not really sure what it means.

I would greatly appreciate any help on this as we are getting vary tight for space. Down to 228mb free (is this the problem)

Thanks

 

[vschumpy]

I believe this is a bug in earlier versions of ARCserve 2000, apply SP5 to it and try again.

 

[RustyMajor]

I am in a similar boat. I have a 20GB database (we do not do any pruning) and ran the dbdefrag util and it ran very fast and gave a similar output like you posted. I then proceeded to the next step of running the keybuild utility (keybuild -k -L arcserve;admin;secret astpsdat). The keybuild process has been running for over 48 hours!!!! I found another post, somewhere in this forum, I think, where a guy ran keybuild on a 6GB db and it took him 38 hours. If my calculations are correct, the keybuild won't be done until sometime Thursday morning, three days from now!!

From that one guy's post, I calculate it takes about 6 hours per GB, so keep that in mind, and that's a complete guess so be warned! If you can free up space some other way (move i386 folder, profiles, etc) I'd prefer that.

 

[RustyMajor]

FYI, Thursday morning has come and gone and it's still going! The keybuild has been running for over 120 hours!! I hope it finishes soon....
One thing is for sure, I will NEVER run this utility again! =)

 

[davidmichel]

Astpsdat contains the list of files and directories backed up. All the rest of the history such as tape, job, session are in the other databases. So it might pay to just initialize this one database.

 

[RustyMajor]

The keybuild finally completed. I saved absolutely no space by running this utility (after deleting about 200 job records) and it took about 264 hours on a 20GB database. I can't believe it took the utility that long and I will never run it again!