11-22-2015 04:12 PM
People,
At the moment my Backup Exec 15 database is running on
Microsoft SQL Server 2008 R2 Express Edition (32 bit) (SP2) - 10.50.4000.0
which I'd like to migrate it into Microsoft SQL Server 2012 Standard Edition (64-bit) (SP2) - 11.0.5343.0
so how to do that safely without leaving any issue to the current backup job & SQL DB maintenance task if there is any ?
Thanks
Solved! Go to Solution.
11-22-2015 05:51 PM
See this document
http://www.veritas.com/docs/000029027
Make sure that the BEDB has its own instance because there would be times when the BEDB needs to be restarted and sharing an instance between the BEDB with some other production databases may hinder production.
Also, be aware that using a non-default BEDB means that you have to take care of the maintenance of the BEDB SQL instance.
With the new BEDB, how do you plan to recover the media server, in case it is wiped out?
11-22-2015 08:19 PM
As I said, the recommendation is for a dedicated instance for the BEDB. Otherwise, when you need to restart the BEDB, you would also need to restart the other databases in that instance.
If you don't know how to recover a media server with a non-default BEDB, why are you embarking on this route?
11-22-2015 10:21 PM
John: To be honest there are very few environments large enough to require a dedicated SQL Server. It has its own set of complications running this. SQL Express is really good-enough for the purposes of running the BEDB.
Thanks!
11-22-2015 11:29 PM
Would recommend a read at this blog as well - https://www-secure.symantec.com/connect/blogs/using-custom-sql-instance-backup-exec-installs
11-24-2015 10:02 PM
11-25-2015 06:23 AM
Agree with pkh if you are having problems with disk space on C: then the BEDB is negligible
However at the end of the day your real problem is disk space so your better options are
1) Somehow increase the size of the C: drive.
2) Consider re-installing Backup Exec and it's SQL express intance onto a different volume on the same server (this is good practice for performance etc too) You would need to take steps to protect the existing database, catalog and database encryption key so that you can recover them after the re-install
3) Consider moving the Backup Exec Catalogs folder (as this is likely to be much larger then your SQL express footprint) assuming the catalogs folder is on the C: drive currently.
11-22-2015 05:51 PM
See this document
http://www.veritas.com/docs/000029027
Make sure that the BEDB has its own instance because there would be times when the BEDB needs to be restarted and sharing an instance between the BEDB with some other production databases may hinder production.
Also, be aware that using a non-default BEDB means that you have to take care of the maintenance of the BEDB SQL instance.
With the new BEDB, how do you plan to recover the media server, in case it is wiped out?
11-22-2015 08:12 PM
@Pkh,
Well the SQL Server doesn't have a specialized / dedicated DB Instance, os it is pretty much the standard MSSQLSERVER (Default).
Would that be enough ?
Not sure how to do that ?
11-22-2015 08:19 PM
As I said, the recommendation is for a dedicated instance for the BEDB. Otherwise, when you need to restart the BEDB, you would also need to restart the other databases in that instance.
If you don't know how to recover a media server with a non-default BEDB, why are you embarking on this route?
11-22-2015 10:21 PM
John: To be honest there are very few environments large enough to require a dedicated SQL Server. It has its own set of complications running this. SQL Express is really good-enough for the purposes of running the BEDB.
Thanks!
11-22-2015 11:29 PM
Would recommend a read at this blog as well - https://www-secure.symantec.com/connect/blogs/using-custom-sql-instance-backup-exec-installs
11-24-2015 08:33 PM
Hi All,
The reason is because the C: drive is running very low under 4 GB and decreasing, this is due to the Windows Update directory getting bigger (WinSXS) and I also found out that this SQL Express edition running BEDB is on C: drive as well.
hence I'd like to move it away from this server.
11-24-2015 10:02 PM
11-25-2015 06:23 AM
Agree with pkh if you are having problems with disk space on C: then the BEDB is negligible
However at the end of the day your real problem is disk space so your better options are
1) Somehow increase the size of the C: drive.
2) Consider re-installing Backup Exec and it's SQL express intance onto a different volume on the same server (this is good practice for performance etc too) You would need to take steps to protect the existing database, catalog and database encryption key so that you can recover them after the re-install
3) Consider moving the Backup Exec Catalogs folder (as this is likely to be much larger then your SQL express footprint) assuming the catalogs folder is on the C: drive currently.
12-14-2015 08:13 PM
Thanks All for the assistance.
With the new BEDB, how do you plan to recover the media server, in case it is wiped out?