Backup Exec 2014 Exchange 2010 -515 The Timestamp in the next log does not match the expected timestamp
I keep getting this error on my Backup to Tape on Backup Exec 2014. Cannot Extract Mailbox messages from exchange backup. Review the job log for more information. When I do I get these V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-515 The timestamp in the next log does not match the expected timestamp. & V-79-57344-915 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-1018 There is a checksum error on a database page. ' So far I tried changing the exchange options from High Availability Server from passive to active copy. And that didn't work so I changed it back. I read around that you can disable GRT but what exactly is that? Also what do I loose disabling that versus enabling it? Here's some more info about my servers Backup Exec 2014 64bit 14.1 rev 1786 hotfix 218257 Server 2008 rs Enterprise 24GB Ram Thanks for the help in advance
problem with LTO 5 tapes in bexec 2012 r3
I'm having a problem with a 800GB LTO 5 tapes in bexec 2012 r3, I appear in a closed circle label support and I can not write to them. the problem is that I have 5 blank tapes in my unit, I can see his ability tells me that are writable, but to run a job on the support group fails. Annex image if anyone can help me or tell me, and I read the manual and I can not get to the problem.
Failed Final error: 0xe00084bd - The system cannot find the path specified - unable to restore file or directory.
Hello I can't backup only this Vm with Backup Exec 2014 since a very long time. They are no snapshot existed in snapshot Manager. When i select manually only one VM using snapshot technology .. Could you help me ? it says always .. And after the message appears.... ANd, Why it talk about restore ? I giev a backup not arestore. Error : e00084bd - The system cannot find the path specified - unable to restore file or directory. See the job log for details. Agent used : Yes Advanced Open File Option used : No
BE 2012 SP4: deduplication cataloging: V-79-57344-33997 + V-79-57344-33029
Hello, I already posted our problem here: https://www-secure.symantec.com/connect/forums/be2012-sp4-expiration-date-set-one-year-after-exipration so far nobody replied. We still have this problem that all backupsets which expire get a new expiration date roughly one year later. Eg: A full backup with a retention period of 3 weeks made on the 31.1.2015 expires on 21.2.2015. Shown correctly yesterday, today the expiration date of exactly the same backup set has a expiration date of 13.2.2016. So we have to manually intervene quite regularily deleting old backup sets otherwise our deduplication backup runs full because old backups are not deleted. This costs us a lot of time. Under Settings -> Database Maintenance, the database maintenance is enabled, delete aged data is enabled and all other options are enabled as well (perform database consistency check, save contents of database to the backupexec data directory, optimize database size). We installed all updates via live update already a long time ago (roughly since summer 2014 there are no more updates ...) I already ran the extensive database repair based on this article: www.symantec.com/business/support/index?page=content&id=TECH67239 But the problem didn't go away, still "should be expired backup sets" get a new exipration date next year. Recently I tried to recatalog the deduplication storage to find all old backup sets which can also be deleted and hoped that probably doing so might also solve this strange problem. I did that by following the standard procedure (stop all services, rename Catalog map, run Catrebuildindex -r , start all services and catalog again via the GUI). But now the cataloging fails and I get a lot of the following errors: In Job Operation - Catalog I get: Drive and media mount requested: 2/14/2015 10:42:18 AM V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {xxx-xxx-xx-xx-xxxxx} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. and then in the errors section I get: Catalog- An error occurred during translation of data to or from the storage media in b2d_deduplicated:1. V-79-57344-33997 - The data being read from the media is inconsistent. Null backupset. Possible reason: Cataloging SW Compressed ArcServe Tape. Backupexec does not support this operation Can somebody clarify this situation? There is no backup job having a retention period longer than 4 weeks (tape), all disk-based backup jobs have 3 weeks as retention period: also during the period the backup sets should be retained, the expiration date is set correctly. Also the wrong expiration date is continuously put forward into the future (see my old post where the wrong expiration date is set to september 2015, now it is set to february 2016. So what can cause such strange behaviour? And how can I at least get a cataloging finish succesfully?BackUp Exec 2012 - tape/slots which tape takes precedence
I'm running Backup Exec 2012. My system is set to run a full backup (Fridays) and incremental (Mon-Thurs) I am under the impression that when you have many overwritable tapes is the drive, the system will first look for tapes that has matching media set, and ifthere isn't any, it will look for scratch media. When it looks for scratch media, it will look for the one with the oldest date in "Allocated Date". Am I right on this? But on a few ocassions it has not followed this "rule". I'm attaching a screencap of my backup from last night. As you can see from the Allocated date, on Monday I scratched and labelled all tapes in order from Slot 1 to 5. I did this so that the allocation date will be in sequence. But somehow yesterday (Tuesday) it skipped the oldest allocated tape and took the second oldest tape. Any idea why?