Backup Exec upgrade 15 to 21 fails with V-225-302 Failed to install SQL Express BKUPEXEC instance
Hi, i'm trying to upgrade Backup Exec 15 to 21 and having an error "V-225-302: ERROR: Failed to install SQL Express BKUPEXEC instance with error -2067922411" Is there any solutions to resolve this problem? I attached a log below Thanks for any help in advacne ----------------------------------------------------------------------------------LOG----------------------------------------------------------------- <div class="error"><b><font color="red"><a name="10-11-2023,16:15:24 ,6803943" style="cursor:hand" onclick="resetfilters('#10-11-2023,16:15:24 ,6803943')"> + </a>10-11-2023,16:15:24 : V-225-302: ERROR: Failed to install SQL Express BKUPEXEC instance with error -2067922411. ***To search for information about this error, click <a href="http://support.veritas.com/umi/V-225-302" target="main">here </a> </font></b><BR></div> <div class="warning"><b><font color="orange"><a name="10-11-2023,16:15:24 ,890996" style="cursor:hand" onclick="resetfilters('#10-11-2023,16:15:24 ,890996')"> + </a>10-11-2023,16:15:24 : Please review C:\Program Files (x86)\Microsoft SQL Server\120\Setup Bootstrap\LOG\Summary.txt for more details.</font></b><BR></div> <div class="info">10-11-2023,16:15:24 : The return value for Microsoft SQL Express returned error code: 2227044885<BR></div> <div class="info">10-11-2023,16:15:24 : Clean up Product installer keys.<BR></div> <div class="info">10-11-2023,16:15:25 : Terminal Services enabled.<BR></div> <div class="info">10-11-2023,16:15:25 : Terminal Services server has been set to Execute mode.<BR></div> <div class="info">10-11-2023,16:15:25 : Failure Detected during Install Progress<BR></div> <div class="info">10-11-2023,16:15:25 : Entering RollbackDB<BR></div> <div class="info">10-11-2023,16:15:25 : RollbackDB - Successfully read 'Upgrade State' value from Software\Veritas\Backup Exec For Windows\Backup Exec\21.0\Install\MigrationStatus<BR></div> <div class="info">10-11-2023,16:15:25 : Param file C:\ProgramData\Veritas\Backup Exec\{19BFB759-5342-4B0E-99A9-171B6C0600F9}\BEInstParams.prm is not available.<BR></div> <div class="info">10-11-2023,16:15:25 : Executing BE_DetachDB.<BR></div> <div class="info">10-11-2023,16:15:25 : Executing Detach_BEDB.<BR></div> <div class="info">10-11-2023,16:15:25 : SQL_GetServiceName. GetComputerName<BR></div> <div class="info">10-11-2023,16:15:25 : SELCSFP1<BR></div> <div class="info">10-11-2023,16:15:25 : DRIVER={SQL Server Native Client 11.0};SERVER=SELCSFP1\BKUPEXEC;Trusted_Connection=Yes<BR></div> <div class="info">10-11-2023,16:15:25 : Unsuccessful return code from SQL statement: SELECT state_desc DatabaseStatus_sysDatabase FROM sys.databases WHERE name = 'BEDB'<BR></div> <div class="info">10-11-2023,16:15:25 : Stopping BEDB SQL service<BR></div> <div class="info">10-11-2023,16:15:25 : Upgrade rollback. Replace damaged BEDB with backed up version of previous BEDB mdf and ldf files.<BR></div> <div class="info">10-11-2023,16:15:25 : BEDB file D:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf has been updated with D:\Program Files\Symantec\Backup Exec\Data\DataBackup2023-10-11-04-09-59\Data\BEDB_dat.mdf.<BR></div> <div class="info">10-11-2023,16:15:26 : BEDB file D:\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf has been updated with D:\Program Files\Symantec\Backup Exec\Data\DataBackup2023-10-11-04-09-59\Data\BEDB_log.ldf.<BR></div> <div class="info">10-11-2023,16:15:26 : RollbackDB - Running BE_AttachDB<BR></div> <div class="info">10-11-2023,16:15:26 : GetClusterUpgradeState returning 0<BR></div> <div class="info">10-11-2023,16:15:26 : Param file C:\ProgramData\Veritas\Backup Exec\{19BFB759-5342-4B0E-99A9-171B6C0600F9}\BEInstParams.prm is not available.<BR></div> <div class="info">10-11-2023,16:15:26 : Executing Attach_BEDB.<BR></div> <div class="info">10-11-2023,16:15:26 : SQL_GetServiceName. GetComputerName<BR></div> <div class="info">10-11-2023,16:15:26 : SELCSFP1<BR></div> <div class="info">10-11-2023,16:15:26 : DRIVER={SQL Server Native Client 11.0};SERVER=SELCSFP1\BKUPEXEC;Trusted_Connection=Yes<BR></div> <div class="info">10-11-2023,16:15:26 : Connected to SQL Server.<BR></div> <div class="info">10-11-2023,16:15:26 : Unsuccessful return code from SQL statement: SELECT state_desc DatabaseStatus_sysDatabase FROM sys.databases WHERE name = 'BEDB'<BR></div> <div class="info">10-11-2023,16:15:26 : Attaching BEDB to SQL Server.<BR></div> <div class="info">10-11-2023,16:15:26 : EXEC sp_attach_db 'BEDB',@filename1 = N'D:\Program Files\Symantec\Backup Exec\Data\BEDB_Dat.mdf', @filename2 = N'D:\Program Files\Symantec\Backup Exec\Data\BEDB_Log.ldf'<BR></div> <div class="info">10-11-2023,16:15:26 : BEDB has been succesfully attached to SQL Server.<BR></div> <div class="info">10-11-2023,16:15:26 : Change BEDB owner to SA user.<BR></div> <div class="info">10-11-2023,16:15:26 : Successfully changed BEDB owner to sa.<BR></div> <div class="info">10-11-2023,16:15:26 : RollbackDB - Installer will start the BE services<BR></div> <div class="info">10-11-2023,16:15:26 : BE_ControlBEServices<BR></div> <div class="info">10-11-2023,16:15:26 : Check and configure PDDE services<BR></div> <div class="info">10-11-2023,16:15:26 : BE_SetPDDEServiceConfig<BR></div> <div class="info">10-11-2023,16:15:26 : BE_SetPDDEServiceConfigSPAD<BR></div> <div class="info">10-11-2023,16:15:26 : BE_SetPDDEServiceConfigSPAD: spad service is not found, so dependency will not be set.<BR></div> <div class="info">10-11-2023,16:15:26 : BE_SetPDDEServiceConfigSPOOLD<BR></div> <div class="info">10-11-2023,16:15:26 : posgresql-8.3 service not found: dependency will be set to : spad<BR></div> <div class="info">10-11-2023,16:15:26 : spoold service is not found<BR></div> <div class="info">10-11-2023,16:15:26 : BE_SetPDDEServiceConfigMTSTRMD<BR></div> <div class="info">10-11-2023,16:15:26 : mtstrmd service is not found, skipping configuration.<BR></div> <div class="info">10-11-2023,16:15:28 : Successfully started service - bedbg. Elapsed time: 1516 ms.<BR></div> <div class="info">10-11-2023,16:15:28 : Successfully started service - MSSQL$BKUPEXEC. Elapsed time: 0 ms.<BR></div> <div class="info">10-11-2023,16:15:37 : Successfully started service - BackupExecAgentAccelerator. Elapsed time: 9609 ms.<BR></div> <div class="info">10-11-2023,16:15:45 : Successfully started service - BackupExecDeviceMediaService. Elapsed time: 7687 ms.<BR></div> <div class="info">10-11-2023,16:15:57 : Successfully started service - BackupExecRPCService. Elapsed time: 12032 ms.<BR></div> <div class="info">10-11-2023,16:15:59 : Successfully started service - BackupExecAgentBrowser. Elapsed time: 1562 ms.<BR></div> <div class="info">10-11-2023,16:16:09 : Successfully started service - BackupExecManagementService. Elapsed time: 10469 ms.<BR></div> <div class="info">10-11-2023,16:16:11 : Successfully started service - BackupExecJobEngine. Elapsed time: 1594 ms.<BR></div> <div class="info">10-11-2023,16:16:11 : ERROR: Failed to start service - BackupExecLockdownServer. Elapsed time: 0 ms. Error: Service handle null.<BR></div> <div class="info">10-11-2023,16:17:10 : Skipping push of remote servers and agents due to failed local install.<BR></div> <div class="info">10-11-2023,16:17:10 : BeSeqDlgs::DlgInstallComplete<BR></div> <div class="info">10-11-2023,16:17:10 : AgentSeqDlgs::Misc_BE_CommonOps<BR></div> <div class="info">10-11-2023,16:17:10 : Dialog Sequence Returning errorlevel -2067922411<BR></div> <div class="info">10-11-2023,16:17:10 : Setting up failed completion dialog.<BR></div> <div class="info">10-11-2023,16:17:10 : Setting up failed completion dialog (Install).<BR></div> <div class="info">10-11-2023,16:17:10 : Initialize the telemetry items on the dialog<BR></div> <div class="info">10-11-2023,16:17:10 : GetClusterUpgradeState returning 0<BR></div> <div class="info">10-11-2023,16:17:10 : GetClusterUpgradeState returning 0<BR></div> <div class="info">10-11-2023,16:17:10 : Skipping push of remote servers and agents due to failed local install.<BR></div><BR><HR><BR><BR></div> </body> </HTML>Solved1.2KViews0likes1CommentCannot login to Symantec Backup 14.2
After migration of domain , Backup exe unable to login. it is showing error as pre the attachment. Symantec Backup exec Version 15 (14.2) Windows server 2012 R2 We had local domain , after migrate to global domain . the system unable to login to console we create one id for backupadmin and add that id under local administrator of the server. Plz help us670Views0likes1CommentAbout DB2 alternate restore
Dear friends, I want to restore DB2 databases to a different client/instance, from a schedualed daily backup. and I have several questions because it's my first time to do the DB2 restore. Could you please help. [enviroment] Redhat enterprise server release 6.10, NBU v7.7.3, DB2 Enterprise Server Edition 10.5 [Server Policy] A daily DB2 type policy with 2 scheduals(application backup &Automatic Full backup) and one backup script is configured and in use. [db2.conf] In this config file, there are object identifier statements for backing up databases only, no object identifier for backing up the archive logs,or for functions. [backup scripts] In this script, “db2 backup db xxxx online load /usr/openv/netbackup/bin/lib include logs” is coded, which is schedualed to excute daily. [Documentation] I have read the topic "About an alternate restore" in Chapter 4. Performing backups and restores of DB2 of the "NetBackup? for DB2 Administrator's Guide release 7.7" [question] 1. I want to restore DBs to a specific date(ex:2022/9/1), and I can't find the info where and how to specify this date option during the restore configration in above guide. 2. Were archieve logs and active logs backed up daily in my backup configration, if not, which logs are required for this specific date restore task, or none of them is required?1.3KViews0likes7CommentsFinal error: 0xe0000f29 - Restore job does not see tape in library for restore job
So I've moved my tapes from my management BE server to the CAS server for a restore off site. I insert the tapes .. scan / inventory. Right click and look at details of the tape and all looks good .. data is was what was backed up at other location and now show in tape library 2 (CAS tape library) all is great... Now when I go run the restore it fails with: Completed status: Failed Final error: 0xe0000f29 - This Backup Exec server cannot access the device selected in the settings for the job. Refer to the job log for details The media required by this job is located on device 'Robotic library 5'. Select device 'Robotic library 5' in the job settings. Well I am doing this... this is the CAS tape library name and it even shows me in the details the tape is located in Library 2. I'm stumped. I've rebooted / stop/start a;; services each location .. made sure I can get to each BE server from each other. Is it my catalogs? can I restart them from scratch? Im just not sure what is causing this to happen.985Views0likes3CommentsBackup Exec on Windows Server 2016 Failed to Start
MyBackup Exec which Runs on Windows Server 2016 fails to Start, it loads but doesnt complete the startup, all the services are running. I ran the BE Utility and dumped, repaired, rebuild, compacted the database all in vain. initially i tried to repair the installation in vain. kindly assist834Views0likes2CommentsCan Database can be restored temporarily - when server failed?
Well currently we got stuck in the captioned situation, and got very frustrated in passed couple weeks. My only question is, is it possible to restore the database before original server recovered? Let me elaborate a little more. Backup Exec 15 was set up at our only server several years ago, which went well until couple weeks ago. The mainboard of Lenovo blade type server much likely reached the end of its life, and it turns out a long period of pending time for new spare part delivery. The backup data has been stored in a NAS directly connected to the server, with LAN cable, and it functions well throughout the time. After the server failed, we have been asking around if the database in NAS can be restored, for the temporary use, while most activities in company simply stopped. The Backup Exec dealers in town cannot give us a solution, which raise our doubt, whether it is impossible to restore without original hardware, or the cost would be very high, or certain condition must be matched, or what-so-ever. This message is not written by IT expert, but just an user, so we are probably wrong technically. Nevertheless, we feel that Backup Exec cannot properly protect data when we need it to. It is a story from Hong Kong, and we hope to hear the answers from experts here. Thank you!972Views0likes4Comments"(Unknown media)" when rotating tapes
I have a Tandberg LTO6 autoloader & BE2012 that I support at one site, and an Overland LTO6 autoloader & BE15 at another. All tapes at both sites are bar-coded. At the Tandberg/BE2012 site, when I rotate previously used, but now overwritable, tapes into the slots and do a Scan from BE, the tapes are shown with their correct labels and are recognized. At the Overland/BE15 site, when I do the same thing, the tapes that I've just loaded show the correct Barcode and Media Label, and all other columns for that matter.But in the Description column, it shows "(Unknown media)". If I inventory those slots, (or just let BE choose those tapes for a backup) the "(Unknown media)" designation goes away. There's no practical difference, so this is really just curiosity, but why are tapes at the Tandberg/BE2012 site recognized correctly, and those at the Overland/BE15 site "unknown" until I inventory or reuse them? Is it an Option setting? Difference between BE2012 and BE15 media management? Autoloader hardware difference?Solved4.1KViews0likes7Comments