Veritas Backup Exec version upgrade & migrate to another new Server
Hello, We need to upgrade our Veritas Backup Exec version from 16 to latest compitable version as per hardware support in existing Server having OS is Windows Server 2008 R2 Standard, then need to migrate the same to new Server hardware with Windows Server 2022 Standard. Please help us to do the same. Thanks & Regards, Soumabrata Bhaumik
BMR Restore won't start "Failed to verify backup--rc(1002)
Hi, We are running NBU 8.0 (both clients, medias, master), and these days I'm trying to perform a BMR restore on a W2008r2 client using NBU 8.0. We're not encountering any errors with the backup operations, but when we start a BMR Restore (USB Key Boot, as we always do here), we encounter: I don't know what clues or logs I should search for, as this is the first time I've encountered this error, and I can't find anything on the Veritas forums or elsewhere. (same problem with Prepare to Restore) Can anyone helps with this error rc(1002) ?Unable to obtain list of backup Images using specified search criteria. ERROR: pipe close failed
ENVIRONMENT Netbackup Version = 8.1 OS = Windows 2008 R2 Enterprise De-Duplication = Configured QUERY For me it seems the backups are expired and no backup images exist on this Netbackup machine. Anyone have idea which let me assume that there are backups but need to figure out the issue on Netbackup machine DETAILS I came across in an issue where in a environment (around 6-8 months back) a netbackup machine was shutdown. As per the administrator the netbackup machine was a DR site machine and was getting sync via Netbackup AIR feature from a Primary site Netbackup server. Now yesterday the shutdown machine had to ON/Start. But unable to find backup OR catalog. Following are some snapshots as a reference Don't know what is this in MSDP pool
Veritas Backup Exec Client Services Suddenly Stopped
I'm having an issue with a work server where the Services for one client stopped. It would perform differential backups just fine, but when it came time to do Full backups, instead of the normal 8-10 hours it would take over a day and then time out of the job. I did a restart on the client, thinking that it had been over 2 months since the last reboot, and host server and since then it says it can not pull the necessary information from the registry to start the Automatic tasks its set to. So now it will not even perform the differentials that it was fine doing before the reboot. I've been trying to restart the services for this client, but so far I have not gotten any where. Can anyone help suggest anything? Also, last year in March I had a similar issue, and fortunately I was able to exit out of the agent and when I opened it again it had pulled the necessary information it needed. This time that isn't happening.Tape Drives show Missing Paths
Some of my tape drives are showing missing paths after a migration from one Fiber switch to another. I have validated that the zones are setup the same on the networking side (and even see the drives checked in, in the fiber database on the switches), I tried a solution from a previous post on one of the drives with the missing path(removing the drive and running tpautoconfig -a), but am not actually seeing the drive show back up after running tpautoconfig -a. Any assistance would be very helpful.
Windows 2008R2 - Final error: 0xe000ff15 - A communications failure has occurred with a System State
Basic Infor: BackupExec Product: Vertias Backup Exec 20.6 Rev 1188 (Installed on dedicated server windows w 2016 OS with IBM TS2900 Tape Loader) Client OS: Physical Windows Server 2008 R2 - 64 Bit / OS Patches status , updated Getting below error while taking (SDR) FULL backup of client Final error: 0xe000ff15 - A communications failure has occurred with a System State resource. Sometimes it works fine, sometimes it doesn't. I tried to follow the guide to clear the windows update, but this error randomly occuring. Howto sort it on a permanent basis? Please refer below LOG, Backup started on 6/13/2023 at 5:58:25 AM. Tuesday, June 13, 2023 6:09:01 AM - V-79-57344-6530120.0.1188.2718eng-systemstate-backupV-79-57344-65301ENRetailWindows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x3 - The System State resource is not responding. Backup set canceled. Tuesday, June 13, 2023 6:09:01 AM - V-79-57344-4148820.0.1188.2718eng-systemstate-backupV-79-57344-41488ENRetailWindows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x3 - Due to one or more errors in \\MYSERVER\System?State, this backup cannot be used for conversion to virtual machines, Simplified Disaster Recovery (SDR), or a complete online restore. Backup completed on 6/13/2023 at 6:09:06 AM. Backed up 9 System State components Processed 6,685,467,793 bytes in 10 minutes and 41 seconds. Throughput rate: 597 MB/min Compression Type: Hardware ---------------------------------------------------------------------- 20.0.1188.2718eng-no_fs-backupENRetailWindows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x3 Job ended: Tuesday, June 13, 2023 at 6:09:28 AM Completed status: Failed Final error: 0xe000ff15 - A communications failure has occurred with a System State resource. Final error category: Resource ErrorsFinal 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.
