- #Symantec backup exec 2010 r2 tape drivers install
- #Symantec backup exec 2010 r2 tape drivers update
- #Symantec backup exec 2010 r2 tape drivers driver
- #Symantec backup exec 2010 r2 tape drivers upgrade
- #Symantec backup exec 2010 r2 tape drivers full
You do not need to remove the previous agent, the installer will upgrade the remote agent, and no reboot is required. I do this manually to avoid any unforeseen issues on our production systems. The last step of the upgrade process is to push out updated remote agents to your servers. If you see it, the file filter is installed and your backups should now be able to run without any errors. Yours should look like this: Symantec Backup Exec 2010 Virtual File Filter Installation in FLTM After installing, check to make sure the Symantec Virtual File Filter got installed: My installation ran successfully, and the 1606 error did not pop up. Type your license keys in the field and then click through to start the installation process.
#Symantec backup exec 2010 r2 tape drivers install
To do this, go to “Tools> Install Options and License Keys”. The next step is adding the license keys for Exchange and Active Directory back into Backup Exec 2010. My entry looks like this: Backup Exec Registry Settings
#Symantec backup exec 2010 r2 tape drivers update
Update the registry entry with the correct source path and close the registry editor.
My installation source files are located at C:\software\BackupExec2010\ (I copied the contents of the DVD to this folder and installed locally, if you are installing from the DVD Drive, your source path should be the drive letter, for example: D:\ ). In my case the key was there, but the value was blank. HKLM\SOFTWARE SYMANTEC\BACKUP EXEC FOR WINDOWS\13.0\INSTALL To examine this, open Regedit and navigate to: There is an error in the registry for the installation source location. Eventually I found Symantec KB 346375 which gave me the solution. Now, just for the heck of it, I installed an USB drive onto the supposely corrupted server and run Windows backup. Tried to backup something on the corrupted server and it hung so ok, it seems like it is server corruption. A search on Google for the specific error message did not return any fruitful results. Ok, so I tried installing BE on the second server and moved tape drive also. I tried a repair from “Programs and Features” in Windows, but the error persisted. Unfortunately, I received the same error that I got during the installation: Symantec Backup Exec 2010 Error 1606:Could not access network locationĮrror 1601.Could not access network location \DLO. To fix this issue, the KB article says to remove the Exchange and Active Directory license keys, then add them back in again. In my case, the “VirtFile” filter from Symantec was missing. Open a command prompt and type: fltmcĪ list of the installed file-system filters will be displayed. Checking for the presence of the Symantec Virtual File Filter is very easy.
Symantec KB #285543 provided some insight into what was causing the problem. I chose to ignore this error after the upgrade completed, but it appears to be critical and has to be fixed. The error I encountered when installing the licenses indicated that the installation was not successful.
#Symantec backup exec 2010 r2 tape drivers driver
The VFF driver is installed when you install any of the following Backup Exec agents or options: Exchange Agent Active Directory Recover Option VMware Virtual Infrastructure Agent Microsoft Virtual Server Agent Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-4609 Here is the error in the backup job log:Ĭompleted status: Failed Final error: 0xe0001201 – For this operation, the Backup Exec Virtual File Filter (VFF) driver must be installed on the media server. I ran into a few problems during the upgrade process, including one that caused the nightly backups to fail. So, you could just run your backup job (which gets the VBK current), then back the VBK up to tape without deleting it.In my previous post I upgraded from Symantec Backup Exec 12.5 to Symantec Backup Exec 2010. If you just keep that VBK in place, every backup job that runs after the initial is updating your VBK to a current level.
#Symantec backup exec 2010 r2 tape drivers full
Since that particular "job" in Veeam was expecting a full VBK to already be in place, you might get errors trying to run it again - meaning you'd have to also re-create the backup job, then recapture a full VBK to get your next backup. You could delete a VBK after it is backed up on tape, but then your next backup job would have to be a "full" backup, rather than just another incremental. That was a revelation for me, too bad it took me a week to figure it out! It appears its actually almost opposite this - the VBK contains the NEW data, and the VBR's contain the snapshots of the "old" data. I thought that all new data was going into the VBR/VIB files. I thought that since the VBK was created initially, it would only contain data that matched the data WHEN it was created. That's the piece that really confused me for awhile with Veeam. The VBR/VIB are the files that have the data for your snapshots. The VBK will always be there, because that IS the backup file. Again, I'm learning myself here, but I think this is true: