backup exchange 2013 error

[lelei90343]

Who can help me

[Marianne]

You forgot to tell us anything about the error and environment. What is the error? Which NBU 7.6 patch level? What does policy config look like? Standalone or DAG? GRT backup or not?

[lelei90343]

Oh!sorry. I can't pasted error message, because computer failure. Environment: NBU 7.6.0.4 (Redhat 5.8) Exchange 2013 Standalone Server (windows 2012) Exchange's policy: Policy type:MS-Exchange-Server Client: mtest.sh.com Backup Selections: Microsoft Exchange Mailboxes:/ Microsoft Information Store:/ Error Message: 09/16/2015 12:59:29 - granted resource dd_stu 09/16/2015 12:59:29 - estimated 0 kbytes needed 09/16/2015 12:59:29 - Info nbjm (pid=4741) started backup (backupid=mtest.sh.com_1442379569) job for client mtest.sh.com, policy mail_bk, schedule mail_bk on storage unit dd_stu 09/16/2015 12:59:29 - started process bpbrm (pid=6951) 09/16/2015 12:59:31 - Error bpbrm (pid=6951) This type of backup is not supported on this version of Exchange 09/16/2015 12:59:31 - Info bpbkar (pid=0) done. status: 72: the client type is incorrect in the configuration database 09/16/2015 12:59:31 - end writing the client type is incorrect in the configuration database (72)

[Marianne]

" Error bpbrm (pid=6951) This type of backup is not supported on this version of Exchange 09/16/2015 12:59:31 - Info bpbkar (pid=0) done. status: 72: the client type is incorrect in the configuration database" Have you checked compatibility? Or in NBU for Exchange Admin Guide to ensure that the policy is configured correctly? Mailboxes and Information Store cannot be in the same policy. Mailbox backup also not supported as from Exch 2010. If you want to restore item-level components, you need to config GRT, but then you need to check from which NBU version GRT is supported for Exch 2013. Show us the entire policy config. On master, run this command from cmd (...netbackup\bin\admincmd): bppllist ( policy-name ) -U

[lelei90343]

I had seen the release notes, NBU 7.6.0.4 version support exchange 2013 Mailboxes and Information Store are be in the different policy, but execute Mailboxes and Information Store policy's Error message are same.

[lelei90343]

There is another mistake Failed to configure the user name and password for the client Exchange If I type correct down/username and password, click Apply button, prompt "Unable to validate user name and password. Error 1300" If I intentionally type incorrect down/username and password, click Apply button, prompt "Unable to validate user name and password. Error 1326"

[Marianne · Accepted solution]

Please go through NetBackup for Microsoft Exchange Server Administrator's Guide  for Policy config (download the pdf from the Attachments link).

You cannot backup mailboxes with Exch 2013.
Extract from above manual:

Mailbox and public folder operations are performed with MAPI. These operations
require the use of the Microsoft Exchange Mailboxes:\ or the Microsoft
Exchange Public Folders:\ directives in the backup policy. This type of backup
is only available with Exchange 2007. This type of restore is only available with
Exchange 2007 and 2003.
Symantec recommends that you perform streaming or snapshot backups. MAPI
mailbox and public folder backups allow for mailbox or public folder recovery, but
are not adequate for disaster recovery. Exchange database backups are required
for disaster recovery. Backups with Granular Recovery Technology (GRT) enabled
can replace MAPI mailbox and public folder backups.

As per the DB SCL, GRT support for Exch began in 7.6.0.3.

Herewith detailed instructions to config GRT backups:

Everything you need to know to get Exchange Granular backups to work:
http://www.symantec.com/docs/HOWTO73076  

Disk Storage Types supported for Granular Recovery Technology (GRT)
http://www.symantec.com/docs/TECH187917

[lelei90343]

[root@nbumas ~]# bppllist mail_bk -U ------------------------------------------------------------ Policy Name: mail_bk Policy Type: MS-Exchange-Server Active: yes Effective date: 09/18/2015 07:08:18 Mult. Data Streams: no Client Encrypt: no Checkpoint: no Policy Priority: 0 Max Jobs/Policy: Unlimited Disaster Recovery: 0 Collect BMR info: no Residence: dd_stu Volume Pool: NetBackup Server Group: *ANY* Keyword: (none specified) Data Classification: - Residence is Storage Lifecycle Policy: no Exchange Source attributes: no Application Discovery: no Discovery Lifetime: 0 seconds ASC Application and attributes: (none defined) Granular Restore Info: no Ignore Client Direct: no Enable Metadata Indexing: no Index server name: NULL Use Accelerator: no HW/OS/Client: Windows-x64 Windows mtest.sh.com Include: Microsoft Information Store:\ Schedule: mail_bk Type: Automatic Backup Frequency: every 7 days Excluded Dates---------- No specific exclude dates entered No exclude days of week entered PFI Recovery: 0 Maximum MPX: 1 Retention Level: 1 (2 weeks) Number Copies: 1 Fail on Error: 0 Residence: (specific storage unit not required) Volume Pool: (same as policy volume pool) Server Group: (same as specified for policy) Residence is Storage Lifecycle Policy: 0 Schedule indexing: 0 Daily Windows:

[lelei90343]

Detailed status:

