Backup fails with error E00084AF
Backup fails with this error "The directory or file was not found, or could not ba accessed" This is happening for multiple directories. Directories exist and are accessible via Windows Explorer and the selection screen in Backup Exec. Veritas Support have no idea and just keep asking for new job logs and VQA reports. Any ideas?
An 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-0x3Server / 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?
Duplicate job copy data from original location instead of source job location
We use BackupExec 22 Rev 1193.1009. BackupExec server (hardware serverProLiant BL460c Gen9) is connected to SAN and LTO8 library. Speed of Ethernet connection is 10Gb/s At first backups are saved to SAN deduplication storage. Then - duplicate job runs. We intended that duplicate job would run from SAN backup, not from original location. The speed between SAN and tape is much faster than speed between original data location and tape. We intended to make a system where 8 backups will run simultaneously to SAN. They are slow (because they copy data from original location) but we do not care - because we can run many backups simultaneously. THEN - when first stage backups are finished - they duplicate to tape. They run only in 3 streams (because library only has 3 drives), but we do not care - because the speed from SAN to LTO8 tape is fast. But it seems, that duplicate backups run from original location, instead of SAN, where first stage of backups are saved. This is VERY VERY bad to us, because we need to backup about a hundred servers and some of them are large. If duplicate backup - copy data from original location, instead from SAN - we loose speed in about 6-8 times I think. I opened topic about a year ago about this issue and I was informed that duplicate backups run from primary backup, not from original data location. Does duplicate JOB copy data from source VM or fro... - VOX (veritas.com) I tried to enable\disable "Direct copy to tape" checkbox, BacupExec still copy data in duplicate backup from original location. Also I tried to save first stage of backup to regular disk storage (without deduplication). This is disk storage on BackupExec server itself - so speed must be very high. But BacupExec still copy data in duplicate backup from original location, not from disk storage. I also checked the bandwidth of optical Ethernet which is connected to BackupExec server and it is utilized no more than on 30% I tried to look through all options of backup, but didn't found anything related to problem - from where duplicate backups run: from original location or from first stage backup. Is it possible to configure duplicate backups to run from first stage backups location? How to do it? This will increase overall speed of my backup system in 6-8 times.
Failover Clustring-Client
Hi, When browsing the servers shares ( servers without agents) from BE 20 that is running on a server 2019, get this error in the Windows system events: Event 81, Failover Clustring-Client. server in the error or BE 20 server itself are not part of any cluster and Cluster tools are not installed. LogExtendedErrorInformation (974): Extended RPC error information: ProcessID is 12484 System time is: 12021/469/53726 0:0:15376:2963 Generating component is 2 Status is 1753 Detection location is 501 Flags is 0 NumberOfParameters is 4 Unicode string: ncacn_ip_tcp Unicode string: Servername Long val: -1182943054 Long val: 382312662