cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Exchange 2010 archive db backup fail

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

INF - FIS IDs:
INF - EXIT STATUS 0: the requested operation was successfully completed
 
vssadmin list writers before backup attempt is normal, after backup of corse it with waiting state.
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {d3f31f8b-893e-4fa2-9814-200192298952}
   State: [5] Waiting for completion
   Last error: No error
 
 
I already try to reregister vss and reinstall netbackup agent. many times reboot server, but no effect.
 
 
Bpfis log in attach. 
 
 
What should I do? Thanks!

 

33 Replies
Highlighted

Any help appreciated!

Any help appreciated!

Highlighted

  1.Which Netbackup version

 

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/business/support/index?page=content&id=HOWTO41825

3.Is NetBackup Client Service running on the Exchange server?

 
Highlighted

1. 7.5.0.5  2. Yes, my

1. 7.5.0.5 

2. Yes, my backups of dag db are ok. 

3. Of course i check itSmiley Happy 

 

I suppose that problem in vss but i have no idea what to do more. 

 

Thanks for reply!

Highlighted

I have try this diskshadow

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. 

Highlighted

again restart the exchange

again restart the exchange server and then check, if its Microsoft exchange writers problem

Highlighted

no use. same error

no use. same error

Highlighted

I noticed you had a status

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.

Highlighted

Thaks for reccomendation, but

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. 

Highlighted

Just to clarify please - this

Just to clarify please - this is a 2010 DAG and yet your selection is Microsoft Information Store rather than being part of a DAG? Have you browsed to the files selection to ensure it is selected correctly? Also you have selected a snapshot backup type - so two questions here, have you tried it without it being a snapshot type (as your selection is an Information Store and not a DAG) and what is the storage used for that store? Some will call the storages own snapshot technology which won't always work - maybe try setting the snapshot type to 1 (system) to see if that helps.
Highlighted

Have you tried it using the

Have you tried it using the DAG name rather than the mailbox server name and browsing the DAG? Do the mailbox servers have the NetBackup Legacy Network Service set to use the exchange admin account too?
Highlighted

in dag is users mailboxes and

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.

Highlighted

but why should i choose dag

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

Highlighted

Ok - so this is effectively a

Ok - so this is effectively a standalone exchange server not related to your DAG - that is fine then, just that usually Exchange 2010 tends to have a DAG of some sort rather than just a mailbox name, so uses bpresolver etc and if it cannot locate the database it wont work and leaves the VSS writer unstable Can you run the following and show the outputs please: Diskshadow List Writers Status List Shadows All Thanks - just wondering if there is a corrupt shadow left behind somewhere that needs removing to solve this
Highlighted

I would try what

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.

Highlighted

Result in attach. Microsoft

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.

Highlighted

OK - one last attempt for now

OK - one last attempt for now before saying what Symantec will say (that it is a Microsoft VSS issue and you need a rollup package / hotfix - which I have yet to see anyone for whom that has worked! - I assume your systems are all up to date with WIndows updates and Exchange Service packs etc?) ... Can you try bpfis query in case NetBackup has left something behind that needs clearing down
Highlighted

yes of course all systems up

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

 

INF - BACKUP START 7688
INF - FIS IDs:
INF - EXIT STATUS 0: the requested operation was successfully completed
Highlighted

As I supposed, backup exec

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? 

Highlighted

I think I should some thing

I think I should some thing to do with this:

16:34:01.966 [4520.5492] <4> bpfis: INF - Preparing freeze of Microsoft Information Store:\VGK_Archive using snapshot method VSS_Writer.
16:34:01.966 [4520.5492] <4> bpfis: INF - Created mount point C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_Microsoft Information Store_VGK_Archive_4520_1
16:34:42.982 [4520.5492] <32> bpfis: FTL - VfMS error 11; see following messages:
16:34:42.982 [4520.5492] <32> bpfis: FTL - Fatal method error was reported
16:34:42.982 [4520.5492] <32> bpfis: FTL - vfm_freeze_commit: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze_commit
16:34:42.982 [4520.5492] <32> bpfis: FTL - VfMS method error 4; see following message:
16:34:42.982 [4520.5492] <32> bpfis: FTL - VSS_Writer_freeze_commit: snapshot create failed
16:34:42.982 [4520.5492] <32> bpfis: FTL - VfMS error 11; see following messages:
16:34:42.982 [4520.5492] <32> bpfis: FTL - Fatal method error was reported
16:34:42.982 [4520.5492] <32> bpfis: FTL - vfm_freeze_commit: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze_commit
16:34:42.982 [4520.5492] <32> bpfis: FTL - VfMS method error 4; see following message:
16:34:42.982 [4520.5492] <32> bpfis: FTL - VSS_Writer_freeze_commit: snapshot create failed
16:34:42.982 [4520.5492] <4> bpfis: INF - Thawing NEW_STREAM0 using snapshot method VSS_Writer.
16:34:42.982 [4520.5492] <4> bpfis: INF - do_thaw return value: 0
16:34:42.982 [4520.5492] <4> bpfis: INF - Deleted mount point C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_NEW_STREAM0_4520_1
16:34:42.982 [4520.5492] <4> bpfis: INF - Thawing Microsoft Information Store:\VGK_Archive using snapshot method VSS_Writer.
16:34:42.982 [4520.5492] <4> bpfis: INF - do_thaw return value: 0
16:34:42.982 [4520.5492] <4> bpfis: INF - Deleted mount point C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_Microsoft Information Store_VGK_Archive_4520_1
16:34:42.982 [4520.5492] <16> bpfis: FTL - snapshot creation failed - Error attempting to gather metadata., status 130
16:34:42.982 [4520.5492] <4> bpfis: INF - Thawing NEW_STREAM0 using snapshot method VSS_Writer.
16:34:42.982 [4520.5492] <8> bpfis: WRN - NEW_STREAM0 is not frozen
16:34:42.982 [4520.5492] <4> bpfis: INF - Thawing Microsoft Information Store:\VGK_Archive using snapshot method VSS_Writer.
16:34:42.982 [4520.5492] <8> bpfis: WRN - Microsoft Information Store:\VGK_Archive is not frozen
16:34:42.982 [4520.5492] <8> bpfis: WRN - snapshot delete returned status 20
16:34:42.982 [4520.5492] <4> bpfis: INF - EXIT STATUS 130: system error occurred

any ideas?