cancel
Showing results for 
Search instead for 
Did you mean: 

I cant backup sql db

modi1234
Level 3

Hi Community,

I am trying to backup an sql databse on windows 7 client from windows server 2016 master. When I run the job manually I get 2 jobs on activity monitor as shown below:

<img attached>

On Sql client agent I see following output:

INF - BACKUP STARTED USING
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\mySQLDB_Backup.bch, Op# = 1
INF - Using backup image client.MSSQL7.client.db.myTestDB.~.7.001of001.20180712102815..C
INF - backup database "myTestDB" to VIRTUAL_DEVICE='VNBU0-4252-5020-1531409296' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <client server>. Connection timeout is <300> seconds.
Backup started Thu Jul 12 10:28:17 2018

This is my script file:

OPERATION BACKUP
DATABASE "myTestDB"
SQLHOST "client server"
NBSERVER "master server"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
NUMBUFS 2
ENDOPER TRUE
VDITIMEOUTSECONDS 900

I have created following log folders:

On client: bpcd and dbclient
On master: bprd (restart NetBackup Request service after creating log folder)
On media server: bpbrm and bptm

and my media server properties looks like this:

<img attached>

 After changing timeouts and adding VDITIMEOUTSECONDS 900 I have also restarted media, master and client services. 

Can anyone please help me figure out what's going on here? Stuck on this since long time. I am able to do backup of files from the same client only sql isn't working.

thanks!

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@modi1234

Standalone tape is the worst kind of backup storage in NBU.
NBU is an enterprise product that works best with storage that is automated.
With a tape library, it is easier to have sufficient tapes for different backup needs that are divided into different retention levels and different pools.

NBU will only append to the same tape if the pool and retention matches. 
Multiple retentions on same media can be enabled, but it is NOT best practice, because a tape can only be overwritten when all images on the tape has expired.

So, you need to have a good look at the all the retention levels in your backup policies. 
Ensure that you have sufficient tapes for each retention level and amount of space needed.
Load an empty/new tape or tape with matching retention before the backup starts.

There is a section in NBU Admin Guide II that explains how NBU chooses media with Standalone tape.

View solution in original post

10 REPLIES 10

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

it has nothing to do with sql. You have probably changed media in your library and did not run the Inventory in NetBackup. Or , you have emphy standalone drive.

You can also review Default-Application_Backup schedule and redirect it to disk storage unit if you have any.

Regards

Michal

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please open the job details for this job to see what exactly is causing the pending request. 

If you need further assistance, please copy the text in Job Details and post here. 

PS:
Did you remember to increase Max Jobs Per Client in master server Host Properties?

07/13/2018 10:06:11 - Info nbjm (pid=9012) starting backup job (jobid=65) for client ***, policy sql_policy, schedule Default-Application-Backup
07/13/2018 10:06:11 - Info nbjm (pid=9012) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=65, request id:{B5E72A31-BD1B-4CD8-92D2-D130A1CC4BE2})
07/13/2018 10:06:11 - requesting resource Any
07/13/2018 10:06:11 - requesting resource ***.***.local.NBU_CLIENT.MAXJOBS.***
07/13/2018 10:06:11 - requesting resource ***.***.local.NBU_POLICY.MAXJOBS.sql_policy
07/13/2018 10:06:11 - awaiting resource Any. 
          A pending request has been generated for this resource request. 
          Operator action may be required. Pending Action: No action, 
          Media ID: HC2002, Barcode: --------, Density: hcart2, Access Mode: Write, 
          Action Drive Name: N/A, Action Media Server: ***.***.local, Robot Type(Number): 0(N/A), 
          Volume Group: ---, Action Acs: N/A, Action Lsm: N/A
07/13/2018 10:08:11 - Info nbjm (pid=9012) Waiting in NetBackup scheduler work queue on server ***.***.local
07/13/2018 10:10:11 - Info nbjm (pid=9012) Waiting in NetBackup scheduler work queue on server ***.***.local
07/13/2018 10:12:11 - Info nbjm (pid=9012) Waiting in NetBackup scheduler work queue on server ***.***.local

 

And yes I increased the max jobs per client in master server host properties to 5. 

So just to verify if my storage media was up and there was nothing going on there, I backed up few files and that worked out fine.

How can I configure tp have Default-Application to back up on disk instead of media ? 

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

reread my post above again and carefully. Is media HC2002 in your robot ads is Netbackup aware of it via Robot Inventory?

Michal

Its actually a stand alone drive so I dont see option to robot inventory it.

and its not empty cause like i mentioned before i can backup other files on the same tape. 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
NetBackup will only add to the same tape if the retention level and pool is the same.

It seems that media id HC2002 is in same pool and has same retention as the Default-Application schedule in the SQL policy, and that is why NBU is asking you to load that tape.

What should i do differently or what settings should I change to make this work?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@modi1234

Standalone tape is the worst kind of backup storage in NBU.
NBU is an enterprise product that works best with storage that is automated.
With a tape library, it is easier to have sufficient tapes for different backup needs that are divided into different retention levels and different pools.

NBU will only append to the same tape if the pool and retention matches. 
Multiple retentions on same media can be enabled, but it is NOT best practice, because a tape can only be overwritten when all images on the tape has expired.

So, you need to have a good look at the all the retention levels in your backup policies. 
Ensure that you have sufficient tapes for each retention level and amount of space needed.
Load an empty/new tape or tape with matching retention before the backup starts.

There is a section in NBU Admin Guide II that explains how NBU chooses media with Standalone tape.

I dont know the exact cause of the solution to this problem but like you said, on changing the stand alone to a robotic library, I was able to succesful proceed with the backups.

 

Thank you!