Migration Backup Exec

[Cristoforo Kanoy]

Nowarnings during the upgrade or in the migration report. I saw the warning on another backup server so expected to see it on this one, but I think it noticed I was having a good day and didn't want to give me bad news.

Do I just stop services and replace the Data and Catalog folders with the backup folders created by the upgrade?

Or is it better to uninstall, reinstall, copy folders at that point and then run bemig?

I was mistaken when I said it has backed up folders, I was thinking it has done Catalog and Data folders, but it was just the mdf and mdf files of the database.

So I beleive my best option for reverting to previous version is to restore from my full backup to v16 and upgrade to 20.3 from there.

I'm doing overall upgrade planning on our infrastructure and saw SQL Server 2014 SP3 will get out of mainstream support in july 2019 identified which systems still run this version, Backup Exec server being one of them. Even if the extended maintenance support continues, MS will definitely limit their efforts for 2014 in favour of 2016 and newer. Thus I'd like to get all our DB instances upgraded in time - where possible to the same versions on the whole infastructure so that we have to keep an eye on less software version to keep patched and maintained.

The BE 20.3 admin guide mentions SQL Server 2014 Express SP2 as minmum requirement, however I haven't found an indication what newer versions of SQL Server (Express) are supported for the BKUPEXEC instance.

Ideally I'd like to upgrade to SQL Server 2017, then again if Veritas doesn't support new SQL Server for the BKUPEXEC instance it wouldn't be worth the effort. Hence my question about what versions are actually supported by Veritas in this case - and where I can find about.

Refer Backup Exec software compatibility list . Check the backup exec database repository section under Backup Exec Feature specific compatibility. This lists all supported SQL version on which BE can host its database.

This week our backup server had to be replaced. So we installed the new server. Installed Backup EXEC 12.5 on the new server. But I want on the new server al my jobs, policies, selection lists and catalogs. After some google search I had found all the info I need to do this.

2. Upgrade your old backup EXEC version to the latest version. If you are upgrading from 9.X first upgrade to 10.X and then upgrade to the latest version. On SERVER01 and SERVER02 should run the same BACKUP EXEC version. Also run LiveUpdate to download the latest hotfix and service packs.

10. Open a command prompt. Run the command C:\Program Files\Symantec\Backup Exec\bemig.exe. This may take some time to complete so wait until it returns to a command prompt. This will migrate all data.

Hi Daniel,

Thank you for putting this guide together. I just successfully migrated from Windows 2003 R2 to Windows 2008 R2 with Backup Exec 2010 R2 using the guide. I had to manually add in the Upgrade and Upgrade Version key in the registry and had to run BEUtility.exe to import the Database and it all worked like a charm. All the service accounts were brought across and all the history. Talk about a painless upgrade!

I am trying the same thing, migrating from W2K3 Server with BE v12 going to W2K8 R2 BE v 2101 R2, it seems to migrate the catalogues but not the databases? I am also going from 32bit to 64bit. Was there any other steps you had to do?

Can anyone tell me if this works if with Storage Option installed? I am getting error after the Copy Database when the services attempt to restart. Device and Media Service terminated with the following error %%536837819

Hi Daniel,

The Backup exec 2012 was sucessfully migrating the catalog but the devices were not coming online in my setup.

Can you suggest me a way to troubleshoot it

I tried to migrate data from Win 2K3 sserver to another 2K3 server

Complex infrastructures and the changing needs of IT require flexible and dynamic solutions that are not just built to last, but also built to change.

Veritas Backup Exec provides recovery for your entire Virtual and Physical Infrastructure and now, with the new Cloud Connector supports migration of backup images to the cloud while retaining the flexibility of Backup to Disk and Tape.

As I noticed this I logged on that server and found ot that the associated socket is owned by beserver.exe which is the RPC Server of Backup exec. The strange thing is that the targeted address has never been backed up by that host and did not even belong to our company.

I know the administrator of that network (its a university network) and he allowed me to scan that host. As it showed the device seems to be a phone. The SIP Port is open. Based on the MAC its a Samsung device. Port 135 is not even open.

