β03-29-2013 03:28 AM
Hello, I'm trying to setup netback to backup exchange archive database. All other backup:sql, vmware and dag services are ok. But we have dedicated exchange server with 2 archive databses and backup of it failed with error: An existing snapshot is no longer valid and cannot be mounted for subsequent operations(1542). I already try bpfis query and it empty:
INF - BACKUP START 6204
β04-01-2013 02:59 AM
Any help appreciated!
β04-01-2013 04:45 AM
1.Which Netbackup version you are using?
2.Have You configured Netbackup Master and Client properties for exchange server correctly? Please follow step by step as described by Symantec on below videos
All versions videos for Exchange backups and restores with NetBackup
http://www.symantec.com/
3.Is NetBackup Client Service running on the Exchange server?
β04-01-2013 04:46 AM
1. 7.5.0.5
2. Yes, my backups of dag db are ok.
3. Of course i check it:)
I suppose that problem in vss but i have no idea what to do more.
Thanks for reply!
β04-01-2013 04:50 AM
I have try this diskshadow script http://www.symantec.com/business/support/index?page=content&id=HOWTO60816 on my archive server and it's create shadow copy of my db ok.
β04-01-2013 04:59 AM
again restart the exchange server and then check, if its Microsoft exchange writers problem
β04-01-2013 05:28 AM
no use. same error
β04-01-2013 07:09 AM
I noticed you had a status code 130 in the log...whenever we had this error during snapshot with Exchange, we usually found a hung bpfis or tracker processes on some of the Exchange DAG servers.
Try stopping the Netbackup services on the Exchange DAG servers and, using bpps, see if there are any hung processes that did not stop. If there are, kill them and then restart the Netbackup services.
β04-01-2013 09:03 AM
Thaks for reccomendation, but with my dag servers backup all ok. my exchange archive server with information store have issue. and i already trying restart all netbackup services, also reinstall it. and many times reboot server at all. all procces works normaly.
β04-02-2013 03:48 AM
β04-02-2013 04:21 AM
β04-02-2013 04:27 AM
in dag is users mailboxes and in information store is email archive mailboxes. i browsed for select for many times so it correct. i try both with and whiout snapshot. without snapshot message that it's unsupported type or something like that. also try different type of snapshots, and error the same.
storage is DD 860 and i have about 20 backup jobs successed every day on it (exchange dag2010, sql,vmware). only 1 problem with this exchange archive db server. i suppose it in connection information store + vss + netbackup problem. but don't know what to try more.
β04-02-2013 04:30 AM
but why should i choose dag if my db in information store on different server, which is not a part of dag?
service - yes, all started wich admin credential
β04-02-2013 05:05 AM
β04-02-2013 05:06 AM
I would try what Mark_Solutions suggests...
Somehow, you are getting mail from the DAG to the Archive Information Store...if it is tied to the DAG through a replication mechanism, the Archive Information Store would be referenced within the DAG.
If it is through some mail forwarding or smtp tap method, then the Archive Information Store is probably standalone and you would configure the policy as such.
Either method, there may be some residual reference to the DAG in the Archive Information Store that may be causing the issue...checking with the DAG name references may help to identify.
β04-02-2013 06:01 AM
Result in attach. Microsoft Exchange Writer in waiting mode, but if i restart information store service and try to backup the error will be the same.
β04-02-2013 06:53 AM
β04-02-2013 10:12 PM
yes of course all systems up to date. i have an idea. i'll try now backupexec job on this server. before i setup netbackup, it was backupexec on it and jobs were done succsessfull. now i reinstall agents and try. let you know later.
>bpfis query
β04-02-2013 10:35 PM
As I supposed, backup exec 2010r3 job on this server begin normally, snapshot were successful created and backup started. So the problem is in netbackup. maybe it have problem in heterogeneous infrastructure? Because I have dag servers and dedicated standalone servers with mailbox database in my Exchange enviroment?
β04-03-2013 05:37 AM
I think I should some thing to do with this:
any ideas?