06-27-2016 05:54 AM
Hi,
After an ungraceful shutdown of my backup server (electricity loss), i'm unable to restart netbackup.
First, i found my vxdbms.conf was corrupt :
11:01:53.639 [10028.10024] <2> read_legacy_touch_file: Found C:\Program Files\Veritas\NetBackupDB\data\vxdbms.conf; requested from(vxdbms_conf.cpp.1529). 11:01:53.639 [10028.10024] <16> ReadVxDBMS_ConfFile: Illegal configuration file: C:\Program Files\Veritas\NetBackupDB\data\vxdbms.conf
It's wasn't a 0kb file, but with strange symbol within.
I recreate it with https://www.veritas.com/support/en_US/article.TECH48879
But, it's still impossible to start, emm, and i have this error when i try to ping the database :
13:25:36.281 [6964.7844] <4> ping_database: ODBC connection string=DRIVER=NB SQL Anywhere;CS=utf8;UID=dba;PWD=***************;LINKS=shmem,tcpip{PORT=13785};ServerName=XXXXXXXXX;DBN=NBDB 13:25:36.281 [6964.7844] <16> ping_database: ODBC connection failed. 13:25:36.281 [6964.7844] <16> ping_database: ErrMsg [Sybase][ODBC Driver][SQL Anywhere]Le mot de passe ou l'ID utilisateur est incorrect, ErrCode -1, Sqlstate 28000
I found it's possible to reinitialize it (http://www.veritas.com/support/en_US/article.000044417), but, i don't want thing to get worse.
Should i continue in this way ?
Thank for your help
G. DESSOLLE
OS : w2k12r2
NB : 7.7.1
Solved! Go to Solution.
06-27-2016 07:27 AM
Providing you run catalog backups, you should have a copy of the catalog NBDB files in /usr/openv/db/staging.
Copy the vxdbms.conf file back from there and see if that helps.
06-27-2016 06:46 AM
Please log a Sev 1 call with Veritas Support.
06-27-2016 07:27 AM
Providing you run catalog backups, you should have a copy of the catalog NBDB files in /usr/openv/db/staging.
Copy the vxdbms.conf file back from there and see if that helps.
06-27-2016 07:28 AM
OK, windows path to staging dir may be a bit different ....
NetbackupDB\staging I think from memory
06-27-2016 08:17 AM
Recovering from Staging or your catalog is the best way to get NBU environment up and runnnig
06-27-2016 11:14 AM
If only vxdbms.conf is 'damaged' no need to revocer everything
06-28-2016 12:18 AM
Thank you for helping out.
With the version of vxdbms.conf from staging, everything restart (fine i hope...). I test some bakup and restore, everything is working.
Is there any software or utility to test everything is allright ?
06-29-2016 05:22 AM
It is alright, if vxdbms.conf is messed up, NBU wouldn't be running ...
06-30-2016 12:22 AM
It is alright, if vxdbms.conf is messed up, NBU wouldn't be running ...
I realize it
This backup server is disk based, and i have doubt about my data files.
My doubts are based there ?
06-30-2016 08:32 PM
06-30-2016 11:37 PM
OK, why are you concerned about the data files - I presume by this you mean the actual 'images' stored on the 'disk' storage unit ?
What has happened that makes you think there could be an issue.
I agree with Marianne, there is no real way to check these files apart from restoring.
07-01-2016 02:25 AM
The best way to test/validate backup media is by running test restores
I test some, and everything is ok.
The OS would've run a filesystem check on all mount points at boot time. Any disk or filesystem errors would be logged to the OS system log.
Everything is ok.
OK, why are you concerned about the data files - I presume by this you mean the actual 'images' stored on the 'disk' storage unit ?
Yes. I have a puredisk diskpool. Because of deduplication, with little corrupt data, we can lose a lot backup.
What has happened that makes you think there could be an issue.
I have no log of the corruption of my vxdbms.conf. This is what makes me doubt the rest.
I rely on your experience, i will make other restore test.
Thank a lot for your help.
You can close the topic.