12-03-2012 08:40 AM
I’m getting the following error when backing up my NAS sometimes “network connection timed out(41)”. I saw that you can change the client properties from a 300 second timeout to something higher. However, I was if someone has done anything else to fix this error on a NAS system.
11/30/2012 6:30:00 PM - Info nbjm(pid=6196) starting backup job (jobid=1369647) for client vcpinas01_xb4, policy 00085-NAS, schedule 00085-NAS-Full
11/30/2012 6:30:00 PM - Info nbjm(pid=6196) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1369647, request id:{712B88BC-791D-493B-810B-1D24669AB827})
11/30/2012 6:30:00 PM - requesting resource ExaGrid08-NAS01-MKE
11/30/2012 6:30:00 PM - requesting resource 00807master01.NBU_CLIENT.MAXJOBS.vcpinas01_xb4
11/30/2012 6:30:00 PM - requesting resource 00807master01.NBU_POLICY.MAXJOBS.00085-NAS
11/30/2012 6:30:57 PM - granted resource 00807master01.NBU_CLIENT.MAXJOBS.vcpinas01_xb4
11/30/2012 6:30:57 PM - granted resource 00807master01.NBU_POLICY.MAXJOBS.00085-NAS
11/30/2012 6:30:57 PM - granted resource MediaID=@aaacI;DiskVolume=Exa08NAS.ExaMKE08.VCPImke;DiskPool=ExaGrid08-NAS-MKE;Path=Exa08NAS.ExaMKE08.VCPImke;StorageServer=VCPImke;MediaServer=00807media02.vcpi.com
11/30/2012 6:30:57 PM - granted resource ExaGrid08-NAS01-MKE
11/30/2012 6:31:03 PM - estimated 666901612 Kbytes needed
11/30/2012 6:31:03 PM - begin Parent Job
11/30/2012 6:31:03 PM - begin Stream Discovery, Start Notify Script
11/30/2012 6:31:03 PM - Info RUNCMD(pid=17456) started
11/30/2012 6:31:04 PM - Info RUNCMD(pid=17456) exiting with status: 0
Status 0
11/30/2012 6:31:04 PM - end Stream Discovery, Start Notify Script; elapsed time: 00:00:01
11/30/2012 6:31:04 PM - begin Stream Discovery, Stream Discovery
Status 0
11/30/2012 6:31:04 PM - end Stream Discovery, Stream Discovery; elapsed time: 00:00:00
11/30/2012 6:31:04 PM - begin Stream Discovery, Policy Execution Manager Preprocessed
Status 41
12/1/2012 1:34:50 PM - end Stream Discovery, Policy Execution Manager Preprocessed; elapsed time: 19:03:46
12/1/2012 1:34:50 PM - begin Stream Discovery, Stop On Error
Status 0
12/1/2012 1:34:50 PM - end Stream Discovery, Stop On Error; elapsed time: 00:00:00
12/1/2012 1:34:50 PM - begin Stream Discovery, End Notify Script
12/1/2012 1:34:50 PM - Info RUNCMD(pid=31640) started
12/1/2012 1:34:51 PM - Info RUNCMD(pid=31640) exiting with status: 0
Status 0
12/1/2012 1:34:51 PM - end Stream Discovery, End Notify Script; elapsed time: 00:00:01
Status 41
12/1/2012 1:34:51 PM - end Parent Job; elapsed time: 19:03:48
network connection timed out(41)
12-03-2012 09:10 AM
Status 41
12/1/2012 1:34:50 PM - end Stream Discovery, Policy Execution Manager Preprocessed; elapsed time: 19:03:46
12/1/2012 1:34:50 PM - begin Stream Discovery, Stop On Erro
elapsed time is 19 hours, seems it tried hard before to go for failure.
what is the netbackup Version , and what is the method of NDMP backup that you are following
local, 3-way or Rremote?
did you check if the Volumes are avaliabe in the NAS failer, and authentications and alll?
12-03-2012 11:11 AM
The version of NB I'm running is 7.1.0.3 and am doing a Remote NDMP. I did check that NAS volumes are avaliable , and that I can authenticate. Is there a good log dir that I can look into for more info? bprd???
12-03-2012 11:29 AM
I may be wrong. but job details looks more like a normal filesystem backup than NDMP backup?
Please show us policy config:
bppllist <policy-name> -U
12-03-2012 12:46 PM
bppllist 00085-NAS -U
------------------------------------------------------------
Policy Name: 00085-NAS
Policy Type: NDMP
Active: yes
Effective date: 07/29/2011 12:00:00
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: no
Policy Priority: 98
Max Jobs/Policy: 4
Disaster Recovery: 0
Collect BMR info: no
Residence: ExaGrid08-NAS
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: yes
Application Discovery: no
Discovery Lifetime: 0 seconds
Granular Restore Info: no
Ignore Client Direct: no
HW/OS/Client: NDMP NDMP vcpinas01_xb4
Include: SET TYPE=tar
/root_vdm_24/0085VDM_UFS3
/root_vdm_24/0085VDM_FS2
/root_vdm_24/0085VDM_FS3
/root_vdm_24/0085VDM_FS4
/root_vdm_24/0085VDM_FS5
/root_vdm_24/0085VDM_FS6
/root_vdm_24/0085VDM_FS7
/root_vdm_24/0085VDM_UFS1
/root_vdm_24/0085VDM_UFS2
/root_vdm_24/0085VDM_UFS4
/root_vdm_24/0085VDM_UFS5
/root_vdm_24/0085VDM_UFS6
/root_vdm_46/EHS80085VDM_FS1
/NASSTORAGE01
Schedule: 00085-NAS-Full-Monthly
Type: Full Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 13 (3 years)
Number Copies: 1
Fail on Error: 0
Residence: 00085-NAS-Monthly
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Allowed to retry after run day
Friday, Week 3
Residence is Storage Lifecycle Policy: 1
Daily Windows:
Friday 18:30:00 --> Monday 05:40:00
Schedule: 00085-NAS-Full
Type: Full Backup
Frequency: every 4 days
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 10 (60 days)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Friday 18:30:00 --> Monday 05:40:00
Schedule: 00085-NAS-Differential
Type: Differential Incremental Backup
Frequency: every 16 hours
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 10 (60 days)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Monday 19:40:00 --> Tuesday 06:00:00
Tuesday 19:40:00 --> Wednesday 06:00:00
Wednesday 19:40:00 --> Thursday 06:00:00
Thursday 19:40:00 --> Friday 06:00:00
Thanks for the help....