Simplified Disaster Recovery Wizard doesn't show backup sets
Hi Guys, I'm trying to restoe a server using SDR. However, when I get to the screen where you choose your backup sets, nothing is displayed in the "Point in time" list. This was the same tape I used about a month ago and it was working fine. I have cataloged tape and it does show all the backup sets if you do it from the BE 2012.(see below) Does anyone know what could go wrong? I have tried a lot of thingsbut couldn't get the backup sets to show up in SDR wizard!3.6KViews1like10CommentsFalha ao fazer backup dos dados
O meu cliente tem problema com o fechamento do ciclo do back up. Recentemente adquiriu um conjunto de licenças para garantir o backup dos seus dados cujo volume é de aproximadamente 10TB, considerando: 13667-M0246 - BACKUP EXEC CAPACITY ED WIN 1 FRONT END TB ONPROMISE STANDARD LICENSE+MAINTANCE BUNDLE QTY 2 TO 5 INITIAL 12MO CORPORATE. 3*12574-M0242- BACKUP EXEC CAPACITY ED WIN 1 FRONT END TB ONPROMISE STANDARD LICENSE+MAINTANCE BUNDLE QTY 2 TO 5 INITIAL 12MO CORPORATE. 3*13667-M0242-20- BACKUP EXEC CAPACITY ED WIN 1 FRONT END TB ONPROMISE STANDARD LICENSE+MAINTANCE BUNDLE QTY 2 TO 5 INITIAL 12MO CORPORATE. A minha dúvida, é se o cliente comprou licença errada, e é possivel a partir da licença atual, efetuar upgrade que possibilita atender o problema. Obrigado525Views0likes1CommentNIC Teaming Slow Throughput, any ideas?
Hey guys, We currently have 2Gig set up through NIC teaming for our backup exec setup.When we have backups running, it barely reaches 35-40% of the bandwith. I am using Backup Exec 2010. Has anyone else here set up NIC teaming before? What are some things that might cause slow performance? Are there any specific settings in Backup Exec that may help? Thanks!5.2KViews3likes9CommentsDisaster Recover: Error 183
Hey Symantec, The name is base & and I need a little help. I have an issue with one of my backup jobs reporting the following error: Backup- \\*.*.com\System?State - Error loading disaster recover information file. Error: 183 Cannot create a file when that file already exists. V-79-57344-41488 - Due to one or more errors in \\*.*.com\System?State this backup cannot be used for conversion to Virtual Machines, Simplified Disaster recovery, or a complete online restore. I'm still troubleshooting items one by one, but I haven't been able to fix this problem on my own. Any help that can be profided is greatly appreciated.1KViews0likes3CommentsServer List Not Refreshing in Backup Exec 15
We are currently running Backup Exec 15 (Version 14.2 Rev. 1180 640bit). We run muliple jobs daily and have recently increased the number of jobs. The issue we seem to be having is that the Server list statuses are not being refreshed or udpated. So for example, I will recieve and email that Server1 completed successfully. But when I log into the BE server and actually view the server list, it still shows that job and other jobs that have either run successfully, failed or cancelled to still show as Active - even though they are not. Closing BE 15 and reopening does not fix this. So the questions are: Why is this happening? Is this a BE service related issue? Anyone else experience this and if so what did you do to resolve it?Solved2.9KViews1like6CommentsBackup Exec 2012 Tape Restore Media ID Mismatch
Hi All, I am trying to restore data that is on 2 Tapes which were written to by using a Dell Powervault 124T. We currently use Backup Exec 2012 Small Business Edition. The Tapes have no barcode however the AutoLoader does have a barcode reader. When we Inventory and Catalogue the tapes they are being given a Media ID however when we come to then restore the data we get an error saying that the Restore failed due to Invalid Physical Volume Library Media Identifier. Above the error it notes a Media GUID which doesnt match the Media ID the Tape has been given. See Images below. How do we get them to match or are we inventorying or cataloging the tapes incorectly? We have stopped the services and renamed the catalogs folder numerous times and this doesnt seem to fix the issue. We can see the Backup Set on the tapes and browse the folder structure however we always get the above failure error. Any assistance would be extremely helpful as we have been trying to restore this data for 1 week and time is now of the escense? Thanks Ben1.7KViews0likes18CommentsAjuda para restaurar backup sem ponto de recupeção
Olás amigos. Preciso de uma ajuda. Em meu servidor o ponto de recuperação foi perdido e o backup todo está em formato *.fbf Como restauro esses arquivos de backup? Uso Bkp Exec 2010. Obrigado!! Hellos friends. I need help. In my recovery point server was lost and the entire backup is in * .fbf How do I restore these backup files? Use Bkp Exec 2010. Thanks !!2.2KViews0likes4CommentsSystem State Backup Problem (Final error: 0xe0000352)
Hi Experts, I'm using Windows Server 2008 R2 Ent, 64bits and Symantec Backup Exec 2010 R3. One of my backup jobs for system state has been failing with the following errors: -> Job ended: Monday, April 20, 2015 at 6:46:11 AM -> Completed status: Failed -> Final error: 0xe0000352 - The specified volume does not exist. Recreate the volume, and then try the job again. -> Final error category: Resource Errors -> For additional information regarding this error refer to link V-79-57344-850 No problem backing up other data, only system state. Had checked "vssadmin list writers" and no errors. Had searched and google around, but still could not find any solution yet. Can anybody help me? Thank you. - Blue835Views0likes3CommentsV-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib.
Hello Everyone, Currently we have a server 2008 64bit server with BE 2014 which was upgrade from 2012 and for some strange reason I keep getting this particular error message while backing up a few VMs as you can see below. V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib. VixDiskLib_Read() reported the error: NBD_ERR_DISKLIBV-79-57344-38366 - WARNING: "VMVCB::\\10.0.1.5\VCGuestVm\(DC)ha-datacenter(DC)\vm\SCSMDW\SCSMDW\SM Warehouse-000002.vmdk" is a corrupt file. This file cannot verify. Transport mode 'nbd' was used for the read operation of the disk 'SM Warehouse_1-000002.vmdk' In addition, I have research this particular message and I have not yet found anything online that is exactly what I am having issues with. Furthermore to provide additional background information the issue that I am having with the VM are on an Exsi host that is running version 5.5.5.6KViews0likes17Comments