cancel
Showing results for 
Search instead for 
Did you mean: 

Import jobs not starting at target site after successful replication at source

Hello team,

Import jobs not starting at target site,but replication is successful at source. nbstlutil pendimplist  show Storage Lifecycle State is "2 (IN PROCESS)". The time of all backup servers is synchronized. How can I solve this problem?

James86_0-1621566627702.png

Image:
Master Server : JLF9BKMAS
Backup ID : dj-3_1621393415
Client : dj-3
Backup Time : 1621393415 (2021/05/19 11:03:35)
Policy : (none specified)
Client Type : 0
Schedule Type : 0
Storage Lifecycle Policy : SLP-01-RPL-6M
Storage Lifecycle State : 2 (IN_PROCESS)
Storage Lifecycle Is Inactive : false
Time In Process : 1621394182 (2021/05/19 11:16:22)
Data Classification ID : (none specified)
Version Number : 0
OriginMasterServer : CPF9BKMAS
OriginMasterServerID : {00000000-0000-0000-0000-000000000000}
Import From Replica Time : 0 (0 secs)
Required Expiration Date : 0 (0 secs)
Created Date Time : 1621393936 (2021/05/19 11:12:16)

Copy:
Master Server : JLF9BKMAS
Backup ID : dj-3_1621393415
Copy Number : 1
Copy Type : 4 (IMPORT)
Expire Time : 0 (0 secs)
Expire LC Time : 0 (0 secs)
Try To Keep Time : 0 (0 secs)
Residence : STU-JLF9BK01MED-MSDP
Copy State : 1 (NOT_STARTED)
Job ID : 0
Retention Type : 0 (FIXED)
MPX State : 0 (false)
RetryCount : 0
Last Retry Time : 0 (0 secs)
Source : 0
Destination ID : (none specified)
Replica: : 0
DataFormat : 0 (DF_UNDEFINED)
SLP Index : 1

Fragment:
Master Server : JLF9BKMAS
Backup ID : dj-3_1621393415
Copy Number : 1
Fragment Number : -2147482648
Resume Count : 0
Media ID : @aaaab
Media Server : JLF9BK01MED
Storage Server : (none specified)
Media Type : 0 (DISK)
Media Sub-Type : 0 (DEFAULT)
Fragment State : 1 (ACTIVE)
Fragment Size : 0
Delete Header : 0
Fragment ID : dj-3_1621393415_C1_IM
Snap MountHost : (none specified)
Media Description : JLF9BK01MED

Image:
Master Server : JLF9BKMAS
Backup ID : dj-3_1621393608
Client : dj-3
Backup Time : 1621393608 (2021/05/19 11:06:48)
Policy : (none specified)
Client Type : 0
Schedule Type : 0
Storage Lifecycle Policy : SLP-01-RPL-6M
Storage Lifecycle State : 2 (IN_PROCESS)
Storage Lifecycle Is Inactive : false
Time In Process : 1621394486 (2021/05/19 11:21:26)
Data Classification ID : (none specified)

...

Tags (2)
8 Replies

Re: Import jobs not starting at target site after successful replication at source

Hello @James86 

It looks like SLP is active but still imports are not starting. You will need to capture nbstserv (master) and spoold and spad logs (target media) from target environment.

post the logs here if possible.

Re: Import jobs not starting at target site after successful replication at source

Thank you pats_729 for your help!

I have added the nbstserv log to the attachment. Which directory should I capture the other two logs from target media?

Tags (2)

Re: Import jobs not starting at target site after successful replication at source

Hello @James86 

If this is BYO media server then look for log files at

/storage_path/log/spad 

/storage_path/log/spoold

if this is a NBU appliance then look for log files at

/msdp/data/dp1/pdvol/log/spoold/spoold.log

 

Re: Import jobs not starting at target site after successful replication at source

@James86 

i reviewed the nbstserv logs and i see following message for all imports

[ImageMgr::GroupingAssignment] Image dj-3_1621393415, index 1 cannot be assigned to a workgroup, status= 130(ImageManager.cpp:2613)
[DsmAccess::getDiskServerTypeByMediaId] failed to get disk volume info: media id = @aaaab(DsmAccess.cpp:197)

It looks like its not able to find @aaaab media pool (Netbackkup assigns this media id to disk pools).

Did you tried restarting NetBackup services on Master and Media yet ? This error was resolved for me after a clean service recycle.

Re: Import jobs not starting at target site after successful replication at source

@pats_729

Thank you for your advice.

I have restarted NetBackup services on Master and Media during this period, but it hasn't been solved. Since the May 21, the report job and import job are all normal, but the previous import job is still "in process" status.

Attached are the logs of spad and spoold. Please help to analyze them,thank you!

Tags (2)

Re: Import jobs not starting at target site after successful replication at source

Hello,
We had a similar issue before, it was resolved by running this command :
usr/openv/netbackup/bin/admincmd/nbstlutil dropwg.

Hope this helps.

BR

Re: Import jobs not starting at target site after successful replication at source

@hha_mea 

Thanks  for your sharing. I also saw your previous post. I didn't see the option of dropwg in the commands reference guide, so I'm not sure about the meaning of the command nbstlutil dropwg.

Solved: A.I.R replication & Import jobs don’t start - VOX (veritas.com)

Tags (2)

Re: Import jobs not starting at target site after successful replication at source

Hello,
I don’t think there is a harm executiing that command because its like droping the previous workgroups (wg) and goes with new ones.
We did it few times and it always solves our problems due to imports not executing