Slow SLP Duplication Jobs
hi , Im using SLP policies ( backup to disk -Local Disk then duplicate to tape -IBM TS), recently duplication jobs take a lot more time to complete ( around 10-12 hours for each) when i check Netbackup i can see it will find right media right away and loads it in tape drive very fast but the duplication job will hangs at "Waiting for positioning of Media ID" for about 10 hours. any help here would be apperciated. thanks! NBRB logs attached to this post. Netbackup 7.7 Windows Server 2012 R2 IBM TS Series LTO-66.9KViews0likes23CommentsSLP Duplication Operation
Being rather new to NetBackup, there is something I hope to clarify, with regards to monitoring duplication operations in SLPs. In my setup, after the backup operation, I have a duplication operation scheduled. To track the progress of the operation, I use the following CLI command: nbstlutil stlilist -U -copy_type duplicate This is the part where I am a little confused. The output of the command is similar to this: Image img_0001 for Lifecycle slp_01 is IN_PROCESS Copy to copy_dest_01 of type DUPLICATE is IN_PROCESS Image img_0002 for Lifecycle slp_02 is IN_PROCESS Copy to copy_dest_02 of type DUPLICATE is IN_PROCESS Image img_0003 for Lifecycle slp_02 is IN_PROCESS Copy to copy_dest_02 of type DUPLICATE is IN_PROCESS Image img_0004 for Lifecycle slp_01 is IN_PROCESS Copy to copy_dest_01 of type DUPLICATE is IN_PROCESS Image img_0005 for Lifecycle slp_03 is IN_PROCESS Copy to copy_dest_03 of type DUPLICATE is NOT_STARTED My question is this: Does the "Image ... IN_PROCESS" entry relate directly to the "Copy ... IN_PROCESS" entry beneath it? In other words, is the "Copy ... IN_PROCESS" entry awaiting the completion of creating the image? In that case then why is there a "Copy ... NOT_STARTED" as well? Tried searching around for how the nbstlutil entries are created but can't seem to get much from it. Any help would be greatly beneficial. Thanks in advance!Solved3.6KViews0likes7CommentsSLP not duplicating
Hi. So we got a problem with our SLP doing duplications. We are currently running Netbackup 7.6.1, one masterserver, and 3 media servers. Windows 2008 R2 We are running all duplications to tape, a dell TL4000. We run 7 different SLP's where 2 of these duplicates to tape. Here comes our problem, one of these two SLP jobs wont duplicate the data to tape. It just keeps putting the data in backlog. The backupjob runs fine, but when its time for the SLP to run duplication, it nevere starts. nbstlutil stlilist -image_incomplete -U Image fil4.hedmark.org_1510305239 for Lifecycle DAS102-ADV-Year is IN_PROCESS Copy to nb-media1-hcart-robot-tld-0 of type DUPLICATE is NOT_STARTED The problem is, the backupjob is done, but it says "IN_PROCESS". I've tried the following: Cancled all jobs running on the SLP. Then manually run them again. Delete the SLP and created it again. Booted all master and media servers. When running the duplication manually from "Catalog" it works fine. And the other SLP runs just fine, duplicates to tape no problem. Any ideas?3.4KViews0likes3CommentsAccelerator for a VMWare Backup Policy with AIR
Hello Experts, I am using NBU 7.7.3. I have a VMWare policy querying a cluster for an annotation to backup some clients. This policy has 4 schedules. Each Schedule has override policy storage selection checked with a corresponding AIR (Automated Image Replication) SLP's as the selection. The Storage selected in the SLP is an EMC DataDomain Storage unit (Using OST Plugin) setup as a Source for AIR. Attached some screenshots. With this setup, Should the 'Use Accelarator' Option be available for selection on the policy? Currently I see it grayed out.3.3KViews0likes9CommentsSLP Nightmare - multiple versions of incomplete duplication
Hello All, I had to replace some hardware in a tape drive (picker & drive). The tape # changed from tld4 to tld3. Of course after the fact I'm getting errors (2001) because Version 8 of the SLP is still trying to process to tld 4 that doesn't exist. Is there an easy way to fix this? I'm a gui girl. Can I remove/delete slps? or change I modify the previous version to point to the new tld3? SLPs are great , but not when you have to modify. You either have to change all the policies or the SLP. Or create a new one, but how does that help the old images that are incomplete?Solved2.8KViews0likes10CommentsSLP configuration
Hi Everybody Question : What is the exact configuration of SLP in my scenario My scenario : we have one EMC datadomain and one HP tape library , I've planned to copy all the backups to datadomain then duplicate them to tapes .I want that data expire immediately after duplicating to tape . I will list the current configuration below , as you see by this config data does not expire after duplication .2.8KViews0likes12Comments"Postpone creation" function for SLP disappears after setting
Hi, First I would like to thank you all for this forum: you saved my day so many times during last years! This is however my first post, and it's regarding an odd behaviour of SLP definition and processing for wich I haven't found any related report. As many other customers I'm using NetBackup v 7.7.2 on a Windows Server 2008 R2 cluster environment (as Master) with two Windows Server 2008 R2 hosts as Media and a third Windows Server 2012 ad another Media with dedicated backup pools. Associated with the two "main" Media Servers are two MSDP disk pool sized about 20TB each, serving as a temporary stage area (from a minumum of 3 to a maximum of 8 days) before defined SLPs duplicate the backup images to tape for the remaining retention periods. Almost all SLPs are responsible for a second duplication to a separate tape pool for each backup image, in order to copy data for Disaster Recovery purpose. So the workflow should run like that: - Take the backup image and write it to MSDP pool with retention time X => COPY1 - Immediately after that, as per SLP window, duplicate the backup image to the DR tape pool with retention time Z (tapes are automatically counted and ejected during the next working day) => COPY3 - After time X, before primary copy expiration, duplicate the backup image to the PROD tape pool with retention time Z => COPY2 During the past few years (and incarnations) of NBU this strategy worked well, as intended: every SLP had the flag set on "Postpone creation of this copy until the source copy is about to expire" for every COPY2 duplication type. Recently I noticed that all COPY2 duplication types, inside all defined SLP, had that flag unsetted. Thinking of someone's misleading action, I personally flagged that option again (only for the COPY2 duplication job types). After about ten minutes, I checked SLP definitions, and all those settings were gone... I repeated the "flag" operation again, and after some time the setting was gone again. The worst thing is that this is not only a "display" issue, because SLP are not working as intended too: without the "Postpone creation of this copy until the source copy is about to expire" option, duplications for COPY2 starts in conjunction with duplications for COPY3, immediately after production of COPY1, resulting in higher SLP backlog and drives/tapes workload. Attached is a screen of one of those odd-acting SLPs, with evidence on the option property that simply refuses to stay flagged... Any suggestions? Thanks again and sorry for my bad english ^^' M.1.9KViews0likes3CommentsIs there any NBU command/syntax to check the duration&speed of each completed AIR/replication job?
Hi guys, I just want to know if there's a specific NBU command/syntax to get the duration and speed of replication that lapse in Activity Monitor. I've tried the command "nbstlutil" but there's no output I needed. Hoping someone can help me thank you. :( # /usr/openv/netbackup/bin/admincmd/nbstlutil repllist -U -sincetime 2021/04/03 | more /find PROD-VMWPSAPDB01_1617382856 Image: Master Server : VMLPNBUINF01 Backup ID : PROD-VMWPSAPDB01_1617382856 Client : PROD-VMWPSAPDB01 Backup Time : 1617382856 (2021/04/03 01:00:56) Policy : VMWPSAPDB01_AIR_BACKUP Client Type : 40 Schedule Type : 0 Storage Lifecycle Policy : Monthly_HO_TO_DR Storage Lifecycle State : 3 (COMPLETE) Storage Lifecycle Is Inactive : false Time In Process : 1617410995 (2021/04/03 08:49:55) Data Classification ID : (none specified) Version Number : 1 OriginMasterServer : (none specified) OriginMasterServerID : {00000000-0000-0000-0000-000000000000} Import From Replica Time : 0 (0 secs) Required Expiration Date : 0 (0 secs) Created Date Time : 1617382856 (2021/04/03 01:00:56) Copy: Master Server : VMLPNBUINF01 Backup ID : PROD-VMWPSAPDB01_1617382856 Copy Number : 102 Copy Type : 3 (REPLICATE_TO_REMOTE_MASTER) Expire Time : 1648918856 (2022/04/03 01:00:56) Expire LC Time : 1648918856 (2022/04/03 01:00:56) Try To Keep Time : 1648918856 (2022/04/03 01:00:56) Residence : *Remote*Master*:Monthly_HO_TO_DR Copy State : 5 (COPYCOMPLETE) Job ID : 70850 Retention Type : 0 (FIXED) MPX State : 0 (false) RetryCount : 4 Last Retry Time : 1621258574 (2021/05/17 21:36:14) Source : 1 Destination ID : (none specified) Replica: : 0 DataFormat : 0 (DF_UNDEFINED) SLP Index : 2 Replication Target: Source Master Server: VMLPNBUINF01 Backup ID : PROD-VMWPSAPDB01_1617382856 Copy Number : 102 Target Machine : PMLRMSDPINF01 Target Info : PureDiskVolume Remote Master : (none specified)1.7KViews0likes6Commentsconfigure SLP for duplication on tape
I am using Veritas NetBackup 7.7.3. I have configure SLP for duplication on tape. We are making three copy of my monthly backup. Primary on DataDomain, 2nd and 3rd on Tape. My queries are: How duplication will start (After completing backup job, both duplication (copy2 & copy3) will start simultaniously or copy3 will start after completing copy2)? As I saw in my environment that both copies are starting simultaniously so that case what is the recommandation for getting better performance? Can we make change so that copy3 will start after completing copy2? If yes please help me with the process.Solved1.6KViews0likes2Comments