V-79-57344-38366 Backup Exec 20.6 12TB VMDK
Hey all, I've finally got all my backups working correctly EXCEPT a legacy drive inside a VMware guest server. I had excluded this single VMDK from the nightly backup job and have set up a single one-time backup of this drive as a seperate job. However I cannot get the one-time job to succeed. The job runs for the entirety of the 11.7TB of data inside that 12TB drive but results in the error I included below. The job takes about 2 days to complete unsuccessfully. Currently the job is setup to use the same storage space as the pre-mentioned nightly backup job of this guest VM's other drives. So I know this isn't a permissions issue. I'm assuming as well, since I simply copied the nightly job and then unselected the drives from that job and added the single 12TB drive that the configuration is likely not the issue. Backup- VMVCB::\\<vmguest>.example.com\VCGuestVm\(DC)ha-datacenter(DC)\vm\[110] VMGUSET-79-57344-38366 - VDDK-Warn: VDDK_PhoneHome: HTTP response error in VddkVacCurlHttpsPost with http status 400 at 1058. VDDK-Warn: VDDK_PhoneHome: VddkVacPushData : Failed to post data to VC/PH at line 1022. VDDK-Warn: VDDK_PhoneHome: VddkVacPushVendorProductData : Failed to push vendor product data at line 1326. VDDK-Warn: VDDK_PhoneHome: VddkVacWriteMember : Empty field to serialize for key edition at line 188. VDDK-Warn: VDDK_PhoneHome: VddkVacPushProductInstanceData : Failed to push product instance data at line 1219. VDDK-Warn: VDDK_PhoneHome: VddkVacPushEnvironmentData : Failed to push env data at line 1136. VDDK-Warn: VDDK_PhoneHome: VddkVacPushSessionData : Failed to push session data at line 1709. VDDK-Warn: VixDiskLib: VixDiskLibIsLegacyConnParams: the instance of VixDiskLibConnectParams is NOT allocated by VixDiskLib_AllocateConnectParams. The new features in 6.7 or later are not supported. VDDK-Warn: HostAgent is not a VirtualCenter. Error 20 at 3710. VDDK-Warn: VDDK_PhoneHome: Invaild transport mode used at line 271 VDDK-Warn: VixDiskLibProvider::NameBasedProvider::Get: Unable to open disk \\UNC\PATH\TO\STORAGE\IMG000027\GUESTVM_1-000002.vmdk, openflags = 4 - VixError 0x3e86. VDDK-Warn: DiskLibProvider_GetDisk: Open failed - index 0. VDDK-Warn: ERROR 2 opening disk 0. VDDK-Warn: VixDiskLibProvider::NameBasedProvider::Get: Unable to open disk 1:\IMG000027\GUESTVM_1-000002.vmdk, openflags = 4 - VixError 0x3e86. The line "The new features in 6.7 or later are not supported.", seems of note as the GUESTVM I'm trying to backup is on a ESXi Server 6.7. But again, that same GUESTVM does backup correctly if I exclude that one 12TB vmdk. My backup exec server is on an older ESXi 5.5 host running a Windows Server 2012R2 guest. The GUESTVM I'm backing up is a Windows Server 2016 install. I notice that in the \\UNC\PATH\TO\STORAGE location when the job starts, it creates 8 GUESTVM_1-000002 vmdk that look to split. The first VMDK reaches 1.98TB and then it starts filling the second. This one ends up around 700GB when the job ends. Please help!8.2KViews0likes7CommentsCannot add Microsoft hyper-v host - connection state closed error
Using Veritas backup exec on Vmware i am unable to add my microsoft hyper-v host server in backup exec . the error message displayed is Cannot insert a resource container - DataAccessBEServer ResourceContainer_Insert: ExecuteReader requires an open and available Connection. The connection's current state is closed. Please Help!4.6KViews0likes7CommentsSOLVED: BE VirtFile.sys Preventing Re-Installation
Hi all, SUMMARY: PS C:\Windows\system32> fltmc Filter Name Num Instances Altitude Frame ------------------------------ ------------- ------------ ----- FsDepends 8 407000 0 WdFilter 8 328010 0 VirtFile 3 280700 0 storqosflt 1 244000 0 wcifs 0 189900 0 CldFlt 0 180451 0 FileCrypt 0 141100 0 luafv 1 135000 0 npsvctrig 1 46000 0 Wof 1 40700 0 and trying to remove virtfile.sys: PS C:\Windows\system32> fltmc unload VirtFile Unload failed with error: 0x801f0010 Do not detach the filter from the volume at this time. I've got BE 21.2 R2 - but because it's a charity license (technically an NFR), there's no support, despite having a valid license slf. I've been using BE 20.x and 21.x for about a year now for this charity on a Windows 2019 box. All was fine until last month when backups would get stuck as Queued. They could stay queued for weeks! I'm a volunteer and the only admin. Pretty desperate for help. I had previously tried everything to get jobs to actually run, including updating to 21.2 from 21.0. I didn't see any activity on any storage, and just to be sure, I added new USB storage and tried a new job to there = still queued forever. The update to 21.2 (r2 1900) failed and it rolled back. I restarted, and tried again and it did update. But still, no backups would run, they'd just stay queued. So I tried an uninstall - which failed. After that I couldn't even launch BE. I've been trying to re-install since them without any luck. I can't even get the agent to install on this server. + 06-02-2021,12:42:15 : RAWS_SetLdsVffLogging - Failed to set the registry value 'SYSTEM\CurrentControlSet\Services\VirtFile\Parameters' - [Max Log Entry]=0. Ensure this value is manually set. - Error code 5: Access is denied. + 06-02-2021,12:42:20 : RAWS_SetLdsVffLogging - Failed to set the registry value 'SYSTEM\CurrentControlSet\Services\VirtFile\Parameters' - [Max Log Entry]=0. Ensure this value is manually set. - Error code 5: Access is denied. + 06-02-2021,12:42:25 : RAWS_SetLdsVffLogging - Failed to set the registry value 'SYSTEM\CurrentControlSet\Services\VirtFile\Parameters' - [Enable Logging]=0. Ensure this value is manually set. - Error code 5: Access is denied. I've taken ownership of hklm\system\currentcontrolset\serves\virtfile, but I cannot delete that key, I assume because virtfile.sys is running and that appears to have something to do with the lockdown service. Beyond that, I'm lost (as if you couldn't tell).... Any guidance would be greatly appreciated. I cannot open a case with support because it's a charity license. ThanksSolved4.4KViews0likes3CommentsFinal error: 0xe00086cc - Access Denied.(Agent update)
We run BE v21, and for the most it's working. Some servers run the backup but also say that the agent is outdated: The remote computer is running a previous version of the Backup Exec Agent for Windows. You must upgrade the Agent for Windows to enable the new features and capabilities of the current version of Backup Exec . I then proceed to do an update of the agent from the server. But then I get the error message: Final error: 0xe00086cc - Access Denied. Ensure that you have the appropriate credentials to access the remote computer and that the UAC remote restrictions are disabled and then try again. On the backup server we have a service account that runs the BE services. On the servers with the agent, I see that this service account is added to the local administrator group. But the "Backup Exec Remote Agent for Windows" service was set to use Local System. So I guess that this might be an issue, so I changed the service to use the same service account as the BE server is using. But still I get the same error message. I also turned off UAC (with a change in Registry) and rebooted the server. Still I get the same error message. So what else can stop the agent from being updated? I find it strange since the server is being backup up.4.3KViews0likes1CommentBackup exec 21.2 Upgrade from 21.1 Speed Issue
Hi All, Has anyone noticed any speed issues with BE 21.2 (21.0.1200.1899) For example a backup of a VM that takes 40 seconds now takes over 4 mins, used to take 1 min with 21.1. Look at the start and finish times compared to the VM backup times. 21.2 Backup started on 12/05/2021 at 17:01:45. Backup Set Detail Information Media Label: IMG000170 GRT backup set folder: E:\BEData\IMG000170 The standard processing method will be used for incremental and differential backups. The data in Pagefile.sys will be skipped during backup because the data is transient and does not need to be restored. Backup Exec has discovered and protected 'C:' on virtual machine 'XXXXXX-DC01.XXXXXX.local'. Backup Exec has discovered and protected Microsoft Active Directory data on virtual machine 'XXXXXXl-DC01.XXXXXX.local'. Backup completed on 12/05/2021 at 17:05:50. Backup Set Summary Backed up 3 files in 8 directories. Processed 16,599,073,988 bytes in 40 seconds. Throughput rate: 23745 MB/min 21.1 Backup started on 08/05/2021 at 17:01:07. Backup Set Detail Information Media Label: IMG000114 GRT backup set folder: E:\BEData\IMG000114 The standard processing method will be used for incremental and differential backups. The data in Pagefile.sys will be skipped during backup because the data is transient and does not need to be restored. Backup Exec has discovered and protected 'C:' on virtual machine 'XXXXXX-DC01.XXXXXX.local'. Backup Exec has discovered and protected Microsoft Active Directory data on virtual machine 'XXXXXX-DC01.XXXXXX.local'. Backup completed on 08/05/2021 at 17:02:08. Backup Set Summary Backed up 3 files in 8 directories. Processed 16,210,747,454 bytes in 37 seconds. Throughput rate: 25070 MB/min I have seem something strange in the log files between the 2 backups. In 21.1 i'm seeing this : [7060] 2021-05-01T17:02:04.290 [loops] - BackupBSDProcessor::ExtendedAddFile: m_bVirtSet 1 m_virtDataId 60 m_virtBedsId 60 m_virtBedsVer 0 [7060] 2021-05-01T17:02:04.295 [server] - MSG_END_VIRTUAL_BACKUP_SET: Restore Work Flow (RWF) in 21.2 im seeing this : BENGINE: [05/12/21 17:02:41] [5800] [loops] - BackupBSDProcessor::ExtendedAddFile: m_bVirtSet 1 m_virtDataId 14 m_virtBedsId 73 m_virtBedsVer 0 BENGINE: [05/12/21 17:02:50] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:02:55] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:00] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:05] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:10] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:15] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:20] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:25] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:30] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:35] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:40] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:45] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:50] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:03:55] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:04:00] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:04:05] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:04:10] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:04:15] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:04:20] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:04:25] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:04:30] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:04:35] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:04:40] [5800] [ndmp\ndmpcomm] - ndmp_readit: Control connection socket (0x8e4) not readable! BENGINE: [05/12/21 17:04:42] [5800] [server] - MSG_END_VIRTUAL_BACKUP_SET: Restore Work Flow (RWF) is empty I'm getting a lot of these ndmp readit errors, what ever they are. I don't have ndmp enabled in the options. Can anyone shed any light on what is going off here as i'm guessing this is causing all the VM backups to slow down making the backups times about 40% longer. cheersSolved3.8KViews0likes11CommentsHow to deploy Backup Exec via the Azure Marketplace
How to deploy Veritas Backup Exec on Azure Marketplace. Veritas Backup Exec provides simple, rapid, and secure offsite backup to Azure for your on-premises environments and protects cloud-based workloads in Azure. Veritas Backup Exec helps customers recover quickly from critical data loss situations, and easily meet data regulatory requirements. By leveraging Veritas Backup Exec in the cloud as well as on-premises, you gain a unified and efficient data protection experience. Deploying Veritas Backup Exec via marketplace frees businesses from purchasing and managing IT infrastructure and enables them tomove to a more cost-efficient operational expense (OpEx) model. To learn “What’s New” with Backup Exec, visit the Veritas Backup Exec webpage. Steps to deploy the Veritas Backup Exec in Azure Marketplace: Through the Azure Marketplace, you can easily and quickly deploy the Veritas Backup Exec 1. Visit Azure Marketplace and click on “GET IT NOW” to use Veritas Backup Exec Note: This is the Veritas Backup Exec for Azure BYOL. 2. Click on “Continue” to take you to the Azure portal. Log in to the Azure portal and click on “continue”. 3. On the Azure Portal click on “Create” 4. Provide required details in “Basics”, “Network and Storage Settings”, “Backup Exec server IP address assignment” tabs and click on “Review + Create”. 5. The “Validation Passed” message will appear on the screen. Click on “Create.” 6. Once you click on create, it will show you “deployment is in progress” 7. Once deployment is completed, click on “Go to Resource Group”. 8. Select the BE server virtual machine. 9. Click on “Start” Virtual Machine, click on “Connect” and select “RDP”. 10. Click on “Download RDP file” and Connect to VM once the RDP file is downloaded. 11. Your Veritas Backup Exec server is now running and you are ready to use Veritas Backup Exec 60 days trial Version. About Licensing: Contact Veritas Technologies LLC to get a license. Veritas Backup Exec support contact3.7KViews3likes0CommentsHow to deploy Backup Exec via the AWS Marketplace
How to deploy Veritas Backup Exec on AWS Marketplace. Veritas Backup Exec provides simple, rapid, and secure offsite backup to AWS for your in-house virtual and physical environments and protects cloud-based workloads in AWS. Veritas Backup Exec helps customers recover quickly from critical data loss situations, and easily meet data regulatory requirements. By leveraging Veritas Backup Exec in the cloud as well as on-premises, you gain a unified and efficient data protection experience. Deploying Veritas Backup Exec via marketplace frees businesses from purchasing and managing IT infrastructure and enables them tomove to a more cost-efficient operational expense (OpEx) model. To learn “What’s New” with Backup Exec, visit the Veritas Backup Exec webpage. Steps to deploy the Veritas Backup Exec in AWS Marketplace: Through the AWS Marketplace, you can easily and quickly deploy the Veritas Backup Exec. 1. Visit AWS Marketplace and click on “Continue to Subscribe” to use Veritas Backup Exec. Note: This is the Veritas Backup Exec for AWS BYOL. 2. Click “Continue” to take you to the AWS portal. Log in to the AWS portal and click “Continue to Configuration”. 3. Set the Delivery Method to “Backup Exec Base Instance”, Software Version to the latest version of Veritas Backup Exec available, and Region to your desired region, then click on “Continue to Launch”. 4. Select Choose Action as “Launch CloudFormation” and Click on “Launch”. 5. On the CloudFormation screen, the default template will be selected in “Specify template”, to create a stack, click on “Next” 6. Specify stack details such as instance type, username, password, key name and CIDR block, etc. Click on “Next”. 7. Provide an appropriate option in the “Configure stack options” screen and click on “Next 8. Review details on the “Review” screen and click on “create stack” 9. The Marketplace “Stack Creation Progress” screen will appear. 10. Once stack creation is completed successfully, select the instance from AWS Instances Services and click on connect and download the RDP file to connect to the Virtual Machine. 11. Your Veritas Backup Exec server is now running and you are ready to use Veritas Backup Exec 60 days trial Version. About License: Contact Veritas Technologies LLC to get a license. Veritas Backup Exec support contact3.4KViews3likes0CommentsAn error occurred while processing a B2D command
Intermittently(on a daily basis, not time specific) i get a B2D command error . The storage device Nas(QNAP TS1685) has the latest firmware installed, the media server is fully up to date(latest backup exec version and fully updated windows). I even rebuilt the array type on that NAS which made no difference. Played around with changing the network switch MTU between 1500 and 9000, which made no difference. I trunked and untrunked connections, also made no difference. I even installed a secondary backup exec media server onto a VM that runs through a different switch. Both servers render the same intermittent error. I did a continuous ping to the nas, and it never drops, even while backup exec throws these intermittent errors. I even changed the storage device to only allow 1 concurrent write session : makes no difference. There is more than enough space on the shared drives. Like i said, sometimes the backup works after retrying a few times. It also does not happen on the same backup set. Totally random. Sometimes after several manual retries, the backup will start fine and even complete. But often, we end up with the below error in the event log. The deduplication option was the worst. The dedup storage device(the same nas device as mentioned above) would be online a few hours and then go offline in backup exec, even while the ISCSI connected drive is hundred percent fine and accessible via windows. This happens on the physical server(Central administration server) and on the VM(secondary backup exec server). We gave up on dedup, because backup exec requires a server restart to reconnect the drive(service restarts didn't work). It doesn't seem to care that it is perfectly fine and working in windows. Like i said, no ping drops, no windows connection drops mentioned in the iscsi event log. Just backup exec that decides randomnly to put the device in an offline state. I then started playing around with TCP/UDP offload settings on the media server network adapter. Switched off all offload settings on the network adapter. Made no difference. An error occurred while processing a B2D command. Drive: OpenPosMTF() CreateFile failed (\\cmsnas\Backup\BackupExecSlow150\B2D008940.bkf). Error=1326 For more information, click the following link: https://telemetry.veritas.com/entt?product=BE&module=eng-event&error=V-379-33808&build=retail&version=21.0.1200.1204&language=EN&os=Windows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x32.9KViews0likes5CommentsRestore Exchange Backup to PST (am i screwed with Exchange 2019 and Office 2016/2019/2021/365) ?!
Hello, i would like to know, how to restore a Exchange User Mailbox to a PST. I have read the latest Veritas Artikel in KB, how to restore. To my understanding, i can only Restore a mailbox with Outlook 2010 installed on the BE Server and with Exchange 2016. How would i restore a user mailbox to a pst if i only have Outlook 2016/2019 or 365 and Exchange 2019? Is there any recommendation? I use BE 21.2 Rev 1200.1899 Thanks JürgenSolved2.8KViews0likes11CommentsServer / Console version mismatch error
Recently had a hung backup that I cleared by restarting the BE services throught the console. Immediatly after console comes up with a login prompt. When I put in credentials I get error: "Cannot connect to <servername>. You must use the same version of backup exec server and the backup exec administration console." I installed both server and console on the same windows 2019 server so I know they are the same version. The Console is running locally. Any ideas?2.7KViews0likes9Comments