09-10-2015 06:11 PM
09-16-2015 03:14 AM
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
09-10-2015 11:00 PM
09-15-2015 10:02 PM
09-15-2015 11:27 PM
09-16-2015 12:33 AM
09-16-2015 01:25 AM
09-16-2015 03:14 AM
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
09-17-2015 10:13 PM
09-17-2015 10:17 PM
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)
09-18-2015 01:49 AM
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