Is it possible to set a null password for your DB user?

Last post 06-15-2017, 11:34 AM by piyu. 20 replies.
Sort Posts: Previous Next
  • Is it possible to set a null password for your DB user?
    Posted: 06-14-2017, 5:25 AM

    Hi

    We connect CommVault to our SAP Sybase ASE 16 DB normally using either the sapsa or sa account and corresponding password.

    During some restore tests we have a situation where the sa account effectively has a null password.

    Can you set a null password in CommVault? If we leave it blank we get an error message:

    Ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.ct_connect():directory service layer: internal directory control layer error: Requested server name not found. Do you want to modify properties again?

    That is the 'usual' message back from ASE to say it can't connect (could be incorrect DB name, password, anything - it's a misleading/unhelpful error message).

    If we say ‘no’ or ‘yes’ it still leaves the password field filled with ‘black dots’, so not sure whether it has accepted a null password. Either way, when we try and run the restore, CommVault fails with the same error message:

    Description: Connection to dataserver failed, Please make sure that SA password is empty before restoring master database

    So pretty certain it hasn't accepted that blank/null password.

    We tried creating a password for sa and were able to connect but then get the same error message saying that the password has to be empty!

    Any ideas how to set this?

    Thanks
    Ross 

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-14-2017, 9:44 AM

    Hi Ross,

     

    We accept null password for sybase sa user.

     

    1. Are you not able to create instance ? Do you see below errors during instance creation or after a failed master restore while modifying instance properties?

    Ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.ct_connect():directory service layer: internal directory control layer error: Requested server name not found. Do you want to modify properties again?

     

    Above error we get is from sybase server while trying connecting to server using isql. There can be many possibilities for this as below:

    A. Sybase server name passed in instance properties is not correct.

    B. Sybase server interface file doesnt have entry for sybase server.

    C. Sysbase system table sysservers is not having entry for sybase server.

     

    2. Regarding restore failure:

    We highly recommend to choose "Sybase create devices" option while restoring master database or system databases. Did you try master database restore using this option?

    http://documentation.commvault.com/commvault/v11/article?p=products/sybase/restore_adv.htm

    If not , can you please set sybase sever sa user actual password  under instance properties (save and ignore if you see connetion errors, password will be saved under instance properties) and try restore using "sybase create devices".

     

    Description: Connection to dataserver failed, Please make sure that SA password is empty before restoring master database

     

    Above error can be seen if master database restore failed and didnt load completly. As master database is not loaded and restored completly we are left with master database without password.

     

    Let us know how is goes.

     

    Thanks

    Piyush

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-14-2017, 11:02 AM

    Hi Piyush

    Thanks for your response.

    The 'Ct_connect' error message isn't recieved from isql. We can log into isql when the sa password is null without issue. The error message is actually displayed by CommVault, when we change the username and password in the settings. Previously they were set to user sapsa and a known password, but for the restore test we set to sa and tried to leave the password blank - then when we try and save we recieve the error.

    Yes we have tried with the "Sybase create devices" option selected too and this makes no difference; we get the same error message back: "Please make sure that SA password is empty before restoring master database or choose create device option in GUI".

    We also tried setting a password for sa, amending the connection settings with the correct password (which saved without an errors), and running a restore - both with and without  "Sybase create devices" option selected.

    Again, we get exactly the same message! 

    Regards
    Ross 

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-14-2017, 12:14 PM

    Hi Ross,

    This error is thrown by sybase server when it is not able to connect to server name provided in instance properties.

    Ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.ct_connect():directory service layer: internal directory control layer error: Requested server name not found. Do you want to modify properties again?


    During restore you should not change password 'Sybase instance' properties in CommCell Console. It should always be set to actual server password.

    To understand why restore is failing. Analyzing logs should help.

    Can you please escalate ticket ?

     

    Thanks

    Piyush

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-14-2017, 12:23 PM

    Also would like know know the sybase server version, commvault version.

     

    Thanks

    Piyush

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 3:55 AM

    The properties in CommCell console are set to use the sapsa account. During our restore/DR test, the master database has gone (and then rebuilt as a blank master using the Sybase ASE recovery tools) and no longer contains the sapsa account. So we have to change the account/password, to use the only account available, sa.

    We actually recieve our support via another third party supplier and have raised a support ticket with them; I raised it here on the support forums in case someone else had experienced a similar issue.

    We are running Sybase ASE 16.0 SP02 PL04 HF1 (shortly to be upgraded to PL05 HF1); I will check on the CommVault version.

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 4:09 AM

    CommVault - Version: 10 R2 Build 166 SP15

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 4:09 AM

    Hi Ross,

     

    Thanks. If master device is gone or lost, we can use same sapsa account in sybase instance properties and use "Sybase create device" option with master database restore. That will first create master device and then once master is created we will load master database dump.

    During this process when we create master device , we dont connect to it using sapsa account , instead we will connect it using sa <no password> internally. Once master database is loaded from our backups, then comes connection using sapsa which you specified in instance properties.

     

    I would recommend this once to be tried:

     

    1. Have same sapsa accound and password under instance properties (even GUI pops up error it will save when you click ok"

    2. Choose "sybase create devices" while restore master/system databases (assuming master device doesn't exist physically or you can rename if it is created from past attempts).

    3. Let us know if this helps.

     

    Thanks

    Piyush

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 4:18 AM

    Ah ok, that makes sense... I will give that a try, many thanks! Smile

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 5:04 AM

    Ok, steps tried.

    Set username and password back to what they were in CommVault (sapsa account).

    Shutdown ASE.

    Removed master.dat.

    Ran the CommVault restore as suggested/as per documentation:

    1. From the CommCell Browser, expand Client Computers > client > Sybase.
    2. Right-click the instance, point to All Tasks and then click Restore Sybase Server.

      The Sybase Restore dialog box is displayed.

    3. On the General tab, select the Sybase Create Devices check box.
    4. Click OK to start the restore.

     

    Unfortunately, we get exactly the same error:

    Error Code: [71:40]
    Description: Connection to dataserver failed, Please make sure that SA password is empty before restoring master database or choose create device option in GUI.
    Source: dc1stddadb01, Process: ClSybAgent


    The detailed error logs show:

    3513 bdb94740 06/15 09:41:17 854189 SybAgent::SybAgent() - Creating the SybJob Object

    3513 bdb94740 06/15 09:41:17 854189 SybAgent::SybAgent() - Got the client Name = dc1stddadb01

    3513 bdb94740 06/15 09:41:17 854189 GetCommServerName() - cp=wlkcomsrv001h.wilko.co.uk,hostname=wlkcomsrv001h.wilko.co.uk

    3513 bdb94740 06/15 09:41:17 854189 SybAgent::SybAgent() - SybJobInfo::Init  JobID=854189  , CSName = wlkcomsrv001h.wilko.co.uk, VMName = Instance001

    3513 bdb94740 06/15 09:41:17 854189 Cvcl::init() - CVCL: Running in FIPS Mode

    3513 bdb94740 06/15 09:41:17 854189 ClSybAgent::ConnectBackToAgent() - attachBackToRequester succeeded

    3513 bdb94740 06/15 09:41:17 854189 SybJobUnit::Initialize() - Constructing CVRstJobClient object

    3513 bdb94740 06/15 09:41:17 854189 Init() - Initializing job control [token=No Token,cn=dc1stddadb01], serverName [wlkcomsrv001h.wilko.co.uk], ControlFlag [1], Job Id [854189]

    3513 bdb94740 06/15 09:41:21 854189 ClSybAgent::ReceiveInitMessage() - Sybase Server : TDD, sa user: sapsa, Sybase Home: /sybase/TDD, ASE: ASE-16_0,                                                                                                                      OCS: OCS-16_0 Shared Memory dir: /sybase/TDD/ASE-16_0, Server Config file: /sybase/TDD/ASE-16_0/install/RUN_TDD_BS,                                                                                                                   Page size: 2048, Max Page size: 16384

    3513 bdb94740 06/15 09:41:21 854189 ClSybAgent::ReceiveInitMessage() - Copy : 0, restoreOptions: 550, restoreTime: 0,                                                                                 total DBs to restore: 9

    3513 bdb94740 06/15 09:41:21 854189 ClSybAgent::SybImpersonateUser() - Changing user to  user=sybtdd, gid=501, uid=81201

    3513 bdb94740 06/15 09:41:21 854189 ClSybAgent::VerifySybVersion() - Relink File name = /sybase/TDD/GalaxyRelinkInfo

    3513 bdb94740 06/15 09:41:21 854189 ClSybAgent::VerifySybVersion() - Received installVer = 10.0.0(BUILD116)

    3513 bdb94740 06/15 09:41:21 854189 ClSybAgent::VerifySybVersion() -  Running Version = 10.0.0(BUILD116)

    3513 bdb94740 06/15 09:41:22 854189 ClSybRestore::Restore() - Total DBs to restore: 9, Restore Options: 550, Copy: 0, Restoretime: 0

    3513 bdb94740 06/15 09:41:22 854189 ClSybBrowseAgent::checkClusterEdition() - path of dataserver: /sybase/TDD/ASE-16_0/bin/dataserver -v

    3513 bdb94740 06/15 09:41:22 854189 ClSybBrowseAgent::checkClusterEdition() - /sybase/TDD/ASE-16_0/bin/dataserver -v output: Adaptive Server Enterprise/16.0 SP02 PL04 HF1/EBF 26462 SMP/P/x86_64/Enterprise Linux/ase160sp02pl04x/2602/64-bit/FBO/Tue Aug 23 01:58:56 2016

    3513 bdb94740 06/15 09:41:22 854189 ClSybBrowseAgent::checkClusterEdition() - line = Adaptive Server Enterprise/16.0 SP02 PL04 HF1/EBF 26462 SMP/P/x86_64/Enterprise Linux/ase160sp02pl04x/2602/64-bit/FBO/Tue Aug 23 01:58:56 2016

    3513 bdb94740 06/15 09:41:22 854189 CvSybDB::InitSybConnection() - Server Name: TDD User: sapsa

    3513 bdb94740 06/15 09:41:22 854189 cv_syb_clientmsg_cb() - Message String: ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed

    3513 bdb94740 06/15 09:41:22 854189 cv_syb_connect() - ct_connect failed

    3513 bdb94740 06/15 09:41:22 854189 cv_syb_connect() - Retry connect with password encrption

    3513 bdb94740 06/15 09:41:22 854189 cv_syb_connect() - ct_connect retry

    3513 bdb94740 06/15 09:41:22 854189 cv_syb_clientmsg_cb() - Message String: ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed

    3513 bdb94740 06/15 09:41:22 854189 cv_syb_connect() - ct_connect failed again

    3513 bdb94740 06/15 09:41:22 854189 CvSybDB::InitSybConnection() - error message: ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failedct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed

    3513 bdb94740 06/15 09:41:22 854189 CvSybDB::InitSybConnection() - cv_syb_connect failed

    3513 bdb94740 06/15 09:41:22 854189 CvSybDB::InitSybConnection() - Cleaning up the connection

    3513 bdb94740 06/15 09:41:22 854189 ClSybRestore::Restore() - InitSybConnection failed

    3513 bdb94740 06/15 09:41:22 854189 ClSybRestore::ReceiveRestoreReq() - Received SYB_DB_70_MASTER_RESTORE_REQ for DB: master

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - access failed with an error [2]

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - Seems to be sybase 15. Just processeing master.dat is good enough.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - LD_LIBRARY_PATH_32= NOT SET

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - SYBASE=/sybase/TDD

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - SYBASE_ASE=ASE-16_0

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - RUNNING /sybase/TDD/ASE-16_0/bin/dataserver -s TDD -b450M -f -z 16384 -d /sybase/TDD/sybsystem/master.dat -c /sybase/TDD/ASE-16_0/install/RUN_TDD_BS

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.31 kernel  SySAM: Using licenses from: /sybase/TDD/SYSAM-2_0/licenses/SYBASE.lic:/sybase/TDD/SYSAM-2_0/licenses/SYBASE_ASE_DE.lic:/sybase/TDD/SYSAM-2_0/licenses/SYBASE_ASE_XE.lic:/sybase/TDD/SYSAM-2_0/licenses/SYBASE_SAP.lic

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 kernel  SySAM: Checked out license for 4 ASE_CORE (2020.1231/permanent/0A1A 1A20 16D1 8E93).

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 kernel  This product is licensed to: SAP, for use with SAP Business Applications.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 kernel  Checked out license ASE_CORE

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 kernel  Adaptive Server Enterprise (Enterprise Edition)

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 kernel  Performing space allocation for device '/sybase/TDD/sybsystem/master.dat' (0.44 Gb).  This may take some time.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 kernel  Finished initialization.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 kernel  Using config area from primary master device.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 server  Configuration Error: Configuration file '/sybase/TDD/ASE-16_0/install/RUN_TDD_BS' has an unknown format on line 10.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 server  Configuration Error: A Named Cache with 'cache status=default data cache' does not exist in the configuration file.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - There return value of popen(/sybase/TDD/ASE-16_0/bin/dataserver -s TDD -b450M -f -z 16384 -d /sybase/TDD/sybsystem/master.dat -c /sybase/TDD/ASE-16_0/install/RUN_TDD_BS) is non-zero with error: 2

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - Successfuly set the environment [export PATH=/sybase/TDD//ASE-16_0/bin:/sybase/TDD//ASE-16_0/install:$PATH]

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::StartServerInRecoveryMode() - RUNNING startserver -f /tmp/m_RUN_temp_TDD

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::StartServerInRecoveryMode() - 00:0000:00000:00000:2017/06/15 09:41:22.36 kernel  The configuration area in device '/sybase/TDD/sybsystem/master.dat' appears to be corrupt. The server cannot continue and will shut down.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::StartServerInRecoveryMode() - Sleeping for 20 seconds after starting server in recovery mode

    3513 bdb94740 06/15 09:41:42 854189 CvSybSysRecovery::StartServerInRecoveryMode() -  DONE of startserver -f /tmp/m_RUN_temp_TDD

    3513 bdb94740 06/15 09:41:42 854189 CvSybDB::InitSybConnection() - Server Name: TDD User: sa

    3513 bdb94740 06/15 09:41:42 854189 cv_syb_clientmsg_cb() - Message String: ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed

    3513 bdb94740 06/15 09:41:42 854189 cv_syb_connect() - ct_connect failed

    3513 bdb94740 06/15 09:41:42 854189 cv_syb_connect() - Retry connect with password encrption

    3513 bdb94740 06/15 09:41:42 854189 cv_syb_connect() - ct_connect retry

    3513 bdb94740 06/15 09:41:42 854189 cv_syb_clientmsg_cb() - Message String: ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed

    3513 bdb94740 06/15 09:41:42 854189 cv_syb_connect() - ct_connect failed again

    3513 bdb94740 06/15 09:41:42 854189 CvSybDB::InitSybConnection() - error message: ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failedct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed

    3513 bdb94740 06/15 09:41:42 854189 CvSybDB::InitSybConnection() - cv_syb_connect failed

    3513 bdb94740 06/15 09:41:42 854189 CvSybDB::InitSybConnection() - Cleaning up the connection

    3513 bdb94740 06/15 09:41:42 854189 CvSybSysRecovery::CreateMasterDatabase() - Could not connect to recovered database

    3513 bdb94740 06/15 09:41:42 854189 JM Client  CVJobClient::setPendingCause(). same messageid is being sent for the same job id within a short time period. so dropping the JPR

    3513 bdb94740 06/15 09:41:42 854189 CvSybDBRecovery::setPendingCause() - Failed to set the pending cause. please check the logs

    3513 bdb94740 06/15 09:41:42 854189 CvSybSysRecovery::PreLoadDatabase() - CreateMasterDatabase failed

    3513 bdb94740 06/15 09:41:42 854189 ClSybRestore::Restore() - PreLoadDatabase failed

    3513 bdb94740 06/15 09:41:42 854189 ClSybRestore::Restore() - Completed count: 0

    3513 bdb94740 06/15 09:41:42 854189 ClAgentSybJobUnit::NotifyCommServe() - Entering..

    3513 bdb94740 06/15 09:41:42 854189 Sending FAILED complete message to JM, 854189

    3513 bdb94740 06/15 09:41:42 854189 ClSybRestore::Restore() - The database job is completed

    3513 bdb94740 06/15 09:41:42 854189 ClSybAgent::Restore() - Restore failed

     

    So it tries to use sapsa at one point which of course won't work, but then it tries sa later - but stil fails?

    Regards
    Ross 

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 5:18 AM

    Thanks for the logs Ross

     

    1. Server Configuration file under instance properties looks incorrect here:  Here configuration file is given as Sybase backupserver run server file. You need to change it and have sybase server configuration file specified.

    It should be like/sybase/TDD/TDD.cfg with default installation.

     

    3513 bdb94740 06/15 09:41:21 854189 ClSybAgent::ReceiveInitMessage() - Sybase Server : TDD, sa user: sapsa, Sybase Home: /sybase/TDD, ASE: ASE-16_0,                                                                                                                      OCS: OCS-16_0 Shared Memory dir: /sybase/TDD/ASE-16_0, Server Config file: /sybase/TDD/ASE-16_0/install/RUN_TDD_BS,                                                                                                                   Page size: 2048, Max Page size: 16384

    3513 bdb94740 06/15 09:41:21 854189 ClSybAgent::ReceiveInitMessage() - Copy : 0, restoreOptions: 550, restoreTime: 0,                                                                                 total DBs to restore: 9

     

    2. As config file is wrong, when commvault tried creating master device if failed as dataserver command didnt find correct config file to read and values under it.

     

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - RUNNING /sybase/TDD/ASE-16_0/bin/dataserver -s TDD -b450M -f -z 16384 -d /sybase/TDD/sybsystem/master.dat -c /sybase/TDD/ASE-16_0/install/RUN_TDD_BS

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 kernel  Performing space allocation for device '/sybase/TDD/sybsystem/master.dat' (0.44 Gb).  This may take some time.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 kernel  Finished initialization.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 kernel  Using config area from primary master device.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 server  Configuration Error: Configuration file '/sybase/TDD/ASE-16_0/install/RUN_TDD_BS' has an unknown format on line 10.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - 00:0000:00000:00000:2017/06/15 09:41:22.33 server  Configuration Error: A Named Cache with 'cache status=default data cache' does not exist in the configuration file.

    3513 bdb94740 06/15 09:41:22 854189 CvSybSysRecovery::CreateMasterDatabase() - There return value of popen(/sybase/TDD/ASE-16_0/bin/dataserver -s TDD -b450M -f -z 16384 -d /sybase/TDD/sybsystem/master.dat -c /sybase/TDD/ASE-16_0/install/RUN_TDD_BS) is non-zero with error: 2

     

     

    As sybase server could not get started and master device creation failed (due to incorrect config file) we see these connection errors later.

     

    Please correct config file under instance properties and save and retry.

     

    Let us know how it goes.

     

    Thanks

    Piyush

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 5:23 AM

    Correction : Sybase config file on Linux installations will be under <SybaseHome>/ASE Path

     

    So it should be /sybase/TDD/ASE-16_0/TDD.cfg for you.

     

    http://documentation.commvault.com/commvault/v10/article?p=products/sybase/config_basic.htm

     

    Thanks

    Piyush

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 7:27 AM

    Brilliant, thanks - making much more sense and we have some progress now!!

     

    New error:

    Error Code: [71:31]
    Description: Loading database failed :[WARNING: In order to LOAD the master database, the ASE must run in single-user mode. If the master database dump uses multiple volumes, you must execute sp_volchanged on another ASE at LOAD time in order to signal volume changes. Can't open a connection to site 'SYB_BACKUP'. See the error log file in the ASE boot directory. Can't open a connection to site 'SYB_BACKUP'. See the error log file in the ASE boot directory. Could not establish communication with Backup Server 'SYB_BACKUP'. Please make sure that there is an entry in Sysservers for this server, and that the correct server is running. ]
    Source: dc1stddadb01, Process: ClSybAgent


     
    I had a look at the ASE log and it shows "Site 'SYB_BACKUP' not found in interfaces file".

    In the interfaces file we have:

    TDD
    master tcp ether vtddadb 3081
    query tcp ether vtddadb 3081

    TDD_BS
    master tcp ether vtddadb 4982
    query tcp ether vtddadb 4982

    TDD_JSAGENT
    master tcp ether vtddadb 3083
    query tcp ether vtddadb 3083

     
    The CommVault setting for the backup server is  SYB_BACKUP. But should it be TDD_BS perhaps?

    But surely SYB_BACKUP must be correct as the backups work... also when we want to shutdown just the backup server we use "shutdown SYB_BACKUP", not TDD_BS....? 

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 7:46 AM

    Hi Ross,

     

    Looks like as we saved instance properties several times before restore when Master was not loaded fully and didnt have backupserver entry , we are seeing default SYB_BACKUP istead of 'TDD_BS'.

     

    Few points to check:

     

    1. What is the backup server name shown under instance properties? IS that TDD_BS or SYB_BACKUP?

    2. What is the output from isql session  of query " Select * from sysservers"(try connecting using sa , no password as master database is still not loaded)

     

    Do you see srvnetname value "TDD_BS" for SYB_BACKUP like an example below?

     

    1> select srvname, srvnetname from sysservers
    2> go
     srvname
             srvnetname                                                                                                                                                                                                                                                                                                                                                                                                                                                                         
     ------------------------------------------------------------
             ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
     SYB_BACKUP
             cvlt_BS                                                                                                                                                                                                                                                                                                                                                                                                                                                                            
     cvlt
             cvlt                                                                                                                                                                                                                                                    

     

    If not we need to update backupserver srvnetname from "SYB_BACKUP" to "TDD_BS" in sysservers table.

    update master.dbo.sysservers set srvnetname = "<Backup-Server-Name>" where srvname = "SYB_BACKUP"

     

    Check SYB0005 in troubleshooting from below link:

    http://documentation.commvault.com/commvault/v10/article?p=products/sybase/backup_troubleshooting.htm

     

    3. After updating cross verify that backup server shows "TDD_BS" at these three places:

    A. Commvault sybase instance properties in GUI. If not updated please save again.

    B. sybase interface file.

     

    TDD
    master tcp ether vtddadb 3081
    query tcp ether vtddadb 3081

    TDD_BS
    master tcp ether vtddadb 4982
    query tcp ether vtddadb 4982

    C. Sysservers table srvnetname where srvname ="SYB_BACKUP"

     

    Let us know if it resolves the issue.

     

    Thanks

    Piyush

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 7:57 AM

    Ross,

    One more thing addition to below point i added earlier:

    3. After updating cross verify that backup server shows "TDD_BS" at these three places:

    A. Commvault sybase instance properties in GUI. If not updated please save again.

    In case after updating srvnetname for backupserver to TDD_BS in sysservers , if GUI instance still shows SYB_BACKUP and you are not able to save the instance properties to make backupserver "TDD_BS" from sapsa user account.

    Workaround will be try with sa and no password and save properties if you can as currently master database is without any password and not loaded.

    Once properties are saved and you are able to see "TDD_BS" you should change user account back to sapsa user and try restore.

     

    This happened because we changed user account during restore which is not recommended .

     

    Let us know how it goes.

     

    Thanks

    Piyush

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 10:12 AM

    Hi Piyush

    Thanks again. Yes it looks as if somethings gone a little wrong; I see in the sysservers table of another system that srvnetname is correctly set as <SID>_BS; however here (TDD, so should be TDD_BS) I'm getting a value of SYB_BACKUP.

    I have ran the update command as suggested to change this to TDD_BS.

    However, we can't change the backup server to TDD_BS in CommVault. The backup server is selected from a drop down list; only SYB_BACKUP exists in there.

    To 'pick this up' I guess we need to re-connect CommVault to the server by changing the username so that it communicates with the server and updates it perhaps?

    Although I fear if we set it to sa with a blank password it will complain again about a blank password - but we can try.

    The CommVault engineer is unavailable though for the rest of the day now so this will have to wait.

    Thanks for all your help today!

    Regards
    Ross 

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 10:42 AM

    Our other three systems are cofigured in CommVault to use SYB_BACKUP, not their respective TDP_BS, SDD_BS and SDP_BS names.

    I see that in the sysservers tables they all have SYB_BACKUP as the srvname and their <SID>_BS name for srvnetname.

    Perhaps correcting the srvnetname for TDD will suffice and we can leave SYB_BACKUP in CommVault (as this IS the server name; rather than the 'srvnetname')? 

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 11:13 AM

    Hi Ross,

     

    TDD_BS is the actual backupserver and the same name we should see in GUI .  All three places it should match. GUI tries to connect to backup server which is mentioned under instance prop.

    As you said:

    After correcting and updating sysservers entry for backupserver, We can try saving instance properties  using sa user and if it works and correct backupserver is added in instance properties, you can change user account back to sapsa and launch restore with "sybase create devices".

     

    Also other three servers you mentioned,

    Can you do a test using isql if you can connect to TDD_BS or SYB_BACKUP.

    isql64 -Usa -S<SID>_BS

     

    Thanks

    Piyush

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 11:18 AM

    Also while updating and changing user account password, please ignore errors popup and click ok  as it will get saved in csdb even connection errors we see.

     

    Thanks

    Piyush

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 11:27 AM

    Ok thanks, will try that next.

    Also tried with the other servers to connect with isql64 and using SYB_BACKUP doesn't work; using <SID>_BS does work - we can connect.

    Which I guess proves your point that CommVault ALSO needs to use the <SID>_BS name to connect, not SYB_BACKUP.

    What I don't understand though is how the backups have worked/connected; as it's always been set to SYB_BACKUP in all 4 systems, and backups have worked? Restores (of the SID only, this is the first time we have tried to restore master) have also worked with it set up in this way. 

  • Re: Is it possible to set a null password for your DB user?
    Posted: 06-15-2017, 11:34 AM

    Hi Ross,

     

    It would be interesting to see how backup worked on ther instances with SYB_BACKUP as for me it fails.

    We can diagnose that seperatly if we can get ClSybAgent/ClSybBrowseAgent logs after clicking instance properties and saving it.

     

    Also we would be updating our documentation with a note  not to change user account while attempting restore.

     

    Thanks

    Piyush

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2017 Commvault | All Rights Reserved. | Legal | Privacy Policy