Exchange 2003 r2 backup, full works incremental fails.
Created: 06 Feb 2013 | 9 comments
Hey.
I have a Backup Exec 2012 server, and i want to take backup of our exchange 2003 r2 server. Full backup works perfectly but when it try to do incremental backup it fails because of licensing? shouldnt both fail or do you only need license for Incremental and diffriental backup?
Discussion Filed Under:
Comments 9 Comments • Jump to latest comment
Hi,
Nope, never heard of this. An Agent for Databases and Applications license covers Exchange. Your backup regime doesn't matter...FULL/INCR, combination of them, it's all the same.
Uninstall the Exchange license and reinstall it and try again.
Thanks!
If you find this is a solution, please mark it as such.
I have license for databases and application, but cant see Exchange backup agent in my license summary. Im gonna try doing a full backup again on exchange and see if i get the same error again.
And in the full backup set i have granual restore from mailboxes. But when i try to do a incr backup it says the Exchange agent wasnt used to complete that backup.
If you can't see the license, did you install it? Stupid question but....
For the error you quoted above, check the TNs below:
http://www.symantec.com/business/support/index?pag...
http://www.symantec.com/business/support/index?pag...
Thanks!
If you find this is a solution, please mark it as such.
Thanks! that helps alot, i havent tried yet, but that just may be the case!
Thanks alot for the help, ill check it out tonight
Seemse like it worked, but now the job have been standing on updating catalogs for 9 hours....
...make sure your BE media server is fully patched with SP1a & any subsequent patches, and that these are push-installed to any remote servers.
Are you perhaps backing up to a dedupe folder?
If you find this is a solution, please mark it as such.
The backup is going to a DataDomain storage solution, and yeah its a dedup storage. Hardware dedup though
...try running the backup to a local B2D and see if you get the same error.
Thanks!
If you find this is a solution, please mark it as such.
Would you like to reply?
Login or Register to post your comment.