Skip to main content

How to upgrade Symantec Backup Exec 2010 to 2012?

By

Last one month ago, I've got one experience in upgrading of Symantec backup exec 2010 to 2012.
I'd like to share my experience of it.

Let's do question what we will need before do the upgrading process,

1) Before upgrade it , what should I do? (Backup what?)

2) will the existing setting can directly import to 2012?

3) If fail, can I roll back to old version?

4) After download and extract SBE 2012, can I directly run it & auto upgrade to 2012?

5) Remote agent, CPS (Continuous Protection Server) console also need to upgrade to lastest version?


Here is the answer for above question,

1) Before upgrading stop SQL server BKUPEXEC service and make a copy of the DATA and

    CATALOGS folder. These folders are located at X:\Program Files\Symantec\Backup Exec

2) When you perform an Inplace upgrade, all the jobs, policies, media sets and other settings are

    retained and imported into the new version.

3) If it fails, it will roll back to older version automatically. We also can roll back to older version by the help of backup DATA and CATALOGS

4) We may run the browser.exe which will initiate the upgrade process.

5) You need to manually update the remote agents either through the BE console or by copying installables on the remote server. But CPS is no more supported in BE2012.


OK... Let's do upgrading process,

1) Do update the latest update patches in SBE 2012. Stop SQL server BKUPEXEC service on the media server

2) Run the browser.exe from Extracted SBE 2012 and follow the instruction.

3) Do update the latest update patches after upgrading process done.

4) Reboot the server

5) Update the remote agents.

Symantec Backup Exec 2012 upgradeing completely done.

Note: You need to register the license file/serial number of Maintenance Contract from License Certificate that deliver from Symantec before do the upgrading process to get license file/serial number for Core software and remote agent.
         If not, your SBE 2012 will show "Trial Version". But that one can fix after registered the Maintenance Contract license on Symantec License Portal and grab license file/serial number that you purchase from Symantec.
         Then re-install those license via SBE Console License Option.


If you still not clear my post, you can watch the Video at below link,

http://www.symantec.com/connect/videos/upgrading-be-2010-r3-be-2012


May you all be happy.
( Be knowledgeable, pass it on then)







Labels:

Comments

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

By
I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...
Post a Comment
Read more

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...
144 comments
Read more

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

By
Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Soc...
7 comments
Read more