Skip to main content

How to upgrade Symantec Backup Exec 2010 to 2012?

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,

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


Popular posts from this blog

Fortigate guide for Begineer - 6

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

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f