IT Infrastructure blog

February 25, 2012

NDMP backup failure (99) in Netbackup

Filed under: NetApp,Symantec Netbackup — Akther @ 12:58 pm
Tags:

We are using NetApp Storage box to keep departmental and end user home folder. We have enabled CIFS on Storage and shared to each department with their respective.

Today we have seen that NDMP backup job has failed with error code 99. It was a full backup and have to resolve quickly because it’s contains business data.

When opening the failed job window we could see that below findings.

2/24/2012 9:16:03 AM – Error ndmpagent(pid=9744) ndmp_authenticate_connection: ndmp_connect_client_auth failed          2/24/2012 9:16:03 AM – Error ndmpagent(pid=9744) failed to connect to NDMP server fas2050b, connect error = -1009 (NDMP server login failed – verify attributes with tpautoconf -verify)

It’s clear that Storage team had changed the password of Root account. When we contact them they said yes and we updated the settings with new password

Here is the place we need to change this settings in Netbackup Console.

 

 

 

 

 

 

Once we changed the credentilas triggered a mannual backup of NDMP and it start working fine.

 

Advertisements

December 3, 2011

Netbackup server not triggering backup automatically

Filed under: Symantec Netbackup — Akther @ 3:59 pm

Noticed that Netbackup server is not triggering backup jobs automatically. It’s observed that this process has suspended and you have to manually trigger backup. How to resolve this?

If you want to stop the triggering automatically issue below command

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbpemreq -suspend_scheduling

November 30, 2011

Restore Enterprise Vault Databases when EV Database server crashed

Filed under: Enterprise Vault 8.0,Symantec Netbackup — Akther @ 7:23 pm
Tags:

Last week our MS SQL Database  Server had severe hardware issues and it was down and can’t boot.  The Enterprise vault 9.0 databases are contains in this server. So none of the users cannot open archived emails because there is no database connectivity with EV.

We are regularly taking backup of these databases by using  Symantec Netbackup 7.0 version. So we need to do a restore from Netbackup server to another SQL server. In a nutshell EV disaster recover y has to perform. Yes we have done this activity successfully and i would like to share that experience with you all.

Environment

Enterprise vault server 9.0 – Installed on Windows 2008 R2 server

MS SQL 2008 R2

Symantec Net backup 7.0

 Activities performed

Prepared new server for MS SQL Database with same name and Ip addres

  1. Installed Windows 2008 Server Ent R2 OS in server
  2. Installed SQL 2008 Server Enterprise R2 Edition
  3. Installed Office 2007
  4. Installed EV client
  5. Mount disks from Netapp ( Space taken from Netapp storage)
  6. Patched and installed all the basic software’s and Antivirus
  7. Installed NetBackup agent
  8. Given the Evadmin (EV service account)  local admin and SQL sys admin permission
  9. IIS and .net installed
  10. Name, IP and versions are same as the old server

Now the Database server is ready for restore. Below screenshot  is taken from Netbackup server. I will list which order we have to restore all the database.

