Falha 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. Obrigado
Backing Up Backup Exec Itself
I'm seeing a lot of conflicting information while Googling in regards to backing up the BE server itself, so I wanted to get updated info for version 15. Is it the correct way to simply to use run a Backup Exec job and protect the following folders? CATALOGS C:\Program Files\Symantec\Backup Exec\Catalogs DATA, DATABASE, and JOB LOGS C:\Program Files\Symantec\Backup Exec\Data LICENSES C:\ProgramData\Symantec Shared\Licenses Obviously this means BE services are running while it's backing up itself and should be done outside of the nightly database maintenance window. Thanks in advance
V-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.
B2V Restore Issue
Hello Guys, I am having a problem trying to restore a Full backup set from a VM with an agent onto an EXSI host. Below are the steps that I have done and I will also be including the screen shots of the job selection, backup options, and error message that I am getting below. Any help would be greatly appreciated. Things I have done so far. 1. Inventory and Catalog the tape. 2. Made sure what I want to restore is on those tape. 3. Select Convert to Virtual from a Point in Time 4. Select the appropriate backup options and attempt to run the job.Importing Catalog from Backup Exec 2014 to another 2014 server
Hello Everyone, I was wondering if anyone has ever tried this and would it worked to import the backup exec catalog file from Server 2008 r2 Standard to another server of the same configuration with the same version of Backup Exec and were there any problems during/after the attempt.
System State Restore Error
Manual restore of single server 2008R2 DC. DC is also the Media Server. Followed the Administrative guide and when I get to the system state restore I get an error. Here is the log showing the error, it is similar to the restore 2008 DC that is in 2003 native mode but this is the first and only DC and was created with 2008 R2. I am running backup exec 2012 (version 14) Build 1798 BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.019 [fsys\shadow] - Restoring SYSVOL as primary BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.019 [fsys\shadow] - Status Unknown (0x00000424) initializing FRS interface for Component 0eeda0a5-150c-487f-bd1289e7ef847231 in SHADOW::PerformPostCustomRestoreMethods BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.019 [fsys\shadow] - Status FS_CUSTOM_RESTORE_FAILURE (0xE000FED7) returned performing Component '0eeda0a5-150c-487f-bd1289e7ef847231' custom restore methods in SHADOW::CloseComponent BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.019 [fsys\systemstate] - AD:Status FS_CUSTOM_RESTORE_FAILURE (0xE000FED7) calling FS_CloseObj in SystemState::CloseObj:104 BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.030 [ndmp\loops] - LP_ENV::MsgError: error 0xe000fed7 processing object SYSVOL\SYSVOL\0eeda0a5-150c-487f-bd1289e7ef847231 BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.030 [fsys\shadow] - Informational: Creating Writer 'System?State\Task Scheduler' BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.030 [fsys\shadow] - Informational: Opening Writer 'System?State\Task Scheduler' BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.030 [fsys\shadow] - Informational: Closing Writer 'System?State\Task Scheduler' BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.031 [fsys\shadow] - Informational: Creating Component 'TasksStore' BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.067 [fsys\shadow] - Informational: Opening Component 'TasksStore' BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.521 [fsys\shadow] - Informational: Closing Component 'TasksStore' BEREMOTE: [11/21/13 06:59:07] [6024] 2013-11-21T06:59:07.521 [fsys\shadow] - Informational: calling IVssBackupComponents::SetFileRestoreStatus for Component 'TasksStore' in SHADOW::CloseComponent Any help would be greatly appreciated