Forum Discussion

Luv_Rai's avatar
Luv_Rai
Level 3
15 years ago

Backup failed by status code 90

Hi,

One of the Window server local drive C: backup is failed with status code 90. and D drive backup is successed.

Snapshot is enabled for this server.

Master Server: NB 7.1

Here is logs: 26/06/2011 12:57:18 - Info nbjm(pid=13900) starting backup job (jobid=161788) for client uk01app504, policy APP_OS_2003_WKLY-MTHLY_C, schedule Monthly 
26/06/2011 12:57:18 - Info nbjm(pid=13900) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=161788, request id:{B63A6213-D723-4A6C-A326-B05659BD7AC2}) 
26/06/2011 12:57:18 - requesting resource uk1net002-hcart3-robot-tld-0
26/06/2011 12:57:18 - requesting resource uk1net003.NBU_CLIENT.MAXJOBS.uk01app504
26/06/2011 12:57:18 - requesting resource uk1net003.NBU_POLICY.MAXJOBS.APP_OS_2003_WKLY-MTHLY_C
26/06/2011 12:57:19 - granted resource uk1net003.NBU_CLIENT.MAXJOBS.uk01app504
26/06/2011 12:57:19 - granted resource uk1net003.NBU_POLICY.MAXJOBS.APP_OS_2003_WKLY-MTHLY_C
26/06/2011 12:57:19 - granted resource CWH604
26/06/2011 12:57:19 - granted resource HP.ULTRIUM4-SCSI.002
26/06/2011 12:57:19 - granted resource uk1net002-hcart3-robot-tld-0
26/06/2011 12:57:19 - estimated 1 Kbytes needed
26/06/2011 12:57:19 - Info nbjm(pid=13900) started backup job for client uk01app504, policy APP_OS_2003_WKLY-MTHLY_C, schedule Monthly on storage unit uk1net002-hcart3-robot-tld-0
26/06/2011 12:57:20 - started process bpbrm (3624)
26/06/2011 12:57:27 - connecting
26/06/2011 12:57:30 - connected; connect time: 00:00:03
26/06/2011 12:57:36 - mounting CWH604
26/06/2011 12:57:48 - Info bpbrm(pid=3624) uk01app504 is the host to backup data from    
26/06/2011 12:57:52 - Info bpbrm(pid=3624) reading file list from client       
26/06/2011 12:57:57 - Info bpbrm(pid=3624) starting bpbkar32 on client        
26/06/2011 12:58:02 - Info bpbkar32(pid=2560) Backup started          
26/06/2011 12:58:02 - Info bptm(pid=5904) start           
26/06/2011 12:58:02 - Info bptm(pid=5904) using 65536 data buffer size       
26/06/2011 12:58:02 - Info bptm(pid=5904) setting receive network buffer to 263168 bytes     
26/06/2011 12:58:02 - Info bptm(pid=5904) using 30 data buffers        
26/06/2011 12:58:03 - Info bptm(pid=5904) start backup          
26/06/2011 12:58:03 - Info bptm(pid=5904) backup child process is pid 2560.5120      
26/06/2011 12:58:03 - Info bptm(pid=5904) Waiting for mount of media id CWH604 (copy 1) on server uk1net002.
26/06/2011 12:58:03 - Info bptm(pid=2560) start           
26/06/2011 12:58:20 - mounted; mount time: 00:00:44
26/06/2011 12:58:25 - positioning CWH604 to file 62
26/06/2011 12:58:46 - Info bptm(pid=5904) media id CWH604 mounted on drive index 6, drivepath {5,0,2,0}, drivename HP.ULTRIUM4-SCSI.002, copy 1
26/06/2011 13:00:27 - positioned CWH604; position time: 00:02:02
26/06/2011 13:00:27 - begin writing
26/06/2011 13:00:53 - Info bptm(pid=5904) waited for full buffer 0 times, delayed 0 times   
26/06/2011 13:00:41 - end writing; write time: 00:00:14
26/06/2011 13:00:53 - Info bptm(pid=5904) waited for full buffer 0 times, delayed 0 times   
media manager received no data for backup image(90)