Stop the EV services from EV server before start restoring

  1. Restore from Netbackup server –>Backup archive GUI–> Select the EV server
  2. First restore –> Directory DB
  3. Then —>Audit DB
  4. Then–> Monitoring DB
  5. Evsite–> EV Vault store Group–>EV Vault store DB Mangers ( we have managers vault store)
  6. Evsite –> EV Vault store Group–> EV Vault store DB users ( we have users vault store)
  7. Manager Partition (Evsite–>EV vault storage group–>V Vault store–>All Partition–>Open partitio
  8. User Partition (Evsite–>EV vault storage group–>EV Vault store–>All Partition–>Open partition
  9. Reinstall EV application ( to sync /update EV binaries) –>RunEVsetup.exe. It wont affect y0ur EV server

Now users can able to open the archived emails.

July 17, 2011

Symantec Certified Specialist in NBU and EV

Filed under: Enterprise Vault 8.0,Symantec Netbackup — Akther @ 11:01 pm
Tags:

I am happy to share the joy to all of you that i have got two Symantec certificates under my belt.  Both these technologies i am working quiet some time and It’s in my radar some time. Finally achieved.

1. Symantec Certified Specialist – Netbackup 7.0 for Windows

2. Symantec Enterprise Vault 9.0 for Exchange Server

I am gonna to put these logos in to my shelf…. Thanks for the support from the colleagues and friends especially Rafeeq, Sameer, Gulzar, Ricky, Felipe and Joeriz to acheive these honour.

Thanks

Akther

June 20, 2011

Error code 58 in netbackup

Filed under: Symantec Netbackup — Akther @ 3:19 pm
Tags:

Here is one of the strange Netbackup issue we faced last week.

MS SQL Database backup failed with Error code 58. Cannot see  any other specific problems in Netbackup server

During the troubleshooting face we went to Database server and check all the services in client. All were started. What we did we restart the serive of Symantec Private Branch Exchange service .

After this we ran backup mannually and it start working fine.

April 27, 2011

Restore single email by using Symantec Netbackup for Exchange 2007

Symantec Netbackup is the powerfull tool that you can use to restore entire Information store, single mailbox and single mail as well. In our Datacenter we are using Netbackup to take the backup of entire servers. In this post i am writing how we can restore single email from Netbackup server.

Symantec Netbackup version : 7.0.1

Exchange Server : 2007 SP1 CCR

Definitly we should  have a full backup of mail boxes to resotre a single email or mail boxes.

Restore a single mail

Go to backup and Restore GUI

Select Full backup from the list

Select the user –> and select which email you want to restore. ( If we select user it will restore mailbox)

Then it will start restoration process.

The particular email could see in user inbox now.

December 3, 2010

Restore MS SQL Database in another server by using Symantec Netbackup Server

Filed under: Symantec Netbackup — Akther @ 8:29 pm

This article will describe how we can restore MS SQL database in to another server.

Important points need to be noted while restoring a database in to another server

1. Login as a user who is having SQL server access permission. If you are login a user who doesn’t have access to database it will throw error while taking Netbackup agent–> Netbackup MS SQL client from start menu ( right click from net backup Ms Sql client and run as administrator will solve this issue some time)

2. Client and server should be same Netbackup version. ( our case 7.0.1 on both end)

Restore process step by step

Go to Destination server –> Start–> Symantec Netbackup–>Netbackup agent –> Netbackup MS SQL client ( right click –> run as administrator if you have permission)

File –> Restore SQL Server Object –>


SQL Host – Where is the original database backup residing ( Source database server)( If SQL server is in cluster you should have given the cluster name)

Source Client – Same as SQL host ( It means the destination server .i.e same server which you login now to restore)

Click –> Ok

It will show you the latest database and log backup

Select latest log file, it will automatically select latest database for this concern log file

Click –> Restore

It will open a window and we need to save a script. give a meaningful name and click save.

It will open a notepad and in this note pad we need to edit below lines

1. DATABASE “Newdatabase”  ——> This is the database will be restore in destination server

2. MOVE  “sourcedb”

TO  “F:\MSSQL10_50.MSSQLSERVER\MSSQL\Data\newdatabase.mdf”

3. MOVE  “Sourcedb_log”  —> This is the source database server
TO  “F:\MSSQL10_50.MSSQLSERVER\MSSQL\Data\newdatabase_log.LDF”

4. RECOVEREDSTATE       RECOVERED  ( This will enable database restore with recovered)
NUMBUFS    1  ( If we see this as 2 for some reason ) there is a chance to fail the restore)

Once it done Go to File –> Manage script file –> select the script file which we saved in the location–> Start

C:\Program Files\Veritas\Netbackup\dbext\MSSQL ( Location of the script file)

Press F9 then you can see the status or Go to NBU server and see the Activity Monitor

It will restore the database with the name of Newdatabase.mdf

Hope it would be helpful for Netbackup administrators around the world

Thanks

Akther


November 27, 2010

You are already running Available_Media.when running the Available_Media command.

Filed under: Symantec Netbackup — Akther @ 7:42 pm
Tags:

Available_media.cmd command is helpful to find out the media status in Veritas Netbackup. If you run the below command to see the status of media you may encountered below error

C:\Program Files\Veritas\NetBackup\bin\goodies>available_media.cmd
You are already running Available_Media.
Try again later.

How to resolve this

There is a tech note available in symantec that how we can resolve this error.

http://support.veritas.com/docs/245562

you have to delete  the AM.<USERNAME>.lok file,  from %temp% folder then run the Available_Media.cmd script again

Thought to share this error with all of you and hope it helps some one who is working with Symantec Veritas Netbackup

November 26, 2010

Status code 96 in Veritas Netbackup server

Filed under: Symantec Netbackup — Akther @ 7:58 pm

If you have a chance to work with Veritas Netbackup server this error code you would probably see.

Error code 96 throwing error in Activity monitor mainly because of unavailability of media.

Why media is not available to write images ? several reason….

1) Media is full

2) Media is suspend mode

3)Media is frozen

4) Media Retention period and the net backup policy retention policy is different ( Tape retention policy is 1 and policy retention period is 1 month ( basically 2)

4) There is no media in Volume pool

So Netbackup Administrator should be vigilant in daily monitoring these media status by using a use full command to check  what happens to tape media.

