Alex_Pitzner_2
Level 3
Joined 18 years ago
User Profile
User Widgets
Contributions
Re: Exchange 2003 Incremementals keep failing with 0xe000035e (but full backups work)
eseutil /mh verifies that the database last full backup were done at the exact time Backup Exec runs the full backup job Previous Full Backup: Log Gen: 122164-122165 (0x1dd34-0x1dd35) - OSSnapshot Mark: (0x1DD36,8,16) Mark: 04/23/2010 19:00:17 I took the databases offline and ran isinteg -s <myservername> -fix -test folder on them. It found and fixed a few errors: You have selected First Storage Group / Mailbox Store Continue?(Y/N)Y Test reference table construction result: 0 error(s); 0 warning(s); 0 fix(es); 0 row(s); time: 0h:0m:12s Test Folder result: 0 error(s); 8 warning(s); 313 fix(es); 9211 row(s); time: 1h :20m:22s Now in test 3(reference count verification) of total 3 tests; 100% complete. You have selected First Storage Group / Public Folder Store Continue?(Y/N)y Test reference table construction result: 0 error(s); 0 warning(s); 0 fix(es); 0 row(s); time: 0h:0m:4s Test Folder result: 0 error(s); 0 warning(s); 16 fix(es); 786 row(s); time: 0h:8 m:13s Now in test 3(reference count verification) of total 3 tests; 100% complete. I ran isinteg again but there were no errors of warnings anymore. I tried another Incremental backup and it failed with the same error.983Views0likes0CommentsExchange 2003 Incremementals keep failing with 0xe000035e (but full backups work)
Backup Exec 2010 running on Windows 2008 R2 64 bit Exchange 2003 running on WIndows 2003 server Full backups run correctly (Ihave them running once a month) Incrementals always fail saying "The Backup Exec Agent for Microsoft Exchange was not used to create the last full backup of this database. You must use the Exchange Agent to run a full backup before you run a differential or incremental backup. " The incremental fails at night even when Ihave run a full backup that same day. Nothing else is trying to backup Exchange.983Views0likes6CommentsRe: SQL Error when backing up and selecting resources
I'm having the same trouble. I have a clustered SQL 2005 installation on (2) WIndows 2003 EE nodes. These nodes are on a different subnet than the backup server but there are no ACLs or firewalls which would prevent them from communicating. I can see the nodes in the selection list, but not the SQL virtual server instance. Therefore I cannot select it to backup. Note: This was working at some point b/c I have a selection list called SQL2005_DBs which DOES have the clustered virtual SQL server instance name in it. However, the backup fails when it tries to access it and the clustered virtual instance name (HUSQLSVR) no longer appears in the Windows Network Domain list. It has been more than 2 weeks since brendonlee's initial post. Does anyone moderate these boards ?298Views0likes0Comments