Highlighted

Backup Exec

Hello guys,

 i have some questions

We are plan to our backup exec 2010 upgrade to 2015 with High Availabilty.

We prepare new server with differet IP and NAME.The new server should be in HA.and we need to migratev to new server.

So i need know how we migrate the catalog folder in new server??

How we migrate  SQL database to new server???e

 

Corrent setup

Version :2010 R3

Migration server

version : 2015 FP2

catalog migration to new server???

sql database migration to new server??

How we implement HA in Backup exec??

Which link we need to use download the Backup Exec product???

 

2 Solutions

Accepted Solutions
Accepted Solution!

@shaabin - 1) On the old

@shaabin -

1) On the old server, first ensure BE 2010 R3 is patched up with SP4. If it is not, run LiveUpdate or manually download SP4 to update it. Push the update to the remote agents as well.

2) Secondly, stop all BE services including the SQL instance. Copy the Data & Catalog folders.

3) On the new server, install BE 15. Post installation, do NOT launch the console.

4) stop all BE services including the SQL instance. Rename the newly created Data & Catalog folders.

5) Copy the Data & Catalog folders from the old server to the new server.

6) Use this article for manual upgrade via BEMIG - https://www.veritas.com/support/en_US/article.TECH50537

7) Finally, to cluster Backup Exec, have a good read at Chapter 17 of the Admin Guide.

 

@ThomasAG -

Pls open a new thread for your issue. And if you require urgent assistance, then best to log a call with Support. Thanks.

 

View solution in original post

Accepted Solution!

Re: Backup Exec

There are two HA (ish) solutions for BE

1) Is a cluster (which still has a limitation for if the disk array itself fails and you may have to uncluster and recluster when applying updates etc) For some reason we no longer have many customers using this option - possibly because if a backup server on it's own has failed there is usually time to recover as long as no other servers are affected and if you have a disaster big enough to destroy all your servers, then your cluster would be  gone as well. (in other words over complexity for limited useful gain)

2) Is a CASO setup with two Backup Exec servers running deduplication and optimized Deduplication between them - this gives you the same data on two storage devices but also has greater license requirements. Also if the CAS server goes down you would have to run a process to make the Managed server back to stand alone, however apart from this step either server would be able to do a restore if the other has completely failed (including disk storage failure on one server) and you can locate the CAS and managed servers in different buildings (with a fast, reliable, always on link betwen them) which you cannot do with a cluster. Note this does take some setting up to meet all the above points.

 

The other option is of course understand (and test/document) the steps that involve SDR to recover the OS and the couple  of extra steps for recovering Backup Exec itself and not use an HA option at all.

View solution in original post

6 Replies

Re: Backup Exec

Hi,

 

best bet is to upgrade the current server to BE 15, and then migrate. This ensures all the data is already converted and you have nothing further to do in terms of this.

 Before upgrading the current server, stop the BE services and get copies of the Data & Catalogs folders to allow a rollback.

The TN below is for BE 2014, but should be relevant for 2014 but should work for BE 15 as well:

https://www.veritas.com/support/en_US/article.TECH216706

Thanks!

Re: Backup Exec

What is your objective in implementing HA for the media server?

Re: Backup Exec

@craig:No that not possible,the customer need that server as it is.The new server is ready.we install BE15 create new jobs and everything.but custometr need their old catalo and Data(sql db)in new server.

 

 

 

Re: Backup Exec

Hi All

 

I would like to get procedures about restoring the entire mailbox database in exchange 2010 DAG enviroment when mailbox database in production is corrupted . Please help me  guys !!!!!

Accepted Solution!

@shaabin - 1) On the old

@shaabin -

1) On the old server, first ensure BE 2010 R3 is patched up with SP4. If it is not, run LiveUpdate or manually download SP4 to update it. Push the update to the remote agents as well.

2) Secondly, stop all BE services including the SQL instance. Copy the Data & Catalog folders.

3) On the new server, install BE 15. Post installation, do NOT launch the console.

4) stop all BE services including the SQL instance. Rename the newly created Data & Catalog folders.

5) Copy the Data & Catalog folders from the old server to the new server.

6) Use this article for manual upgrade via BEMIG - https://www.veritas.com/support/en_US/article.TECH50537

7) Finally, to cluster Backup Exec, have a good read at Chapter 17 of the Admin Guide.

 

@ThomasAG -

Pls open a new thread for your issue. And if you require urgent assistance, then best to log a call with Support. Thanks.

 

View solution in original post

Accepted Solution!

Re: Backup Exec

There are two HA (ish) solutions for BE

1) Is a cluster (which still has a limitation for if the disk array itself fails and you may have to uncluster and recluster when applying updates etc) For some reason we no longer have many customers using this option - possibly because if a backup server on it's own has failed there is usually time to recover as long as no other servers are affected and if you have a disaster big enough to destroy all your servers, then your cluster would be  gone as well. (in other words over complexity for limited useful gain)

2) Is a CASO setup with two Backup Exec servers running deduplication and optimized Deduplication between them - this gives you the same data on two storage devices but also has greater license requirements. Also if the CAS server goes down you would have to run a process to make the Managed server back to stand alone, however apart from this step either server would be able to do a restore if the other has completely failed (including disk storage failure on one server) and you can locate the CAS and managed servers in different buildings (with a fast, reliable, always on link betwen them) which you cannot do with a cluster. Note this does take some setting up to meet all the above points.

 

The other option is of course understand (and test/document) the steps that involve SDR to recover the OS and the couple  of extra steps for recovering Backup Exec itself and not use an HA option at all.

View solution in original post