C:\Program Files\Veritas\NetBackup\bin\goodies>available_media.cmd >>c:\media.txt

This will throw the media is in full or frozen or suspend or available.

Based on this unfreeze the media or find out new tape and put it in to the correct volume pool.

other use full command to see a particular media status is below

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listmedia -mediaid TP0064

( TP064 defines the label name of tape)

output of this command would be below. Here you can find out the retention period of tape, when this image will be expire and Media status.

Here media status is showing Active, it may be vary like Full or Frozen.

NBEMMCMD, Version:7.0.1
====================================================================
Media GUID:                     968da873-a972-4a9f-a27c-62404b8991b2
Media ID:                            TP0064
Partner:                                –
Media Type:                       HCART2
Volume Group:                000_00000_TLD
Application:                    Netbackup
Media Flags:                    1
Description:                    Added by Media Manager
Barcode:                           TP0064
Partner Barcode:          ——–
Last Write Host:             Netbackup-Masterserver
Created:                            10/27/2010 16:13
Time Assigned:              11/13/2010 18:34
First Mount:                    11/13/2010 18:35
Last Mount:                     11/19/2010 12:01
Volume Expiration:              –
Data Expiration:            12/03/2010 12:00
Last Written:                   11/19/2010 12:00
Last Read:                         –
Robot Type:                     TLD
Robot Control Host:     Netbackup-Masterserver
Robot Number:               0
Slot:                                     22
Side/Face:                      –
Cleanings Remaining:   –
Number of Mounts:       3
Maximum Mounts Allowed:     0
Media Status:                   ACTIVE
Kilobytes:                         198078296
Images:                              14
Valid Images:                   14
Retention Period:             1
Number of Restores:             0
Optical Header Size Bytes:      1024
Optical Sector Size Bytes:      0
Optical Partition Size Bytes:   0
Last Header Offset:             3095010
Adamm Guid:                     00000000-0000-0000-0000-000000000000
Rsm Guid:                       00000000-0000-0000-0000-000000000000
Origin Host:                    NONE
Master Host:                  Netbackup-Masterserver
Server Group:                NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    5
Volume Pool:                    Exchange pool
Previous Pool Name:             –
Vault Flags:                    –
Vault Container:                –
Vault Name:                     –
Vault Slot:                     –
Session ID:                     –
Date Vaulted:                   –
Return Date:                    –
====================================================================

If you want to expire the image in particular tape we can use below command ( be sure that you would not require this data in future)

C:\Program Files\Veritas\NetBackup\bin\admincmd> bpexpdate -m TP0064 -d 0

This will expire media TP0064 and will be available for next backup .

Hope this article would be helpful for Netbackup admins.

Thanks

Akther

November 22, 2010

Status code 71 in Veritas Netbackup server for Exchange Mail box backup

Filed under: Symantec Netbackup — Akther @ 6:36 pm

There was an issue to take backup of Exchange mailboxes  ( granular backup to say in Veritas terminology) through Symantec Veritas Netbackup.

Error code was showing 71 in Activity monitor.

Error was below

11/22/2010 3:23:46 PM – mounting Tp0066
11/22/2010 3:23:48 PM – Warning bpbrm(pid=2140) from client Exchange-cluster: WRN – unable to successfully enumerate folder: Microsoft Exchange Mailboxes:\
11/22/2010 3:23:48 PM – Warning bpbrm(pid=2140) from client Exchange-cluster: WRN – unable to successfully enumerate folder: Microsoft Exchange Mailboxes:\
11/22/2010 3:23:48 PM – Error bptm(pid=4636) socket operation failed – 10054 (at child.c.1294)
11/22/2010 3:23:48 PM – Warning bpbrm(pid=2140) from client Exchange-cluster: WRN – unable to successfully enumerate folder: Microsoft Exchange Mailboxes:\
11/22/2010 3:23:48 PM – Error bptm(pid=4636) unable to perform read from client socket, connection may have been broken
11/22/2010 3:23:48 PM – Error bpbrm(pid=2140) could not send server status message
11/22/2010 3:23:50 PM – end writing
none of the files in the file list exist(71)

SOLUTION/WORKAROUND:

1. Checked and found that we cannot browse and enumerate the mailboxes from the Exchnage policy \ Selections

2. Went to Exchange active node and configured the exchange backup account. ( Services–> Netbackup client–>logon tab–>give exchange admin account and password there). Then restart the netbackup service

3) Updated the changes using bprdreq command

C:\program files\veritas\netbackup\bin\admincmd >bprdreq -readconfig

 

4) ran the Mailbox backup manually. And it works fine.

 

Thanks

Akther

Create a free website or blog at WordPress.com.