Forum Discussion

ipmanyak's avatar
ipmanyak
Level 5
6 years ago
Solved

Info bpbkar32(pid=0) done. status: 31: could not set user id for process

The policy type is  User Backup. Client  - Windows 2008. The job ceased to work 3-4 days ago.

----------

21.08.2019 9:39:17 - Info nbjm(pid=2656) starting backup job (jobid=298954) for client tmn-meridian-db, policy tmn-meridiandb, schedule usersched
21.08.2019 9:39:17 - Info nbjm(pid=2656) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=298954, request id:{0A9E27CA-6895-4BA0-8E9A-14FD2777C9D2})
21.08.2019 9:39:17 - requesting resource four_backup_stu
21.08.2019 9:39:17 - requesting resource tmn-backup.NBU_CLIENT.MAXJOBS.tmn-meridian-db
21.08.2019 9:39:17 - requesting resource tmn-backup.NBU_POLICY.MAXJOBS.tmn-meridiandb
21.08.2019 9:39:17 - granted resource tmn-backup.NBU_CLIENT.MAXJOBS.tmn-meridian-db
21.08.2019 9:39:17 - granted resource tmn-backup.NBU_POLICY.MAXJOBS.tmn-meridiandb
21.08.2019 9:39:17 - granted resource MediaID=@aaaed;DiskVolume=K:\;DiskPool=four_pool;Path=K:\;StorageServer=tmn-backup;MediaServer=tmn-backup
21.08.2019 9:39:17 - granted resource four_backup_stu
21.08.2019 9:39:18 - estimated 0 Kbytes needed
21.08.2019 9:39:18 - Info nbjm(pid=2656) started backup (backupid=tmn-meridian-db_1566362357) job for client tmn-meridian-db, policy tmn-meridiandb, schedule usersched on storage unit four_backup_stu
21.08.2019 9:39:18 - started process bpbrm (5928)
21.08.2019 9:39:22 - Info bpbrm(pid=5928) tmn-meridian-db is the host to backup data from
21.08.2019 9:39:22 - Info bpbrm(pid=5928) reading file list from client
21.08.2019 9:39:22 - connecting
21.08.2019 9:39:24 - Info bpbrm(pid=5928) starting bpbkar32 on client
21.08.2019 9:39:24 - connected; connect time: 00:00:02
21.08.2019 9:39:25 - Error bpbrm(pid=5928) from client tmn-meridian-db: ERR - setuid failed
21.08.2019 9:39:25 - Info bpbkar32(pid=0) done. status: 31: could not set user id for process
21.08.2019 9:39:25 - Info bpbkar32(pid=0) done. status: 31: could not set user id for process
21.08.2019 9:39:25 - end writing
could not set user id for process(31)

-----------

All necessary services Veritas on client side are started

Name schedule usersched  is identical on master server and client.

I have one more policy  to the same client with type backup MS-Windows and  it works successfully.

What ideas ?

7.5
Windows Server 2003
  • ipmanyak's avatar
    ipmanyak
    6 years ago

    A few days ago the server was restarted. I  found out that service  "NetBackup Legacy Client Service" not running though there is an automatic start. I started it  manually. Then for test  I run

    "C:\Program Files\Veritas\NetBackup\bin\bpbackup.exe" -p tmn-meridiandb -s usersched -L h:\backups\bpbackup.log h:\backups\*.bak

    but unsuccessfully with same status: 31: could not set user id for process.

    1 hour later I remembered that the admin in windows is not an Administrator. :)

    Then I run  cmd.exe as Administrator and my command started successfully .

     

     

2 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    6 years ago

    The problem is with the user id used with this specific backup:

    could not set user id for process

    How is the job kicked off?
    If this is a script kicked off by Windows scheduler or another 3rd-party scheduler, then have a look under which user credentials the job is started.
    Is the user profile still active? 
    Did the user password change?

    So, all troubleshooting should be done on the client, investigating the user credentials for this job. 

    • ipmanyak's avatar
      ipmanyak
      Level 5
      6 years ago

      A few days ago the server was restarted. I  found out that service  "NetBackup Legacy Client Service" not running though there is an automatic start. I started it  manually. Then for test  I run

      "C:\Program Files\Veritas\NetBackup\bin\bpbackup.exe" -p tmn-meridiandb -s usersched -L h:\backups\bpbackup.log h:\backups\*.bak

      but unsuccessfully with same status: 31: could not set user id for process.

      1 hour later I remembered that the admin in windows is not an Administrator. :)

      Then I run  cmd.exe as Administrator and my command started successfully .