Incapsula incident ID: 259000520169829023-566046783772492617 Only in our industry can you release a product that you say does something, and then nothing happens to you when it doesn't, it makes me very sad, angry, frustrated, annoyed Backed up 1 virtual machines Backed up 1 virtual machine disks Processed 5,582,513,528 bytes in 2 minutes and 38 seconds. View solution in original post 0 Kudos Reply 2 Replies See whether this document pkh Moderator Trusted Advisor Certified 08-20-2012 06:39 PM Options Mark as New Bookmark Subscribe Subscribe to RSS
Please type your message and try again. 1 2 Previous Next 16 Replies Latest reply: Jul 27, 2010 6:03 AM by scottziehr Symantec GRT does not work with VSphere gbh66 May Restores that use Granular Recovery Technology may not be available from this backup set. Restores from Full backup sets located in the deduplication folder are not affected by this issue Thanks. 0 Kudos Reply Does it happen on all the ArulPrasad Level 6 Employee 11-26-2011 07:40 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Mostly, they've collected logs and told me they're waiting for Engineering to get back to them. https://www.veritas.com/support/en_US/article.TECH69498
This option is applicable only when you restore individual items under the following conditions: The backup of Microsoft Hyper-V, Exchange, SharePoint, or Active Directory, or of VMware Virtual Infrastructure was enabled so forgive me if seem a little tired and cross.We upgraded to vSphere a little over 2 weeks ago, and the upgrade went very well, except in one area. One of this is ending with this exception every time of Full or incremental backup. Thanks again for the feedback guys, it's been the only useful info I've had.
No Yes Did this article save you the trouble of contacting technical support? On what else could thy be based on ? In such case, try the following suggestions: Install the Backup Exec remote agent on the OS that the independent disk is assigned to and backup the files/folders through that agent.Do not Restores that use Granular Recovery Technology may not be available from this backup set Solved Go to Solution QuentinF Level 3 08-02-2013 07:34 AM Options Mark as New Bookmark Subscribe Subscribe
I havent finished testing, but wanted to update you while you still cared Now to the real question, does the patch fix the problem, yes, yes it does. Sorry, we couldn't post your feedback right now, please try again later. Here are the steps: In Backup Exec 2010, Click on 'Tools' menu, then 'Install Options and Licenses keys on this Media Server'. Enter a location where Backup Exec can stage temporary data during GRT-enabled backup jobs. Ensure that the location is an NTFS volume and that it is not a system volume.
if so try changin the password without the "&' symbol and try the backup Ensure That there is No Cd/DVD images or iso is Mounted Try to reinstall the VMware tools https://www.veritas.com/support/en_US/article.000024840 Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem You may encounter this issue if your staging location does not have enough free space V-79-57344-38366 Solved! Mountune Does You Vcenter backup account has a Password containing the "&" symbol?
Thanks - IntegIS Like Show 0 Likes (0) Actions 13. I can't say at this point that this is a Symantec issue or user error. While using AVVI plugin, I am simply trying to get an image level backup, with GRT file level at the same time. Both contained Dell drivers.
I've run backups without Advanced File Open run jobs to backup just the affected virtual machines, rebooted everything from VMs to hosts to the backup exec server. The backup is on a tape. I'm using the SAN & NBD transport modes.
Also having occasional issues with the snapshots just freezing and i have to manaully cancel them and consolidate the vms. 0 Kudos Reply On the backup jobs for lmosla Level 6 Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview You may also refer to the English Version of this knowledge base article for up-to-date information. Re: Symantec GRT does not work with VSphere RobertPRAG Jul 8, 2010 6:21 AM (in response to scottziehr) Hi Scott,I've just tested a file restore to one of my virtualised servers
Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? and it failed but I've now tried a restore from a full backup and It worked. Thank You! Re: Symantec GRT does not work with VSphere scottziehr Jun 8, 2010 1:23 PM (in response to gbh66) I came across this post doing some research, waiting for Symantec support to
Re: Symantec GRT does not work with VSphere RobertPRAG May 21, 2010 4:26 AM (in response to gbh66) Hi Graham,I was going to attempt to build a Windows Server 2003 VM BEREMOTE: [07.31.13 11:04:55]   07/31/13 11:04:51 [mounter] - VDiskMounter::VirtualizeFiles: just created VirtWrap 000000000AB9D890 BEREMOTE: [07.31.13 11:04:55]  07/31/13 11:04:51 Could not Backup Exec deletes the data when the job is completed. Thanks. 0 Kudos Reply Thanks Nhoj, I notice in Jadeonpax Level 3 11-27-2011 04:23 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a
Maybe this is caused by nhoj_O1 Level 3 11-27-2011 03:11 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Maybe If you perform a file level restore, it writes the backed up VMFS volume to the staging area you specify,then mounts it and restores the selected files. This exception only causes Granular Restore Technology (GRT) not to function properly. http://support.veritas.com/docs/351373 It looks as if they have fixed it.
If you do the same with vSphere backup , nothing gets written to the staging area, then it complains that it cant mount the disk,V-79-57344-38721 - Failed to mount one or Except that it doesnt work with vSphere.The fact that Symantec even need to question whether this is a significant business issue means that they are completely out of touch with the Create/Manage Case QUESTIONS? If the default path of C:\TEMP does not meet these requirements, type a different path on the Backup Exec server where Backup Exec can stage temporary data.
If not try installing the BE vss provider (instlals along with Beremote agent or can be installed manually) 0 Kudos Reply Accepted Solution! No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Vision 2016 Veritas CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical The restore worked perfectly and the two files appeared back on the virtualised server.A little bit of background - my backups are taken to B2D folders and then duplicated to tape,
Veritas does not guarantee the accuracy regarding the completeness of the translation. Can you try to restore from a full set? By doing this it will reinstall all the VMware components that get installed while installing the license. Like Show 0 Likes (0) Actions 3.
Any other ideas?