To ensure that this is not based on a DNS error I did a lookup of all servers backed up by Backup Exec but none of that servers did resolve to this external address. I looked through the firewall logs and this device has never been a part of our network.

Try to check for database error (see below the screenshot on how to do it) or remove backupexec and re-install it. Seem a old device maybe selected to do a backup for testing, but where never removed and now no longer listed (as you don't see it)

To give an actual example. My backupexec on a customer was using a remote site as a media server, but it was not even selected, nor it showed in backupexec. I removed the backupexec instance at the remote site, but the main backupexec was sending data there anyway. I had to fully reinstall to remove any trace of that old server.

Progent's Online Expertise for Popular Backup and Recovery Products

Backing up is critical at any level of computing, and dozens of backup/recovery technologies and products are in use to address this need. Solutions can be as simple as the tar and gzip utilities in the Linux/UNIX world or as comprehensive as Microsoft Data Protection Manager for Windows environments. Unfortunately, many legacy solutions are more expensive to maintain and operate than to replace, and many backup products adopted without careful planning fail to deliver the availability and protection a business really needs. Progent's extensive team of IT experts can provide affordable online support to help you manage or deploy popular backup/restore products for all major operating systems and any network topology.

In addition to offering small and mid-size companies ProSight Data Protection Services for low-cost and fully managed cloud backup, Progent can also provide online access to IT engineers with expertise in a wide range of products and technologies for backing up Windows, Apple, and Linux/UNIX servers and desktops as well as laptops, iPads, and smartphones. Progent can help you design, enhance, or troubleshoot backup systems for a variety of architectures including local, edge to datacenter, across premises, cloud-based, or hybrid. In addition, Progent's certified VMware consultants, Hyper-V experts, and Citrix specialists can show you how to follow leading practices to deploy virtualization technology for continuous transparent backup and ultra-fast recovery. Progent can also help you migrate from a legacy backup solution to a state-of-the-art system that can save you money while reducing or eliminating scheduled downtime and accelerating recovery.

Best Practices for Setting Up and Managing a Modern Backup Environment

The spread of ransomware has rewritten the rules for creating a backup solution that can recover fully and promptly from a ransomware breach. A common strategy of attackers is to attempt to locate and destroy backups in order to increase their chances of getting the ransom demand paid. Valid offline or off-site cloud is the only "bullet proof" solution against ransomware attacks. Progent can help you design, implement, and test a backup/recovery solution driven by best practices to deal with today's threat landscape. Progent offers expertise in these vital areas: Develop a backup strategy to ensure that all critical data is backed up at least weekly and is inaccessible online. Review the backup strategy and determine how to implement immutability, air gapping, and offsite backup. Lock down the backup account so it can be used only during the backup windows and not on other endpoints. Enable 2FA on backup endpoints Review the backup infrastructure and design a strategy to avoid the volume being broken. One touch or manual imaging on each desktop system can be costly and slow in a disaster environment. Best practices call for an imaging system for company endpoints that is updated on a regular schedule and also on an as-needed basis. Cloud backups should be separated from the client environment impact and should be reviewed in detail on possible recovery times and methods of obtaining the data. Often the cloud backups are the only non-impacted recovery option. Unfortunately, data transfer speeds or shipment of data in some physical format can take a prohibitively long time, resulting in excessive delays in the recovery process. Backup Products Supported by Progent

Progent supports a variety of modern and legacy backup platforms and can help you migrate to current-generation products or deploy contemporary backup systems based on leading practices. Backup products for which Progent can provide consulting and troubleshooting support include:

Barracuda Backup incorporates technology developed by Intronis, a company Barracuda acquired, to provide a flexible backup solution for on-premises, virtual, cloud-hosted, and Software-as-a-Service (SaaS) environments. For disaster recovery, Barracuda supports data replication to the Barracuda Cloud, Amazon Web Services (AWS), or any private site you designate. Progent is a Barracuda partner and can help you design, deploy or troubleshoot a Barracuda backup environment, or Progent can provide end-to-end managed services so you can outsource your entire backup and disaster recovery solution. For more information about Progent's support services for Barracuda Backup, see Barracuda Backup and disaster recovery consulting.

3a8082e126