09/18/2015 12:11:17 - Info nbjm (pid=4741) starting backup job (jobid=28) for client mtest.sh.com, policy mail_bk, schedule mail_bk
09/18/2015 12:11:17 - Info nbjm (pid=4741) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=28, request id:{4F3F40F4-5DBB-11E5-BE0E-059D905454F2})
09/18/2015 12:11:17 - requesting resource dd_stu
09/18/2015 12:11:17 - requesting resource nbumas.NBU_CLIENT.MAXJOBS.mtest.sh.com
09/18/2015 12:11:17 - requesting resource nbumas.NBU_POLICY.MAXJOBS.mail_bk
09/18/2015 12:11:17 - granted resource nbumas.NBU_CLIENT.MAXJOBS.mtest.sh.com
09/18/2015 12:11:17 - granted resource nbumas.NBU_POLICY.MAXJOBS.mail_bk
09/18/2015 12:11:17 - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=dd_pool;Path=PureDiskVolume;StorageServer=nbumas;MediaServer=nbumas
09/18/2015 12:11:17 - granted resource dd_stu
09/18/2015 12:11:17 - estimated 0 kbytes needed
09/18/2015 12:11:17 - begin Parent Job
09/18/2015 12:11:17 - begin Snapshot: Start Notify Script
09/18/2015 12:11:17 - Info RUNCMD (pid=16855) started
09/18/2015 12:11:17 - Info RUNCMD (pid=16855) exiting with status: 0
Operation Status: 0
09/18/2015 12:11:17 - end Snapshot: Start Notify Script; elapsed time 0:00:00
09/18/2015 12:11:17 - begin Snapshot: Step By Condition
Operation Status: 0
09/18/2015 12:11:17 - end Snapshot: Step By Condition; elapsed time 0:00:00
09/18/2015 12:11:17 - begin Snapshot: Read File List
Operation Status: 0
09/18/2015 12:11:17 - end Snapshot: Read File List; elapsed time 0:00:00
09/18/2015 12:11:17 - begin Snapshot: Create Snapshot
09/18/2015 12:11:17 - started process bpbrm (pid=16861)
09/18/2015 12:11:21 - Info bpbrm (pid=16861) client_pid=13888
09/18/2015 12:11:21 - Info bpbrm (pid=16861) from client mtest.sh.com: BPRESOLVER has executed on server (MTEST)
09/18/2015 12:12:02 - Info bpresolver (pid=13888) done. status: 2
09/18/2015 12:12:02 - Info bpbrm (pid=16861) mtest.sh.com is the host to backup data from
09/18/2015 12:12:02 - Info bpbrm (pid=16861) reading file list for client
09/18/2015 12:12:02 - Info bpbrm (pid=16861) start bpfis on client
09/18/2015 12:12:02 - Info bpbrm (pid=16861) Starting create snapshot processing
09/18/2015 12:12:02 - snapshot backup using alternate client mtest.sh.com
09/18/2015 12:12:07 - Info bpfis (pid=14388) Backup started
09/18/2015 12:13:48 - Critical bpbrm (pid=16861) from client mtest.sh.com: FTL - vfm_freeze: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze
09/18/2015 12:13:48 - Critical bpbrm (pid=16861) from client mtest.sh.com: FTL -
09/18/2015 12:13:48 - Critical bpbrm (pid=16861) from client mtest.sh.com: FTL - snapshot preparation failed, status 156
09/18/2015 12:13:48 - Info bpfis (pid=14388) done. status: 156
09/18/2015 12:13:48 - end Snapshot: Create Snapshot; elapsed time 0:02:31
09/18/2015 12:13:48 - Info bpfis (pid=14388) done. status: 156: snapshot error encountered
09/18/2015 12:13:48 - end writing
Operation Status: 156
09/18/2015 12:13:48 - end Parent Job; elapsed time 0:02:31
09/18/2015 12:13:48 - begin Snapshot: Stop On Error
Operation Status: 0
09/18/2015 12:13:48 - end Snapshot: Stop On Error; elapsed time 0:00:00
09/18/2015 12:13:48 - begin Snapshot: Delete Snapshot
09/18/2015 12:13:49 - Info bpbrm (pid=16974) Starting delete snapshot processing
09/18/2015 12:13:49 - started process bpbrm (pid=16974)
09/18/2015 12:13:53 - Info bpfis (pid=17164) Backup started
09/18/2015 12:13:53 - Critical bpbrm (pid=16974) from client mtest.sh.com: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.mtest.sh.com_1442549477.1.0
09/18/2015 12:13:54 - Info bpfis (pid=17164) done. status: 4207
09/18/2015 12:13:54 - end Snapshot: Delete Snapshot; elapsed time 0:00:06
09/18/2015 12:13:54 - Info bpfis (pid=17164) done. status: 4207: Could not fetch snapshot metadata or state files
09/18/2015 12:13:54 - end writing
Operation Status: 4207
09/18/2015 12:13:54 - begin Snapshot: End Notify Script
09/18/2015 12:13:54 - Info RUNCMD (pid=16979) started
09/18/2015 12:13:54 - Info RUNCMD (pid=16979) exiting with status: 0
Operation Status: 0
09/18/2015 12:13:54 - end Snapshot: End Notify Script; elapsed time 0:00:00
Operation Status: 4207
Could not fetch snapshot metadata or state files (4207)

[Marianne]

So, it seems that you have fixed whatever was wrong with the policy?

We now see a snapshot failure.

Have you checked the Exch server Event logs for VSS errors? 

What is the status of VSS writers on the Exch server?

Please post output of these commands:

vssadmin list writers

vssadmin list providers