Regards

Om

6 Replies

  • Please confirm that your policy type is MS-Windows and not Standard.

    Please post policy config. On master, run: bppllist <policy-name> -U

  • Policy type is already configured- MS-Windows

    Bppllist output is here:

    ------------------------------------------------------------

    Policy Name:       APP_OS_2003_WKLY-MTHLY_C

      Policy Type:         MS-Windows
      Active:              yes
      Effective date:      06/18/2004 16:54:26
      Backup network drvs: no
      Collect TIR info:    no
      Mult. Data Streams:  yes
      Client Encrypt:      no
      Checkpoint:          no
      Policy Priority:     0
      Max Jobs/Policy:     Unlimited
      Disaster Recovery:   0
      Collect BMR info:    no
      Residence:           uk1net002-hcart3-robot-tld-0
      Volume Pool:         FlatFile_Data
      Server Group:        *ANY*
      Keyword:             Windows Operating System
      Data Classification:       -
      Residence is Storage Lifecycle Policy:    no
      Application Discovery:      no
      Discovery Lifetime:      0 seconds

      Granular Restore Info:  no
      Ignore Client Direct:  no
      HW/OS/Client:  PC            WindowsNET    Uk01app525
                     PC            WindowsNET    UK01APP047
                     PC            WindowsNET    uk01app053
                     PC            WindowsNET    uk01app529
                     PC            WindowsNET    uk1app004
                     Windows-x86   Windows2003   uk01app504
                     Windows-x86   Windows2003   uk01app552
                     Windows-x86   Windows2003   uk01app543
                     Windows-x86   Windows2003   uk01app544
                     Windows-x86   Windows2003   uk01app561
                     Windows-x86   Windows2003   uk01app563
                     Windows-x86   Windows2003   uk01app564
                     Windows-x64   Windows2003   uk01app565
                     Windows-x64   Windows2003   uk01app566
                     Windows-x86   Windows2003   uk01app570
                     Windows-x86   Windows2003   uk01app571

      Include:  C:\

      Schedule:          Monthly
        Type:            Full Backup
        Maximum MPX:     12
        Synthetic:       0
        PFI Recovery:    0
        Retention Level: 10 (1 year)
        Number Copies:   1
        Fail on Error:   0
        Residence:       (specific storage unit not required)
        Volume Pool:     FlatFile_Data_EOM
        Server Group:    (same as specified for policy)
        Calendar sched: Enabled
          Friday, Week 5
          EXCLUDE DATE 0 - 01/02/2005
          EXCLUDE DATE 1 - 02/06/2005
          EXCLUDE DATE 2 - 03/06/2005
          EXCLUDE DATE 3 - 04/03/2005
          EXCLUDE DATE 4 - 05/01/2005
          EXCLUDE DATE 5 - 05/29/2005
          EXCLUDE DATE 6 - 06/05/2005
          EXCLUDE DATE 7 - 07/03/2005
          EXCLUDE DATE 8 - 08/07/2005
          EXCLUDE DATE 9 - 09/04/2005
          EXCLUDE DATE 10 - 10/02/2005
          EXCLUDE DATE 11 - 11/06/2005
          EXCLUDE DATE 12 - 12/04/2005
          EXCLUDE DATE 13 - 02/05/2006
          EXCLUDE DATE 14 - 03/05/2006
          EXCLUDE DATE 15 - 04/02/2006
          EXCLUDE DATE 16 - 09/03/2006
          EXCLUDE DATE 17 - 10/01/2006
          EXCLUDE DATE 18 - 11/05/2006
        Residence is Storage Lifecycle Policy:     0
        Daily Windows:
              Friday     20:00:00  -->  Sunday     12:00:00

      Schedule:          Weekends
        Type:            Cumulative Incremental Backup
        Maximum MPX:     12
        Synthetic:       0
        PFI Recovery:    0
        Retention Level: 3 (1 month)
        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)
        Calendar sched: Enabled
          Saturday, Week 1
          Saturday, Week 2
          Saturday, Week 3
          Saturday, Week 4
          EXCLUDE DATE 0 - 08/30/2004
          EXCLUDE DATE 1 - 12/03/2004
          EXCLUDE DATE 2 - 12/31/2004
          EXCLUDE DATE 3 - 02/25/2005
          EXCLUDE DATE 4 - 03/25/2005
          EXCLUDE DATE 5 - 03/28/2005
          EXCLUDE DATE 6 - 04/01/2005
          EXCLUDE DATE 7 - 04/29/2005
          EXCLUDE DATE 8 - 06/03/2005
          EXCLUDE DATE 9 - 07/01/2005
          EXCLUDE DATE 10 - 07/29/2005
          EXCLUDE DATE 11 - 09/02/2005
          EXCLUDE DATE 12 - 09/30/2005
          EXCLUDE DATE 13 - 10/28/2005
          EXCLUDE DATE 14 - 11/25/2005
          EXCLUDE DATE 15 - 12/30/2005
          EXCLUDE DATE 16 - 01/27/2006
          EXCLUDE DATE 17 - 02/24/2006
          EXCLUDE DATE 18 - 03/31/2006
          EXCLUDE DATE 19 - 04/28/2006
          EXCLUDE DATE 20 - 05/05/2006
          EXCLUDE DATE 21 - 05/06/2006
          EXCLUDE DATE 22 - 05/26/2006
          EXCLUDE DATE 23 - 05/27/2006
          EXCLUDE DATE 24 - 06/30/2006
          EXCLUDE DATE 25 - 07/28/2006
          EXCLUDE DATE 26 - 07/29/2006
          EXCLUDE DATE 27 - 08/25/2006
          EXCLUDE DATE 28 - 08/26/2006
          EXCLUDE DATE 29 - 09/29/2006
          EXCLUDE DATE 30 - 09/30/2006
          EXCLUDE DATE 31 - 10/27/2006
          EXCLUDE DATE 32 - 10/28/2006
          EXCLUDE DATE 33 - 11/24/2006
          EXCLUDE DATE 34 - 11/25/2006
          EXCLUDE DATE 35 - 12/29/2006
          EXCLUDE DATE 36 - 12/30/2006
          EXCLUDE DATE 37 - 09/25/2010
          EXCLUDE DATE 38 - 11/27/2010
        Residence is Storage Lifecycle Policy:     0
        Daily Windows:
              Saturday   00:00:00  -->  Sunday     23:00:00

  • So, backup for C:\  is successful for all clients, only uk01app504 is failing with status 90?

    Check Host Properties for this client and check Exclude List. See if C:\ appears in exclude list.

    If not, enable bpbkar log on client and check log after next failure for clues.

  • Go into Services and restart the snapshot (SymSnap?) service(s).  (Or reboot, which will do the same thing.)

    I have had this happen on my own Windows (XP) box a few times - in my case, I believe it is because my NetBackup client is also being backed up by BESR and some conflict is causing snapshot issues - but I completely haven't figured it out yet.  I just know that I get inexplicable status 90 errors and its cause is rooted in the fact that the snapshot doesn't "work" correctly (drilling down to the bpfis logs may confirm) and this fixes it.  Knowing how to fix it, it became a much lower priority for me to figure out why it was breaking in the first place. :)

    [ I'm trying to remember if I had ever seen status 90 before I put NetBackup 7.1 on this box, but unfortunately my memory has some holes here. ]

  • I have the same issue and have been working with support for a while, I received an EEB but it still has the issue.

    Windows 2003 cluster, the SAN drives running on the other node are causing status 90s and the EEB was suppose to have NBU 7.1 ignore the drives that are not currently active on the cluster node. This problem was not in 6.5.x or earlier.

    I tried to find the SymSnap or Symantec Snap or Veritas Snap service but saw nothing along that line on the servers, anything else to check?

  • I have Windows 2003 cluster, SAN Drives running on the other node, but Netbackuo 7.1 not Ignore the not active drives, and failed with status code 90. Was not he supposed to ignore to not active drives ?

    In the police atributtes inclue the "ALL_LOCAL_DRIVES".

    Anyone can help me ?

    Tks

    Nuno Grave