SLP Disk to tape backup size is differs
We have configured, Netbackup with Pure Disk setup. we are taking 17 TB backup. Now customer is requesting us to configure Dupllicate backup to tape for higer retentoin. My question is > i see full backup logs shows 17 TB backup has been completed and SLP duplicate jobs shows only 3.8 TB of data writen and no errors found. I need to know why. need some answers.
Necesito saber como calcular el espacio de Jobs en cintas
Necesito ayuda para asesorar a un cliente que me pide lo siguiente: --> Necesitamos también que nos preparen una estadística de espacio que ocupa en cinta los Jobs y con una extracion mensual cuantas cintas necesitaríamos anualmente. ¿Qué datos necesitaría pedirle al cliente? ¿Hay alguna herramienta para ayudarme a hacer más fácil este trabajo?
BMR on Solaris Multipathing
“Until now, BMR supported EMC Powerpath solution. But the demand for native multipath is increasing, which is a platform-independent technique. To cater to this demand, support for native multipath is added in BMR 7.5 for the Linux platform.” BMR supports only EMC Powerpath solution. BMR does not Support for Native multipathing on Solaris. Question is: When will SYMANTEC Netbackup start support for Solaris Multipathing? A big deploymment was done, and the backup solution was the Netbackup 7.5 but now we came at the point that BMR does not support Solaris Multipathing. in such situation, Customer is surviving and big question mark on BMR Solaris Multipathing.
0xe000fedd, 0xe000037b, 0xe00084af or 0xe000846b errors
When attempting to backup Exchange 2007 resources configured with either Local Continuous Replication (LCR) or Cluster Continuous Replication (CCR), the backup job will intermittently fail with 0xe000fedd, 0xe000037b, 0xe00084af or 0xe000846b errors Problem When attempting to backup Exchange 2007 resources configured with either Local Continuous Replication (LCR) or Cluster Continuous Replication (CCR), the backup job will intermittently fail with 0xe000fedd, 0xe000037b, 0xe00084af or 0xe000846b errors. Error 1. 0xe000fedd - A failure occurred accessing the object list. 2. 0xe000037b - Using the job settings, Backup Exec attempted to back up the passive copy of the Exchange database. However, the passive copy was not available after the Microsoft Volume Shadow Copy Service (VSS) snapshot was performed. Try to run the job again. 3. 0xe00084af - The directory or file was not found, or could not be accessed. 4. 0xe000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent. Cause 1) The 0xe00084af message will only be seen if the Microsoft Exchange properties in the job configuration is set to "Backup from the passive copy Only (job fails if not available)". 2) The 0xe000846b message was seen in an environment where a hardware VSS provider was present. Microsoft has acknowledged the issue. For more information about the issue please contact Microsoft Technical Support. http://support.microsoft.com/kb/982118 Solution There are two workaround to resolve this issue. Workaround 1: Configure an Error Handling Rule in the Backup Exec Console that retries any job that fails with error E000FEDD, E000037B, E00084AF or 0xE000846B. It is suggested that at least 3 retry attempts are made, although the amount is optional. Make sure the rule is set to "Reschedule the job for its next scheduled service". The error codes E000FEDD, E000037B and 0xE000846B can be found under the Error category called "Resource". The error code E00084AF is located in the category called "Job". Notes: This method allows the backup to complete from the Passive Copy of the Exchange database, but relies on the VSS failure being intermittent so should be tested/monitored carefully. For more information on the use of Error Handling Rules please review the content of the Backup Exec for Windows Administrator's Guide. Depending on the job and media set configuration this workaround could consume extra storage media. Error E00084AF can be caused by other job configurations so this may cause retry attempts against other jobs. Workaround 2: This workaround should be used if setting an error handling rule does not solve the issue. Configure the Microsoft Exchange settings within the properties of the backup job so that the setting for "If Exchange 2007 backup source is LCR or CCR:" is specified as "Backup from the active copy only (job fails if not available)". Also make sure there is enough free disk space on the Exchange server for the snapshot to complete, as it will otherwise fail with the error "Using the job settings, Backup Exec attempted to back up the passive copy of the Exchange database. However, the passive copy was not available after the Microsoft Volume Shadow Copy Service (VSS) snapshot was performed. Try to run the job again." Thx Semih SOYKAL
