AD GRT - vmware snapshot
Hi, this must be a subject discussed countless of times- regardless I havn't quite found the answers I was looking for. I am trying to figure out if I can and should backup Active Directory using vmware snapshots, and if it is possible to use GRT with snapshots. this article firmly states against it: http://techgenix.com/dont-snapshot-domain-controllers-96/ however this old thread I found: https://vox.veritas.com/t5/Backup-Exec/Backing-up-AD-in-a-VMWare-VM-Using-GRT-Causes-Job-Warnings-Safe/td-p/529685 suggests it's fine to use snapshots to backup AD. moreover it suggest that with"active directory agent license installed on the media server" I will be able to use GRT. so I am left with two main questions: 1) can and should I backup AD with vmware snapshots? 2) what is this "active directory agent license installed on the media server"- does RahulG mean a regular netbackup client installed on the DC or is it an actual agent on the media server capable of expanding the snapshot to restore single users or etc.? thanks in advanced for the helpSolved3.8KViews0likes7CommentsBackup Exec 16 - Temporary VMware folders are not cleaned from the Backup Exec data directory
HI All, So we started with Backup Exec 14 few years back and I've updated to BE 16 last week with latest patch due to following issue when Symantec could not resolve it. Issue: When backup up VM's, there are lot of Temporary folders been created in folder C:\Program Files\Symantec\Backup Exec\Data. (Folders name include VM's name and date ), and number of folders been created keep growing everyday. Troubleshoot done: I've logged a call with Symantec and for a week they did troubleshooting and today an Advanced tech called me and advised that this is a known issue and only work-around is to delete these folders manually ? Now I have had the same above issue while we were on BE 15, with all the patches installed, hence why I quickly upgraded to BE 16 to see if that resolve the issue. Symantec advance support tech directed me to this article ( https://www.veritas.com/support/en_US/article.000023219 ) which is according to the article was an issue on BE 2014. So I don't believe that Backup Exec 16 will have this now, will it ? And I can't accept an answer been deleting these folder manually every day as a solution. Does anyone experienced this kind of issue ? Cheers3.3KViews0likes3CommentsBackup Exec 16 Exchange GRT backup error with deduplication
After windows in place upgrade from windows server 2012 R2 to 2016, and BE services started normally and all job are running successfully, except Exchange and VMware GRT backup failed with the following error. Final error: 0xe0001203 - An error occurred while creating or accessing the directory specified for this operation. Check to make sure that the B2D folder and/or the temporary path specified for this operation are valid. V-79-57344-4611 - An error occurred creating or accessing the directory \\.pdvfs\servername\2\BEData specified for this operation. Ensure that the directory is accessible and can be written to. I changed storage from deduplication disk to tape drive and job success . FP 2 and latest HF 128051are installed .Solved3KViews0likes3CommentsBackup Exec 2014 VRAY - Granular Restore Problem via Disk Based Backup
Hi there, I've read lots of posts on this forum and cannot find a solution to the exact problem I'm having, so I'm hoping someone here can help. I'm not a Backup Expert (clearly:smileyhappy:) and I've just run out of ideas. I'm using Backup Exec 2014 VRAY with all updates, service packs, hotfixes installed on a Windows Server 2012 R2 Virtual Machine (VMWare 5.5).We run 2 backups on our site - a Tape Based backup where the tape gets taken off site (requirement of management), and a disk based backup. I regularly have to restore individual files from one of our file servers (virtual machine) from the disk based backup. I would like to be able to restore the individual files from the disk based backup, rather than having to stage the entire virtual machine somewhere first. As I have understood from what I have read, you should be able to restore at granular level with disk based backups, but not from a tape based backup for obvious reasons. I have the following options enabled on the backup that are related to GRT. I have tried two ways of restoring : 1. Right click on the server in the server view > Restore > Files, Folders or Volumes > File and Folder backups from a backup set > Enter the date range and find the file I want to restore > This wants to stage the VM before restore 2. Click on the VMware Cluster > Right-click on the server in question > Restore GRT-Enabled data for the selected virtual machine > Files, Folders or Volumes > File and folder backups from a backup set > Enter the date range and find the file I want to restore Whichever way I try, seems to want to stage the VM first, which takes a huge amount of time. Apologies if I have not supplied enough information, I am happy to post anything else that is needed to help diagnose this issue. Thanks for taking the time to read Best regards James2.7KViews0likes10CommentsEnable file recovery for VMware virtual machines
NetBackup has a feature calledEnable file recovery from VM backup thatallows the restore of individual files from VMware virtual machine backups. How is this any different than using GRT? Can you use GRT on a VM and restore a single file from a snapshot backup?2.4KViews0likes3CommentsBackup Exec 16 and GRT restore MS Exchange 2007
Hello guys. I have new-installed Veritas Backup 16 (on Windows Server 2012R2) I have MS Exchange 2007 on Windows Server 2003 R2 x64bit I configure everyday B2D-job with full backup of MS Exchange bases with GRT (only Exchange-bases no any other files) And I have two problems with it 1. Every job is finished with error V-79-57344-65193 for some of Information store (not for all, only for two from three). I check this article in KB and do all reccomendations but no result 2. When i try to restore any item from GRT-backup (for example one email) i get BROWSE FAILURE. The volume that is used for the staging location must be a writable NTFS volume that is local to the Backup Exec server. Also, the volume must have the same sector size as the volume from which the Exchange log files were backet up. or for some cases the next Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-546 The log file sector size does not match the sector size of the current volumn. " I check sector size for Exchange Server and for Backup Exec server(special folder on local disk, which i point GRT-restore path in Global Settings Backup Exec. Exchange: Bytes Per Sector : 512 Bytes Per Cluster : 4096 Bytes Per FileRecord Segment : 1024 Backup Exec: Bytes Per Sector : 512 Bytes Per Physical Sector : 4096 Bytes Per Cluster : 4096 Bytes Per FileRecord Segment : 1024 So it looks like the same. Anyone can helps me to understand what i'm doing wrong?Solved2.2KViews0likes4CommentsStaging & Hyper-V restores
This article-- https://www.veritas.com/support/en_US/article.000075462 --leaves me with a few questions: "Tape backups require a staging location that is at least as large as the data that you back up." The way I read this, restore requires enough space for all data in the backup job. But to be able to do a GRT restore from any arbitrary VHDX, we need enough staging space for the largest VHDX backed up, plus 1GB for GRT metadata. Correct? A non-GRT DR restore (restoring an entire Hyper-V host) requires no staging space at all, even if the job was GRT-enabled during backup. Correct? A non-GRT VHDX restore (restoring an entire VHDX) requires no staging space at all, even if the job was GRT-enabled during backup. Correct?Solved2.1KViews0likes4CommentsBackup Exec 16 cannot recover single elements from virtual machines using GRT
I'm using Backup Exec 16 to backup 2 Vmware virtual machines with Active Directory and Exchange 2013. I have noticed that even if i have enabled GRT in the job options i can only restore the whole vmdk. I cannot restore single elements from Active Directory or Exchange using GRT. Both virtual machines have the backup exec agent installed. I'm using the default Microsoft VSS provider to backup the virtual machines. Jobs successfully complete without errors. I cannot understand why the backups aren't granular.1.9KViews0likes4CommentsBackup Exec 15 - FP5 - 2012 R2 Hyper-V Cluster - GRT Backups Stuck in Snapshot Processing
Hello all. We have a 2012 R2 Hyper-V Cluster, all patched to date. This cluster has 6 nodes, each one connected via FC to a 3PAR 7400c All-Flash array. Each cluster node hosts about 20 VMs and 2 or 3 CSV (so each VM role has direct access to their storage via FC as it is its own Coordinator Node). With that in mind, we installed BEX 15 FP5 in each cluster node so that we could backup the VMs directly through FC and not via Ethernet (it's way faster and we do have a lot of data). Since implementation, eveything is going smooth (with some issues sometimes) with all cluster nodes except one. Every cluster node has either a FC Tape Library or a SAS Drive (all LTO6/LTO5, all firmwares up-to-date). This cluster node, VHT06, shows erratic behavior. It starts the granular job, but hangs in a random VM in "Snapshot Processing". We can't cancel the job unless we stop the "vmms.exe" service or reboot the cluster node. If we manage to cancel the job, the VM gets stuck in "Backing up..." within Hyper-V manager and can't reboot. We thought it could be the tape library, so we changed it. Still the same issue. We even evicted and reprovisioned the cluster node two times. Backup through RAWSworks fine. Marco1.9KViews0likes2Comments