05-12-2016 03:12 PM
Hello everyone I am a little new to netbackup and the environment I am working with so please bare with me.
I have been tasked with fixing current job failures with in this environment.
Master SunOS 5.10 NB 7.6.0.4
Media Linux 2.6.18 NB 7.6.0.4
Client SunOS 5.10 NB 7.5.0.4
Current Policy has a full and a diff-inc schedule.
The full should use the policy storage listed in the schedule. Its currently failing with 144 invalid command usage.
The diff-inc is set to override the policy and backup to puredisk <media_server>_MSDP_ITC. This job is completing successfully.
From the log it appears the full is trying to write to the puredisk storage <media_server>_MSDP_ITC specified in the diff-inc override.
Any further explanation or resolution would be appreciated
Here is the status log from the job:
05/11/2016 22:30:00 - Info nbjm (pid=36) starting backup job (jobid=4644124) for client <client_name>, policy <client_name>_NFS, schedule fullbkps
05/11/2016 22:30:00 - Info nbjm (pid=36) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=4644124, request id:{6CC5E39C-17E9-11E6-8073-00144F2B2BB2})
05/11/2016 22:30:00 - requesting resource <media_server>_MSDP_ITC
05/11/2016 22:30:00 - requesting resource <master_server>.NBU_CLIENT.MAXJOBS.<client_name>
05/11/2016 22:30:00 - requesting resource <master_server>.NBU_POLICY.MAXJOBS.<client_name>_NFS
05/11/2016 22:30:01 - granted resource <master_server>.NBU_CLIENT.MAXJOBS.<client_name>
05/11/2016 22:30:01 - granted resource <master_server>.NBU_POLICY.MAXJOBS.<client_name>_NFS
05/11/2016 22:30:01 - granted resource MediaID=@aaaaW;DiskVolume=PureDiskVolume;DiskPool=<media_server>_MSPD;Path=PureDiskVolume;StorageServer=<media_server>;MediaServer=<media_server>
05/11/2016 22:30:01 - granted resource <media_server>_MSDP_ITC
05/11/2016 22:30:01 - estimated 3080995891 kbytes needed
05/11/2016 22:30:01 - begin Parent Job
05/11/2016 22:30:01 - begin Stream Discovery: Start Notify Script
05/11/2016 22:30:02 - Info RUNCMD (pid=28257) started
05/11/2016 22:30:02 - Info RUNCMD (pid=28257) exiting with status: 0
Operation Status: 0
05/11/2016 22:30:02 - end Stream Discovery: Start Notify Script; elapsed time 0:00:01
05/11/2016 22:30:02 - begin Stream Discovery: Stream Discovery
Operation Status: 0
05/11/2016 22:30:02 - end Stream Discovery: Stream Discovery; elapsed time 0:00:00
05/11/2016 22:30:02 - begin Stream Discovery: Policy Execution Manager Preprocessed
Operation Status: 144
05/12/2016 08:49:43 - end Stream Discovery: Policy Execution Manager Preprocessed; elapsed time 10:19:41
05/12/2016 08:49:43 - begin Stream Discovery: Stop On Error
Operation Status: 0
05/12/2016 08:49:43 - end Stream Discovery: Stop On Error; elapsed time 0:00:00
05/12/2016 08:49:43 - begin Stream Discovery: End Notify Script
05/12/2016 08:49:43 - Info RUNCMD (pid=10951) started
05/12/2016 08:49:43 - Info RUNCMD (pid=10951) exiting with status: 0
Operation Status: 0
05/12/2016 08:49:43 - end Stream Discovery: End Notify Script; elapsed time 0:00:00
Operation Status: 144
05/12/2016 08:49:43 - end Parent Job; elapsed time 10:19:42
invalid command usage (144)
Thanks, Gary
Solved! Go to Solution.
05-13-2016 12:10 AM
05-12-2016 07:34 PM
Can you show us, how you configured the policy ?
run command on Master "/usr/openv/netbackup/bin/bppllist <policy name>
05-12-2016 07:43 PM
05-12-2016 08:05 PM
05-12-2016 08:17 PM
Here is the policy configuration
# ./bppllist <client_name>_NFS -U
------------------------------------------------------------
Policy Name: <client_name>_NFS
Policy Type: Standard
Active: yes
Effective date: 12/31/1969 19:00:00
Client Compress: no
Follow NFS Mounts: no
Cross Mount Points: no
Collect TIR info: no
Block Incremental: no
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: no
Policy Priority: 10
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: SLP_ITC_Unixnet_Disk6mon_Tape3yr_<media_server>
Volume Pool: Unix_Net_Clients
Server Group: *ANY*
Keyword: (none specified)
Data Classification: Silver
Residence is Storage Lifecycle Policy: yes
Application Discovery: no
Discovery Lifetime: 0 seconds
ASC Application and attributes: (none defined)
Granular Restore Info: no
Ignore Client Direct: no
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: yes
HW/OS/Client: Solaris Solaris_x86_1 <client_name>
Include: /attach
/diskvsnpool0/websrv-dump
/WTserver
/diskvsnpool0/AdobeDownloads
/diskvsnpool0/Claptop
/diskvsnpool0/EXCHG
/diskvsnpool0/appsrv-logs
/diskvsnpool0/attachments-dump
/zipattach
Schedule: fullbkps
Type: Full Backup
Frequency: every 28 days
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Maximum MPX: 10
Retention Level: 9 (infinity)
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
Schedule indexing: 0
Daily Windows:
Sunday 22:30:00 --> Monday 06:00:00
Monday 22:30:00 --> Tuesday 06:00:00
Tuesday 22:30:00 --> Wednesday 06:00:00
Wednesday 22:30:00 --> Thursday 06:00:00
Thursday 22:30:00 --> Friday 06:00:00
Friday 22:30:00 --> Saturday 06:00:00
Saturday 22:30:00 --> Sunday 06:00:00
Schedule: userbkps
Type: User Backup
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 10
Retention Level: 9 (infinity)
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
Schedule indexing: 0
Daily Windows:
Monday 08:00:00 --> Monday 16:00:00
Tuesday 08:00:00 --> Tuesday 16:00:00
Wednesday 08:00:00 --> Wednesday 16:00:00
Thursday 08:00:00 --> Thursday 16:00:00
Friday 08:00:00 --> Friday 16:00:00
Schedule: userarch
Type: User Archive
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 10
Retention Level: 8 (1 year)
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
Schedule indexing: 0
Daily Windows:
Monday 08:00:00 --> Monday 16:00:00
Tuesday 08:00:00 --> Tuesday 16:00:00
Wednesday 08:00:00 --> Wednesday 16:00:00
Thursday 08:00:00 --> Thursday 16:00:00
Friday 08:00:00 --> Friday 16:00:00
Schedule: incrbkps
Type: Differential Incremental Backup
Frequency: every 1 day
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
PFI Recovery: 0
Maximum MPX: 10
Retention Level: 5 (3 months)
Number Copies: 1
Fail on Error: 0
Residence: <media_server>_MSDP_ITC
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Sunday 22:30:00 --> Monday 06:00:00
Monday 22:30:00 --> Tuesday 06:00:00
Tuesday 22:30:00 --> Wednesday 06:00:00
Wednesday 22:30:00 --> Thursday 06:00:00
Thursday 22:30:00 --> Friday 06:00:00
Friday 22:30:00 --> Saturday 06:00:00
Saturday 22:30:00 --> Sunday 06:00:00
#
05-12-2016 08:21 PM
We see that you are using SLP for Full Schedule.
Residence: SLP_ITC_Unixnet_Disk6mon_Tape3yr_<media_server>
Now, we do not know what storage units are used in SLP.
Can you Marriane's questions first, as why you want to backup full and incre on different storage units ?
05-12-2016 08:36 PM
05-12-2016 11:08 PM
This link should work ...
https://www.veritas.com/support/en_US/article.000022706
05-13-2016 12:10 AM
05-13-2016 07:53 AM
Marianne
"Why would you want to send Full and Incr to different Storage Unit? When backing up to dedupe storage, it does not make sence to only backup Incrementals to it."
I am not sure why it has been setup this way again I am just taking over whats in place.
Your Solaris client also seems to be an older version (7.5.x). Any reason why it has not been upgraded yet?
This I dont know either
Did backups work fine for this client previously?
As far back as I could see in the activity monitor it has failed.
I did read over the tech note.
Upgrading the client did resolve the issue.
Thanks for the support on this everyone!
05-13-2016 09:18 AM