01-22-2016 03:09 AM
Hey,
i would like to change the location for the BEDB from one SQL to another...
I have a BE 15 Server (only BE installed) and a seperate SQL Server 2012 (both on W2k12)
I did a backup of the BEDB, transfer it to another SQL Server and restored it.
Now i am using BEUtility to change the Database Location
Trying to access the new Instance
and get an error message:
FAILED TO ACCESS THE REGISTRY KEY OF THE SELECTED SERVER 'SERVERNAMEXXX" to get the SQL SERVER VERSION NUMBER.
I read in different cases, that i have to add something to HKLM in Registry in the Symantec folder, but there is no Symantec installed on SERVERNAMEXXX... i only want to change the location of the BEDB from one SQL to another SQL Server instance...
Thanks! Cheers,
Solved! Go to Solution.
01-22-2016 05:28 PM
With your present configuration, have you thought about how to recover your media server in the event that your data centre got wiped out and you have to start afresh?
01-25-2016 01:19 AM
SQL Express locally installed works very well and is recommended by Veritas.
Thanks!
01-25-2016 01:51 AM
Any specific reason for not using the default SQL instance & choosing a remote SQL instance instead ?
Would recommend a read at this blog as well - https://www.veritas.com/community/blogs/using-custom-sql-instance-backup-exec-installs?cid=11456121#comment-11456121
If there is a definite business requirement for moving over the SQL instance to a remote server, please check/advise the following -
1) Do not keep the new instance name as BKUPEXEC
2) Are remote connection protocols such as Named Pipes, TCP/IP enabled at the remote SQL server ?
3) Does the BE logon account have full permissions on the SQL registry hive at the remote SQL server ?
01-22-2016 08:41 AM
Follow the TN below and see if this helps you:
https://www.veritas.com/support/en_US/article.TECH37752
Also, it's recommended to use SQL Express that BE ships with to get the BEDB installed on.
Thanks!
01-22-2016 05:28 PM
With your present configuration, have you thought about how to recover your media server in the event that your data centre got wiped out and you have to start afresh?
01-24-2016 11:58 PM
01-25-2016 01:19 AM
SQL Express locally installed works very well and is recommended by Veritas.
Thanks!
01-25-2016 01:44 AM
i dont see the idea behind that...
SQL Express installing on the BE Server? why should it solve my problem?
he is searching for a BE instance on the seperate SQL server...
not for another SQL instance...
01-25-2016 01:51 AM
Any specific reason for not using the default SQL instance & choosing a remote SQL instance instead ?
Would recommend a read at this blog as well - https://www.veritas.com/community/blogs/using-custom-sql-instance-backup-exec-installs?cid=11456121#comment-11456121
If there is a definite business requirement for moving over the SQL instance to a remote server, please check/advise the following -
1) Do not keep the new instance name as BKUPEXEC
2) Are remote connection protocols such as Named Pipes, TCP/IP enabled at the remote SQL server ?
3) Does the BE logon account have full permissions on the SQL registry hive at the remote SQL server ?