Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Veritas 10 v.5520 Error 1068

Status
Not open for further replies.

johng75

IS-IT--Management
Joined
Jul 14, 2004
Messages
247
Location
US
background info:

heres my dilima, when veritas was installed on the machine originally, it was put on the c: drive, well after time the drive filled up, and while i was out it got down to 50+/-MB free on the drive, we looked at what was taking up the most room to move and saw that the SQL log file grew to 8+GB and was taking up most of the partition so we wanted to move it. after talking with the SQL person in house, we detached the SQL data base (BEDB) moved the 'bedb_dat.mdf' and the 'bedb_log.ldf' to another partition, then went and attached the data base back in SQL.

here is where it goes down hill:

when i attempt to restart the backup exec services i get the 1068 error

when i attempt to open up the veritas software, it tells me i can not conect to a media database, i then go and look back at the BEDB database i re-attached in SQL, and it makes two new mdf and ldf files in the origional folder and is pointed at them instead of the files i moved to another partition

everything is telling me to reinstall, but if i dont have to id rather not, i cant place the origional files back in the origional space because the drive has already takin up just enough space to where there isnt enough room

if for some reason the only way to get this to work is by re-installing, would i be able to re-install the veritas program to the c: drive, but place the two files in question to the other directory for storage reasons

server specs:

win 2k sp4
veritas 10 v. 5520

Life is not a journey to the grave with the intention
of arriving safely in a pretty and well preserved body,
but rather to skid in broadside, thoroughly used up,
totally worn out, and loudly proclaiming

--"WOW-- What a Ride!"
 
I'm not a BE expert...but 8 GB sounds like a bit much for the BEDB database. It sounds like BE isn't doing DB maintenance. What if you temporarily move some stuff off of the C: drive...move the DB back to the C: drive...run DB maintenance and see if that drops the size. Personally, I use a 4 week rotation, so I purge everythign out of the DB that is older than 8 weeks. That will probably drop your DB size tremendously. My BE database is about 6 MB. Also, don't forget to turn on the Maintenance Schedule so that it automatically does it.
 
use the beutility.exe in the Backup Exec directory.
After you add you server to the list right click on the server name and there is a option to set new database location. This will modify the registry to reflect the new instance name or location.

You could also look at HKLM\software\veritas\bedatabase registry hive and see if anything is out of place.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top