Catalogue Reporting from Backup Exec 12.5
Hello time-travelers, No it's not 2010. No need to adjust your clocks. What's the easiest way to run a discovery report on the Backup Exec 12.5 catalogue please? Are there any native or 3rd party tools that could help the discovery? Looking for simple information about: * Names of clients with valid backup images in the catalogue. * Date ranges of valid backup images in the catalogue. * Any data restores performed in last 2 years. Background: We have a legacy Backup Exec 12.5 platform running on Server 2003 that's been sitting idle for a number of years. The last backup image was created about 2 years ago, so it definitely has valid images. We have finally decided to decommission the old platform, but our Risk team wants to know what data is still being held on backups before they'll sign off on the "early" destruction. Thanks in advance for any advice.884Views0likes0CommentsBackup Exec 9.1 Driver Download
I had a tape drive fail and need to recover data. My new drive is a Certance LTO-2 drive, and from what I read, I need the file originally linked to be atBackupExecTapeDeviceDriverInstall_273853.exe in order to get this drive working. How do I get that file? Thanks.742Views0likes2CommentsRestoring single VMDK
We've restored a single VMDK with it's VMX file to the backup media server, uploaded that to the ESX VM host, added it to a powered down server and attempt to power on the server, but get message: "Unsupported or invalid disk type 2 for 'scsi0:2'. Ensure that the disk has been imported." ... "Unable to create virtual SCSI device for 'scsi0:2' " Is there anything special I need to do when requesting the restore to have a usable VMDK file or a step after the restore from tape step? Was running BE16 at the time of restore for this example. Upgrading to 20.3 right now. But I doubt the process changed. Using vSphere web clientVersion 6.5.0.20000 Build 9451637 My goal is to get a file out of a VMDK based backup by attaching restored VMDK to a non-critical server. This has never worked for me, so I'm obviously doing something wrong.1.9KViews0likes4CommentsExchange backup nearly always fails now after destination change
Hi, I have been backing up Exchange to another server for a long time with no issues. We have started to get low on space on the destination server so had to change the location of the backup. The new backup is an external hard drive on a different server. The backup seems to run through fine (takes 2hrs as normal) and I get a ~ 80GB backup placed in the destination. However Backup Exec always reports as 'Failed' with errorExchange_Backup_Job<noscript> e00084af - The directory or file was not found, or could not be accessed I don't understand because the server CAN see the destination folder (and has full access to be able to delete old versions of the backup) but it always fails now. Note: When I changed the destination initially it failed the first few times then worked. I've tried 25 times and it has been successfull 6 times. So it doesn't appear that it is a setup problem. Could anyone advise what could be wrong please? Thank you738Views0likes1CommentVSS Snapshot error
Hi Guys, Kindly please assist I am currently facing this issue for the past 3 weeks now. VSS Snapshot error. Out of disk space, or could not find an NTFS volume while creating the snapshot. Microsoft Volume Shadow Copy Service (VSS) requires an NTFS volume with enough free disk space for each physical or virtual disk volume to cache the data that changes during the backup job. I tried everything, Yes the backups are still failing. Please assist me with this.895Views0likes2Comments