-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when installing Veeam Backup & Replication v12 #43
Comments
Thanks for including a copy of your playbook. As shown in the playbook samples, your This is because version 12 installs a local PostgreSQL instance instead of SQL Express. The default username for PosgreSQL is postgres. If this does not resolve your issue, feel free to reopen. |
Thank you for your help |
I am seeing this error even though I am specifying
|
@kbreit-insight You're most likely experiencing a different error. Please check the log specified in the error for more details. Using the default folder it's: Looking at your playbook, your For example:
Please open a new issue if you require further assistance. |
Describe the bug
When I run the playbook using roles from VeeamHub and used playbook with ISO download and installing community version of veeam and with out ISO download and installing community edition of Veeam Backup and Replication
To Reproduce
Steps to reproduce the behavior:
Installled roles - VeeamHub from ansible-galaxy
used the playbook from github
hosts: all
tasks:
name: Copy Veeam ISO file to Windows
copy:
src: "/XXXX/VeeamBackup&Replication_12.0.0.1420_20230209.iso"
dest: "C:\Downloads\"
include_role:
name: veeamhub.veeam.veeam_vas
tasks_from: vbr_install
vars:
version: "12"
destination: "C:\Downloads\"
destination_iso_file: "VeeamBackup&Replication_12.0.0.1420_20230209.iso"
sql_install_username: "sql_install"
sql_install_password: "PassW0rd!"
sql_service_username: "svc_sql"
sql_service_password: "PassW0rd!"
sql_username: "sa"
sql_password: "PassW0rd!"
Screenshots
Operating system used for Veeam Installation
Could anyone solve this issue
The text was updated successfully, but these errors were encountered: