#1 Global Leader in Data Resilience

How to Re-Initialize Veeam Backup for Salesforce Configuration Database Connection

KB ID: 4370
Product: Veeam Backup for Salesforce | 2.0 | 2.1 | 3.0
Published: 2022-10-27
Last Modified: 2024-09-18
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Purpose

This article documents how to change which account Veeam Backup for Salesforce uses to connect to its configuration database.

Solution

Scenario 1: Change Database Credentials When Existing Connection is Functioning

This scenario assumes the current connection to the database is valid and that you are simply updating user credentials.

  1. Create a new DB username/password in PostgreSQL. 
  2. Grant that user permissions for the configuration database and schema.
  3. Within Veeam Backup for Salesforce, click Configuration, switch to the Salesforce section, then switch to the Database tab. 
  4. In the top-right of the Database tab, click the Configuration Database button.
  5. Provide the new database username and password, and then click save.
    The new user will be saved, and the connection will be re-established.

Scenario 2: Change Database Credentials When Existing Connection Is Unavailable

This scenario assumes there is no access to the Veeam Backup for Salesforce interface since the database connection is unavailable.

Note: Steps 1 and 4 are version-specific. All other steps are the same between versions of Veeam Backup for Salesforce.

  1. SSH into the server and navigate to:
    • For Veeam Backup for Salesforce v2:
      /opt/vbsf/vbsf-backend/
      
    • For Veeam Backup for Salesforce v3
      /opt/vbsf/vbsf-backend/config
      
  2. Delete the following files:
    • local.mv.db
    • local.trace.db
    • persistence-db.properties
    • init.properties
  3. Restart the backend service.
sudo systemctl restart vbsf-backend
  1. Get the access token:
For Veeam Backup for Salesforce v2
sudo cat /opt/vbsf/vbsf-backend/init.properties | grep firstuser.token
For Veeam Backup for Salesforce v3
sudo cat /opt/vbsf/vbsf-backend/config/init.properties | grep admin.password.set.token | cut -d'=' -f2 
  1. In a browser, open the Veeam Backup for Salesforce URL with the access token from above.

    Example:

https://<vbsf_server_address>/?access_token=<access token>
  1. Follow the wizard and create a local administrator user password.
  2. On the Connect to PostgreSQL step, choose "Existing Installation" and provide the connection credentials.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.