Exchange 2007. eseutil /cc. JET_errLogSectorSizeMismatch

Consider this scenario.

You’ve had to recover email from an older version of Exchange. You’ve created a new domain, installed Exchange with the same organisation name and added a new Exchange server where the Storage Group and Database retains the same name and structure.

You’ve successfully restore from tape. However the Database isn’t mounted and fails to mount.

You’ve try to replay the logs from the restore.env file and you get this error

eseutil /cc

Operation terminated with error -546 (JET_errLogSectorSizeMismatch, the log file sector size does not match the current volume’s sector size) after 0.78 seconds.

You get the same error when you try to reply the logs manually using eseutil /r

The cause? The sector size.

As discussed in this blog post, the sector size and physical disk types for databases in an Exchange 2010 Dag need to remain the same across all volumes. I highly recommend taking the time to read the article in it’s entirety. https://blogs.technet.microsoft.com/exchange/2013/04/24/exchange-2010-database-availability-groups-and-disk-sector-sizes/

First. I had a look at my disks by running this command

fsutil fsino ntfsin DriveLetter:

Take note of my example below and the ‘Bytes Per Physical Sector’

>fsutil fsinfo ntfsinfo c:

NTFS Volume Serial Number :       0x1e6848246847f953
Version :                         3.1
Number Sectors :                  0x00000000077ccfff
Total Clusters :                  0x0000000000ef99ff
Free Clusters  :                  0x00000000004ba961
Total Reserved :                  0x0000000000000040
Bytes Per Sector  :               512
Bytes Per Physical Sector :       4096
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0

>fsutil fsinfo ntfsinfo D:

NTFS Volume Serial Number :
Version :                         3.1
Number Sectors :                  0x00000000077fefff
Total Clusters :                  0x0000000000effdff
Free Clusters  :                  0x0000000000c99b89
Total Reserved :                  0x0000000000000000
Bytes Per Sector  :               512
Bytes Per Physical Sector :       512
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0

>fsutil fsinfo ntfsinfo e:

NTFS Volume Serial Number :
Version :                         3.1
Number Sectors :                  0x000000007cffefff
Total Clusters :                  0x000000000f9ffdff
Free Clusters  :                  0x0000000002edb5ec
Total Reserved :                  0x0000000000000000
Bytes Per Sector  :               512
Bytes Per Physical Sector :       512
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0

The backup product had restored the logs required for the database onto the C:\. As this failed the database was in a ‘dirty shutdown state’ and eseutil /cc or eseutil /r failed

The ‘Bytes Per Physical Sector’ for the C:\ differed from the disks that held the database and logs

The fix was relatively simple. I moved the logs required for restore to the D: and reran eseutil /cc

 

Netbackup. AdvancedDisk. CIFS Share. STS error.

I was wanting to set up an Advanced Disk Pool in Netbackup for duplication to our long term storage.

I went through the steps and created a new Disk Storage Server through ‘Configure Disk Storage Servers’ Wizard and configure my media server as the Disk Storage Server.

diskstorageserver

Next, I go through the Disk Pool Wizard. Type Advanced Disk, Server as my Media Server, then I go to add Volume.

Each time, I’d get this error. “RDSM has encountered an STS error: failed to update storage server configuration due to unsupported platform, invalid configuration or system error”

volume

Why was this happening? According to the user guides, a CIFS share is supported for Advanced Disk.

Hindsight is a wonderful thing, eventually the problem was identified. The volume needs to be the root of the CIFS share.

Don’t add a path to a subfolder! I was adding the UNC path to a subfolder on the share.

Hopefully this saves somebody out there a headache.

NBU_CATALOG.MAXJOBS Limit Reached

Scenario: Your Catalog backups are not running. You check the jobs and these are hung with the error below.

Limit has been reached for the logical resource %MyServer%.NBU_CATALOG.MAXJOBS

Google and Symantec’s forums weren’t giving me much. I checked disk space, the policy, the schedules, the media and anything other setting I could find.

