01-14-2016 03:54 AM
Trying BE 2015 on server 2012 R2 and it keeps failing when trying to attach to the SQL server 2014. Here is the exact error:
The install does notice the SQL cluster and i have tried to enter the cluster/computer name\instance and the install locks up and i must kill the setup process. The drive the SQL DB resides on is attached to a server via SaS cable and other DB's have no problem accessing the drive/DB's. I can browse to that drive from the server where BE 2015 is being installed. Why can't BE 2015 install? I don't see SQL 2014 listed as "supported".........
Solved! Go to Solution.
01-14-2016 04:27 AM
Whilst this should not cause a failure - are you trying to put the Backup Exec database into a SQL instance that is shared with production databases for other applications as if you are this is not a recommended setup (primarily due to extra complexity in the event of recovery from a disaster)
Recommenced setup is always put Backup Exec in an instance on it's own and for simplicity on BE servers that are not busy (so not managing a huge number of josb and backup sets) use the SQL Express instance that we will install for you.
For very busy servers or CASO setups with a large managed environment we do recommend that full SQL is used (but still a unique instance)
Also if not letting BE use the express instance we install for you then it is recommended to NOT call the instance you are using BKUPEXEC as this can cause problems for future upgrades.
Some more info here:
https://www.veritas.com/community/blogs/using-custom-sql-instance-backup-exec-installs
01-24-2016 10:26 PM
No, no support on the trial version unless you have active maintenance currently.
If you can trash and recreate the server, then do so, otherwise just install the SQL Express instance. It works incredibly well.
Thanks!
01-14-2016 04:27 AM
Whilst this should not cause a failure - are you trying to put the Backup Exec database into a SQL instance that is shared with production databases for other applications as if you are this is not a recommended setup (primarily due to extra complexity in the event of recovery from a disaster)
Recommenced setup is always put Backup Exec in an instance on it's own and for simplicity on BE servers that are not busy (so not managing a huge number of josb and backup sets) use the SQL Express instance that we will install for you.
For very busy servers or CASO setups with a large managed environment we do recommend that full SQL is used (but still a unique instance)
Also if not letting BE use the express instance we install for you then it is recommended to NOT call the instance you are using BKUPEXEC as this can cause problems for future upgrades.
Some more info here:
https://www.veritas.com/community/blogs/using-custom-sql-instance-backup-exec-installs
01-14-2016 05:52 AM
To answer your question, yes i am trying to put the BE DB in a shared SQL instance. I will create a new instance for BE only.
From the link you shared, i don't see a problem with using the full SQL install. We don't use the software firewall, the permissions can be set on the folders, SQL is patched with Windows updates, etc. Any idea as to why this error 1606?
01-14-2016 06:37 AM
01-14-2016 07:26 AM
The reason to not use a full SQL instance is only why do you need to if the express edition (on the same server as BE) can do the job.
Also as per pkh comment (probably below because of reply ordering) unless you have a really good reason to install in a non-default instance (so very busy Backup Exec server) because the DR process for the Backup Exec server itself is more complicated with remote SQL it is stil better to stay with local default express instance.
01-14-2016 11:27 AM
pkh, my thought for recovering the media server is we always make a baseline install of all the servers then copy the vhdx somewhere else so all we have to do is make a new VM uisng the copied vhdx. Wouldn't that work (it has worked for other servers)?
01-14-2016 04:33 PM
01-14-2016 04:46 PM
Well, i have but not with BE and the first thing i think of are the backup sets (i might be calling it the wrong thing). How will BE know of all the backups after the baseline vhdx is made? Are you saying that when using a custom SQL instance (not the msde) there is no way to recover a media server should it fail?
I should also restate that the SQL servers are in a MS failover cluster and i wonder if this is why we are getting that error? Do we need to run the cluster wizard from BE (maybe that does not exist now)?
01-15-2016 02:14 PM
Here is what the install log says:
01-18-2016 05:26 AM
01-19-2016 12:49 PM
01-19-2016 01:07 PM
If you're trying to install Backup Exec on a cluster, have you seen the TN below?
https://www.veritas.com/support/en_US/article.TECH64591
THanks!
01-19-2016 04:46 PM
No. This new website sometimes marks an answer as a solution when I am scrolling through the discussion.
01-19-2016 05:40 PM
I'm not installing BE on a cluster but BE DB to a cluster of sql 2014 servers.
01-22-2016 07:26 AM
Any with any ideas? Can you get support with a trial version?
01-24-2016 10:26 PM
No, no support on the trial version unless you have active maintenance currently.
If you can trash and recreate the server, then do so, otherwise just install the SQL Express instance. It works incredibly well.
Thanks!