Forum Discussion

evargas's avatar
evargas
Level 4
13 years ago

Clearing out the Program Files\Veritas\Netbackup\Temp directory

Our environment:

Netbackup servers running version 7.0.1 on Solaris 10 64 bit

Exchange servers running on Windows 2008 R2 64 bit

DAG setup with 2 nodes, active copies on both nodes

Our Exchange Administrator is claiming that Netbackup doesn't clean up Program Files\Veritas\Netbackup\Temp directory when the backup runs.

is that a concern or should I take a look at this issue?

 

this is what they said Symantec told them.. is this acurate?

is this directory suppose to be updated or clean up every time the backup starts?

the issus we are having is that backup fails on one or two databases (full backups) or sometimes Netbackup skips one out 30 databases.

Suspected causes are NetBackup has not been consistently clearing out the Program Files\Veritas\Netbackup\Temp directory. According to information from Veritas, files left in this temp folder can cause backup failures.

 

Any help or comments are appreciated.

 

Thanks

 

7.1.x and Earlier
Backup and Recovery
Best Practice
Linux
MS Exchange
NetBackup
Solaris
Troubleshooting
  • V4's avatar
    V4
    13 years ago

    Did you checked for VSS patches. and for retryable error. try restarting information store service

    have look on following Tn

    http://blogs.technet.com/b/timmcmic/archive/2012/03/11/exchange-and-vss-my-exchange-writer-is-in-a-failed-retryable-state.aspx

    http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/c247bcba-8105-46f9-b7ef-937b0f265b3e

     

  • V4's avatar
    V4
    Level 6
    13 years ago

    Firstly need to focus on why backups are failing. As backup fails, hence fails are left over under /temp

    What error do u see on your database backup failure?

    Windows Event logs?

     

  • evargas's avatar
    evargas
    Level 4
    13 years ago

    The common error codes are exit codes 2, 130, 13 and 156

    but the one we get more often is exit code 130, we have opened many case with Symantec support about this issue but have not got any resolution.  we only get on a finger pointing between Symantec and Microsoft supports.

    Symantec claims that is a VSS writer issue and Microsoft claims that is the way tha Netbackup handles the VSS writers.

    when the backup fails with code 130, the VSS writers are in "Rretriable error" mode, but if we run a manual backup on that database it completes successfully.

    Writer name: 'Microsoft Exchange Replica Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {6e4edb49-7ef3-4913-9997-a7b3a6033cec}
       State: [7] Failed
       Last error: Retryable error

    The other issue is that sometimes there are no errors anywhere and some databases are "skip" they are not listed in the work order.  the backup completes successfully but some databases are missing from backups.

    we have seen these errors on the nodes.

    Event ID 2112

    The Microsoft Exchange Replication service VSS Writer instance 6ed07bb5-166e-412a-867b-9302e4694891 failed with error code 80070020 when preparing for a backup of database 'nambx21'.

    Event ID 2024
    Exchange VSS writer 8/29/2012 8:05:29 PM
     

    Event ID 2032
    Exchange VSS writer 8/29/2012 8:05:29 PM

    The Microsoft Exchange Replication service VSS Writer failed when terminating the backup.

     

  • V4's avatar
    V4
    Level 6
    13 years ago

    Did you checked for VSS patches. and for retryable error. try restarting information store service

    have look on following Tn

    http://blogs.technet.com/b/timmcmic/archive/2012/03/11/exchange-and-vss-my-exchange-writer-is-in-a-failed-retryable-state.aspx

    http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/c247bcba-8105-46f9-b7ef-937b0f265b3e

     

  • evargas's avatar
    evargas
    Level 4
    13 years ago

    We have already go through these.

    We are trying to find out the root cause of this errors and posibly a solution.

    so far I have not found any.