cancel
Showing results for 
Search instead for 
Did you mean: 

EXIT STATUS 1: the requested operation was partially successful

Alaaeddine
Level 2

Hi All,

I have a problem with several Backup's that they are not ending with full success :(

it's always with the same message : "status: 1: the requested operation was partially successful"

you will find the output of the Job attached with this statu.

I need your help please.

Best Regards

 

09/27/2020 01:59:13 - Info bpbkar(pid=10436) 100000 entries sent to bpdbm
09/27/2020 02:14:55 - Info bpbkar(pid=10436) change journal enabled for <V:\\>
09/27/2020 02:15:37 - Info bpbkar(pid=10436) NOT using change journal data for <V:\\>: unable to validate change journal usage <rea\
son=previous backup wasn't a successful backup>
09/27/2020 03:30:06 - Info bpbkar(pid=10436) 150000 entries sent to bpdbm
09/27/2020 03:31:21 - Info bpbkar(pid=10436) accelerator sent 261163726336 bytes out of 535463103488 bytes to server, optimization \
51.2%
09/27/2020 03:31:22 - Info bptm(pid=174644) waited for full buffer 53527 times, delayed 466827 times
09/27/2020 03:31:27 - Info bptm(pid=174644) EXITING with status 0 <----------
09/27/2020 03:31:27 - Info frcp00nbu002(pid=174644) StorageServer=PureDisk:frcp00nbu002; Report=PDDO Stats for (frcp00nbu002): scan\
ned: 522939389 KB, CR sent: 34895873 KB, CR sent over FC: 0 KB, dedup: 93.3%, cache disabled
09/27/2020 03:31:27 - Info bpbrm(pid=174597) validating image for client frcp00ppd0371-sav
09/27/2020 03:31:28 - Info bpbkar(pid=10436) done. status: 1: the requested operation was partially successful
09/27/2020 01:39:29 - end writing; write time: 002:39:02

1 ACCEPTED SOLUTION

Accepted Solutions

davidmoline
Level 6
Employee

The reason for the status 1's are contained in the log file you attached - they are the warning messages, mostly about being unable to backup files in use by another process. 

A number of options available

  • ignore the errors (status 1 isn't generally a problem).
  • determine what process is using the files and stopping it (this may not be as simply as it sounds), getting everyone to log off would remove most of your warnings (although it looks like the accounts might be service accounts)
  • exclude those files that are causing the problems (most look like registry hives or other transient files that typically aren't critical, but may be so exclude with care). 

A suggestion to help the backup, you might want to investigate looking at multistreaming you backup, so each drive has its own backup job. This wont do anything to reduce the warnings you are receiving, but may better identify where the errors are occurring. An added advantage of doing this is that the backup may complete more quickly as you should be able to run multiple jobs at one time (assuming the server can cope with the additional load).

View solution in original post

1 REPLY 1

davidmoline
Level 6
Employee

The reason for the status 1's are contained in the log file you attached - they are the warning messages, mostly about being unable to backup files in use by another process. 

A number of options available

  • ignore the errors (status 1 isn't generally a problem).
  • determine what process is using the files and stopping it (this may not be as simply as it sounds), getting everyone to log off would remove most of your warnings (although it looks like the accounts might be service accounts)
  • exclude those files that are causing the problems (most look like registry hives or other transient files that typically aren't critical, but may be so exclude with care). 

A suggestion to help the backup, you might want to investigate looking at multistreaming you backup, so each drive has its own backup job. This wont do anything to reduce the warnings you are receiving, but may better identify where the errors are occurring. An added advantage of doing this is that the backup may complete more quickly as you should be able to run multiple jobs at one time (assuming the server can cope with the additional load).