I'm not Scott, but yes, your conclusion is correct. //Oscar -- Note: To sign off this list, send a "signoff networker" command via email to listserv AT listmail.temple DOT edu or visit the list's Web
Now our Exchange 2K IS savesets are failing. Any ideas what might cause this? Thanks, -Josh * exchange.semaphore.lan:MSEXCH:IS savegrp: suppressed 1 lines of output * exchange.semaphore.lan:MSEXCH:IS
Author: "Narkinsky, Brian" <Brian.Narkinsky AT DEP.STATE.FL DOT US>
Date: Thu, 21 Aug 2003 12:53:16 -0400
There are missing transaction log files since the last full backup. Perform a full backup. Brian Narkinsky System Manager Department of Environmental Protection MS 6520 2600 Blairstone RD Tallahassee
Missing full backups will cause the unknown error, and cause the backup to fail? All I need to do is run a full backup and it will fix the unknown error and let those backups succeed? -Josh == Joshua
Author: "Narkinsky, Brian" <Brian.Narkinsky AT DEP.STATE.FL DOT US>
Date: Thu, 21 Aug 2003 13:18:45 -0400
No something outside of the Exchange backup APIs, deleting the transaction logs and then trying to perform an incremental backup will cause this error. A full backup doesn't really care if all the tr
Okay, that makes sense. So how do I fix the problem...run a full backup? -Josh == Joshua Close Office: (206) 905-5031 Network Administrator Mobile: (206) 510-2452 CCNA / CCDA Semaphore Corporation ==
Author: Scott Bingham <sbingham AT LEGATO DOT COM>
Date: Thu, 21 Aug 2003 10:30:18 -0700
Hello all, Josh: This might be an indication of a serious problem in the Exchange Server, and should be investigated. A full backup is indeed a good place to start. If it also gives errors, then you
Thanks a lot guys. I will do some investigating, run a full backup and get back to you. The log files you speak of, what log files are they, were are they located? Are they the applogs in the nsr dir
Author: Scott Bingham <sbingham AT LEGATO DOT COM>
Date: Thu, 21 Aug 2003 12:37:03 -0700
[Resent because my first attempt, with all of the replies, was rejected by the List as being longer than 500 lines long.] Hello Brian, Sorry -- this is not quite right. *All* of the logfiles are back