• Posted in: Home
• 42
• Author: admin

How to migrate move Backup Exec from one system to another with the same version of BE, Windows and same or different computer names. Problem. How to migrate move Backup Exec from one system to another with the same version of BE, Windows and same or different computer names. Solution. Instructions for moving an installation of Backup Exec. The Backup Exec move process consists of five sections. I.  Prepare the current Backup Exec installation on the source computer system. Command Reference Guide for Cisco Prime Infrastructure 3. Command Reference. Your favorite technology company, Google, is working on an upcoming feature that could put the kibosh on autoplaying videos for good. Soon youll be able to silence. Error severity description 18002 20 Exception happened when running extended stored procedure. SQL Server is terminating. SmartPCFixer is a fully featured and easytouse system optimization suite. With it, you can clean windows registry, remove cache files, fix errors, defrag disk. Hi All, Does anyone have script to Remove Sophos EndPoint 10. I have tried the script under httpscommunity. II.  Move Backup Exec data to a temporary storage location. III. Install Backup Exec on the new Backup Exec target media server. IV. Move the Backup Exec data from the temporary storage location to the new target Backup Exec media server. V.  Verify that the new Backup Exec installation matches the original Backup Exec installation. Important Note Do not remove Backup Exec from the original computer until the migration of data and media to the new Backup Exec media server is complete. It must be verified that the new Backup Exec installation matches the original installation. How To Manually Uninstall Backup Exec 2012 Remote Agent' title='How To Manually Uninstall Backup Exec 2012 Remote Agent' />I. Prepare the current Backup Exec installation. In order to move Backup Exec from one computer to another, the following preparation must be performed on the original Backup Exec media server. How To Manually Uninstall Backup Exec 2012 Remote Agent' title='How To Manually Uninstall Backup Exec 2012 Remote Agent' />Backup Exec Version and Revision Number Write down the Backup Exec version and revision number listed on the Backup Exec. Help About Veritas Backup Exec for Windows Servers menu. Update Backup Exec Software Install all the Backup Exec software updates hotfixes and service packs available for the Backup Exec version and revision currently installed. Software updates can be obtained from either the Backup Exec Technical Support site or Veritas Live. Update. 3.  Installed Backup Exec Options, License Keys, and Installation Path Write down a list of the installed Backup Exec options, license keys and the installation path from the existing Backup Exec installation. To obtain this information, follow these steps. Open Backup Exec. Select. Tools Install Options and License Keys on this Media Server from the Backup Exec menu. After the license keys are obtained, precede through the install screens to obtain the install path. Once this information is obtained, the install can be canceled. Note  Backup Exec keeps a record of the Backup Exec license keys currently installed in a file named BESERNUM. XML. This file is located under Documents and SettingsAll UsersApplication DataveritasBackup Exec. The license keys listed in this file can be imported. Figure 1 during the installation on the new Backup Exec media server instead of manually entering the license keys. To use this file during the installation of the new Backup Exec media server, save the file to location on the new Backup Exec media server so it can be retrieved when needed. DB2 10. 5 APAR Fix list contains list of APARs shipped for each fix pack in DB2 Version 10. Linux, UNIX and Windows products. The Severity column value of 1 is. Back in the SCOM 2007 days there was a nice SCOM specific utility called MOMClean. How to migrate move Backup Exec from one system to another with the same version of BE, Windows and same or different computer names. Article ID 100020224. I think the best way is to uninstall the mom agent from the client machine first take a look here Uninstall Agent from Windowsbased Computers. Post upgrade behavior and new feature changes that impact the migration testingHere is a link to the New Features Matrix, at a glance httpinfocenter. BE-Remote-Agent.jpg' alt='How To Manually Uninstall Backup Exec 2012 Remote Agent' title='How To Manually Uninstall Backup Exec 2012 Remote Agent' />Identify backup to disk folder locations Write down the path of all backup to disk folders. To obtain this information, follow these steps. Open Backup Exec. Select the. c. Highlight Backup to Disk Folders, right click and select properties. Note location of B2. D folder see figure 2Figure 2 Backup to Disk folder location. II. Move Backup Exec data to a temporary location. Perform the following steps on the original Backup Exec media server. Note If the server in question that is being moved is a CAS server, then prior to shutting down the services ensure that all of the Backup Exec services for each Managed Media Server that communicates with the CAS are shut down as well. Stop all Backup Exec and DLO if installed services Using the Windows Services applet stop the following Backup Exec services Figure 3 and Figure 4. Backup Exec Agent Browser. Backup Exec Device and Media Service. Backup Exec DLO Administration Service only if DLO is installedBackup Exec DLO Maintenance Service only if DLO is installedBackup Exec Job Engine. Backup Exec Remote Agent for Windows Servers. Backup Exec Server. Stop the Backup Exec SQL Server service a separate DLO Instance will also exist with 1. SQL Server BKUPEXEC This is a SQL Express instance. Stop this instance if it is the instance that the Backup Exec BEDB and DLO BEDLO databases are using. SQL Server MSSQLSERVER This is SQL Server instance local or remote. This is a default SQL instance. This can be a SQL 2. SQL 2. 00. 5, or SQL 2. Stop this instance if it is the instance that the Backup Exec BEDB and DLO BEDLO databases are using. SQL Server SQL2. ONE This is a SQL Server named instance local or remote. This can be a SQL 2. SQL 2. 00. 5, or SQL 2. Stop this instance if it is the instance that the Backup Exec BEDB and DLO BEDLO databases are using. Figure 3 Backup Exec and DLO Services. Figure 4 SQL Service where Backup Exec and DLO databases are installed. Copy Files Using Windows Explorer, copy the following Backup Exec directories files to a temporary location keeping the directories separate. C Program FilesveritasBackup ExecData. IMPORTANT NOTE Do NOT copy the msgq. Figure 5Figure 5 BECASO message queue files. C Program FilesveritasBackup ExecCatalogs. Note If this is a CAS server, make sure to copy over the Catalog folders for the Managed Media Servers as well. These should all be listed under the Catalogs folder. C Program FilesveritasBackup ExecIDR if presentC Program FilesveritasBackup ExecReportsSaved. Backup to Disk folders as mentioned in section I step 4 above if createdNote The only files that must be copied over are the B2. D. bak files. These are the actual media. Figure 6Figure 6 Backup to Disk Media. Important Note  At this point, if the source computer name is the same as the target computer name then turn off the source 3. The domainworkgroup information should also match. III. Installing Backup Exec on the new Backup Exec media server. Perform the following steps on the new Backup Exec media server. Install Backup Exec Install the same version and revision of Backup Exec that is installed on the original Backup Exec media server. If moving to a 6. Backup Exec installation CD instead of the 3. CD. Note  When prompted for Backup Exec license keys, enter the Backup Exec license keys from the original Backup Exec media server. If using the Backup Exec license keys file BESERNUM. XML to enter the license keys, select the. Import button. see Figure 7 and point to the location of the saved license key file. Figure 7 Import License Keys from Source System. Note  When prompted for the installation path, use the same path as the original Backup Exec media server. For example, if the path C Program FilesveritasBackup Exec was used in previous installation, then use the same path. Note The SQL install path can be changed. If the Backup Exec BEDB and DLO BEDLO databases were installed to a SQL Express instance, the databases can be moved to another non SQL Express instance. The database files can be moved to any SQL 2. SQL i. e. SQL 2. SQL 2. SQL Server files cannot be moved to a SQL Express instance. Reboot Restart the computer do not open Backup Exec after rebooting. Install Updates Install all the Backup Exec software updates hotfixes and service packs available for the Backup Exec version and revision currently installed. Software updates can be obtained from either the Backup Exec Technical Support site  or Veritas Live. Update. 4. Reboot Restart the computer do not open Backup Exec after rebooting. VMware v. Center Converter Standalone Release Notes. VMware v. Center Converter Standalone 6. May 2. 01. 5 Build 2. Check periodically for additions and updates to these release notes. Whats in the Release Notes. These release notes cover the following topics. Introduction to Converter Standalone. VMware v. Center Converter Standalone provides an easy to use solution to automate the process of creating VMware virtual machines from physical machines running Windows and Linux, other virtual machine formats, and third party image formats. Through an intuitive wizard driven interface and a centralized management console, Converter Standalone can quickly and reliably convert multiple local and remote physical machines without any disruptions or downtime. Download Samplitude 9 Professional Full'>Download Samplitude 9 Professional Full. Benefits. Convert physical machines running Windows or Linux operating systems to VMware virtual machines quickly and without any disruption or downtime. Convert third party image or virtual machine formats such as Parallels Desktop, Symantec Backup Exec System Recovery, Norton Ghost, Acronis, Storage. Craft, Microsoft Virtual Server or Virtual PC, and Microsoft Hyper V Server virtual machines to VMware virtual machines. Enable centralized management of remote conversions of multiple physical servers or virtual machines simultaneously. Ensure conversion reliability through quiesced snapshots of the guest operating system on the source machine before data migration. Enable non disruptive conversions through hot cloning, with no source server downtime or reboot. Top of Page. Whats New. The VMware v. Center Converter Standalone 6. Support for virtual machine hardware version 1. Compatibility with v. Sphere 6. 0 and Workstation 1. Support for additional guest operating systems Red Hat Enterprise Linux 7, Ubuntu 1. Cent. OS 6 7, Windows Server 2. R2, Windows 8. 1. Support of pure IPv. Proxy mode. File level cloning for volumes with Re. FS file system. Support for XFS file system. Support for predictable network interface names. Top of Page. VMware v. Center Converter Standalone 6. Support Notice. VMware v. Center Converter Standalone 6. This capability will be discontinued in the next release. If you use this capability, you should start planning your transition. For the full list of the third party backup images and virtual machines see Interoperability. Top of Page. Installation Notes. You can download, install, and run VMware v. Center Converter Standalone in English only. Users with limited rights cannot install Converter Standalone on Windows. You must log in as an administrator to install Converter Standalone. Top of Page. Platforms. You can install VMware Converter Standalone 6. Windows Server 2. R2 SP2 3. 2 bit and 6. Windows Vista SP23. Windows Server 2. SP2 3. 2 bit and 6. Windows Server 2. R2 6. 4 bitWindows 7 3. Windows 8 3. 2 bit and 6. Windows 8. 1 3. 2 bit and 6. Windows Server 2. Windows Server 2. R2 6. 4 bitTop of Page. Interoperability. Converter Standalone 6. Physical machine running an operating system noted in Supported Guest Operating Systems. VMware Desktop products. Workstation 1. 0. Fusion 6. x and 7. Player 6. x and 7. VMware v. Center virtual machines. Sphere 6. 0v. Sphere 5. Sphere 5. 1v. Sphere 5. Sphere 4. 1v. Sphere 4. Third party backup images and virtual machines to be discontinued. See Support notice. Acronis True Image Echo 9. Acronis True Image Home 1. Symantec Backup Exec System Recovery formerly Live. State Recovery 6. Live. State Recovery 3. Norton Ghost version 1. Parallels Desktop 2. Compressed disks are not supported. Parallels Workstation 2. Compressed disks are not supported. Parallels Virtuozzo Containers are not supported. Storage. Craft Shadow. Protect Desktop, Shadow. Protect Server, Shadow. Protect Small Business Server SBS, Shadow. Protect IT Edition, versions 2. The Microsoft VHD format for the following sources. Microsoft Virtual PC 2. Reimage Serial Free Download. Microsoft Virtual PC 2. Microsoft Virtual Server 2. R2. vmc. For conditions and limitations about converting Backup Exec System Recovery, Shadow. Protect, and Consolidated Backup images, see the VMware v. Center Converter Standalone Users Guide. Depending on the selected source, you can convert it to the following destinations. VMware v. Center virtual machines. ESX 4. 0 and 4. 1 ESXi 4. Center Server 4. 0, 4. VMware Desktop virtual machines. VMware Workstation 1. VMware Player 6. x and 7. VMware Fusion 6. x and 7. Earlier releases of Converter Standalone versions 3. VMware v. Sphere 6. Top of Page. Supported Guest Operating Systems. Converter Standalone 6. Windows Server 2. R2 SP2 3. 2 bit and 6. Windows Vista SP2 3. Windows Server 2. SP2 3. 2 bit and 6. Windows Server 2. R2 6. 4 bitWindows 7 3. Windows 8 3. 2 bit and 6. Windows 8. 1 3. 2 bit and 6. Windows Server 2. Windows Server 2. R2 6. 4 bitCent. OS 6. Cent. OS 7. 0 6. Red Hat Enterprise Linux 4. Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 6. Red Hat Enterprise Linux 7. SUSE Linux Enterprise Server 9. SUSE Linux Enterprise Server 1. SUSE Linux Enterprise Server 1. Ubuntu 1. 2. 0. 4 3. Ubuntu 1. 4. x 3. CAUTION During cloning of powered on Linux machines, Converter Standalone 6. All other source file systems are converted into ext. For more information about the operating systems supported by Converter Standalone and other system requirements, see the VMware v. Center Converter Standalone Users Guide. Top of Page. Prior Releases of Converter Standalone. Features from prior releases of Converter Standalone are described in the release notes for each release. To view release notes for prior releases of Converter Standalone, click one of the following links Top of Page. Known Issues. The Converter Standalone 6. Top of Page. Installation. If the name of the Converter Standalone installation directory contains non ASCII characters, you might experience conversion and configuration problems If the name of the Converter Standalone installation directory contains non ASCII characters, the following issues might occur. Conversion and configuration of Windows virtual machines might fail with an error message Unable to reconfigure destination virtual machine. In the vmware converter worker. Error 3 error restoring key Unknown error 3 0x. C n. dataSKUNKWORKSFILLER into. If you try to convert a Linux physical machine, you might receive an error message in the Convert Machine wizard Unable to obtain hardware information. You must restart machines that run 6. Windows Vista or later before re installing Converter Standalone. If you uninstall Converter Standalone from a 6. Windows Vista, Windows Server 2. Windows 7 machine and do not restart it, a subsequent Converter Standalone installation might fail with the following error message Error 2. Could not install service Vstor. Mnt. Api 1. 0 Driver shared. Please reboot and try to install again. Workaround Restart the Windows Vista, Windows Server 2. Windows 7 machine and try installing Converter Standalone again. Converter Standalone installer removes Workstation 6. When you use Workstation 6. Windows source machine, Workstation deploys a remote Workstation agent on the source. If you choose to leave the remote agent on that source and then install Converter Standalone on the same machine, the Converter Standalone installer uninstalls that agent without any warning messages. Users with limited rights cannot install Converter Standalone on Windows. If you are logged in to Windows as a non administrator user, the following error message is displayed while the Install.