Solution: The solution is obvious in hindsight. Netbackup only allows one Catalog job to run at a time.

Queried my history and found a hung Catalog job. Terminated the old job, ran a manual backup and all is going again.

Netbackup – Parent_end_notify.cmd

Scenario: You are using Netbackup and you are wanting a script to run when a job completes.

Options: There are two options, you can run a script on the client each time a child job runs and completes or you can run a script from the master server each time a parent completes.

I will focus on the Master Server.

Solution: Under %ProgramFiles%\Veritas\NetBackup\bin you will find a file called parent_end_notify.cmd. This is what you will use to run any script you need.

This is a .cmd, so be familiar with windows batch files. 😉

There are seven parameters Netbackup sends to this batch file everytime a parent job completes.

@REM %1 = CLIENT – the client hostname
@REM %2 = POLICY – the policy label
@REM %3 = SCHEDULE – the schedule label
@REM %4 = SCHEDULE_TYPE – the type of schedule: FULL INCR UBAK
@REM UARC
@REM %5 = STATUS – the backup status for this job
@REM %6 = STREAM – the backup stream number for this job always -1
@REM %7 = STREAM_CNT – # streams started (if -1, genjob failed to call pem)

It is up to us to make the decision. In my case, I wanted to evaluate for three policies and if they completed with exit status 0 (successful), run a command.

Highlighted below are the bits I added in bold, I added this at the end of the script between the commented out mail section and EndMain

@REM – might want to mail this info to someone
@REM –
@REM – @call %NB_MAIL_SCRIPT% someone_who_cares “NetBackup parent end notify” %OUTF%
@REM —————————————————————————
@if “%2” == “Policy1” goto Policy1
@if “%2” == “Policy2” goto Policy2
@if “%2” == “Policy3” goto Policy3
goto EndMain
@REM —————————————————————————
:Policy1
@if “%5” == “0” goto Successful
@if “%5” != “0” goto NotSuccessful
:Successful
@ECHO “MyContent” > PathToFile.txt
goto EndMain
:NotSuccessful
goto EndMain
@REM —————————————————————————
:Policy2
@if “%5” == “0” goto Successful
@if “%5” != “0” goto NotSuccessful
:Successful
@ECHO “MyContent” > PathToFile.txt
goto EndMain
:NotSuccessful
goto EndMain
@REM —————————————————————————
:Policy3
@if “%5” == “0” goto Successful
@if “%5” != “0” goto NotSuccessful
:Successful
@ECHO “MyContent” > PathToFile.txt
goto EndMain
:NotSuccessful
goto EndMain
@REM —————————————————————————
:EndMain
@endlocal
@REM – End of Main Program —————————————————–

Other Information: 

Master Server:

parent_start_notify
https://www.veritas.com/support/en_US/article.000044303

parent_end_notify https://www.veritas.com/support/en_US/article.HOWTO106055

Client Side: 

bpstart_notify
https://www.veritas.com/support/en_US/article.000044292

bpend_notify
https://www.veritas.com/support/en_US/article.000044293

Netbackup 7.05.07. Exchange 2013. Error 2. Dag.

After configuring Exchange 2013 DAG database and configuring the database backup in Netbackup, it would fail with error 2.

After a lot of reading, many a trial and error, I found this little gem http://www.symantec.com/connect/forums/exchange-2013-error-2

The solution?

In your policy under Microsoft Exchange Attributes, Netbackup wants the preferred server list populated.

Choose your Source – Active or Passive. Click Preferred Server list and add your DAG nodes.

My Working Configuration

Backup Selections: Microsoft Exchange Database Availability Groups:\DAGName\Microsoft Information Store

Attributes:
Snapshot Client “Perform Snapshot Backups”
Microsoft Exchange Attributes: Source. Populated Preffered Server list with DAG nodes.

Clients: YourDAGName (Cluster DNS name for your DAG)