NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 2826

NetBackup status code : 2826
HOWTO105083 | 2014-11-20
How To | CMS-XML

Restore data failed with status code 2826

Restore data failed with status code 2826
TECH187237 | 2013-12-23
Technical Solutions | CMS-XML

NDMP restore of backup files from a Celerra NDMP host to a NetApp NDMP host failing with status 2826.

NDMP restore of backup files from a Celerra NDMP host to a NetApp NDMP host failing with status 2826 .
TECH179929 | 2012-07-28
Technical Solutions | CMS-XML

restore by bprestore command fails with status 2826 | Symantec Connect

restore by bprestore command fails with status 2826
Connect Forums | HTML

I am getting same error 2826 while restoring | Symantec Connect

I am getting same error 2826 while restoring
Connect Forums | HTML

NDMP Restore job failing with Error code 2826 | Symantec Connect

NDMP Restore job failing with Error code 2826 Hi, Please help me with a solution to get over of a solution on restore failure code 2826 . 6/28/2013 20:59:26 - begin Restore
Connect Forums | HTML

Restore complete with "invalid error number(2826)" | Symantec Connect

Restore complete with "invalid error number( 2826 )"
Connect Forums | HTML

User directed restores initiated by bprestore using a -R rename file on a UNIX client timeout with status 41.

User directed restore on an Unix client may fail with a exit status code 41 and the error message Invalid status code ( 2826 ) can be observed in the job details at version 7.1, or may fail with a exit status code 13 and record the message Standard Policy Restore Error (2800) to the job details at version 7.5 when the rename file used with the bprestore command is improperly formatted.
TECH203205 | 2013-06-21
Technical Solutions | CMS-XML

Overwrite restore of fonts files fails with "WIN32 1224" errors for Windows 2008 R2 SP1 clients.

In Activity Monitor, Job State “Incomplete”, Status 2826 ” is reported for the restore job. -- Job Details -- 2012/03/26 12:59:49 - Error bpbrm(pid=4140) from client nbusup58-v2: ERR - unable to restore C:\Windows\Fonts\corbelb.ttf (WIN32 1224: The requested operation cannot be performed on a file with a user-mappedsection open.)
TECH184748 | 2012-04-12
Technical Solutions | CMS-XML

AIX Restore with error | Symantec Connect

AIX Restore with error 6/20/2013 8:59:34 AM - end Restore; elapsed time: 00:09:24 invalid error number( 2826 ) I found on some forum which mention that the reason of failure is the file structure different between AIX and Windows, so there are no way to restore it to the windows platform, is it true?
Connect Forums | HTML

Restore failed with 2826 | Symantec Connect

Restore failed with 2826 05/20/2012 00:59:38 - begin reading 05/20/2012 00:59:38 - Info bpbrm (pid=27991) sending media manager msg: CONTINUE RESTORE 05/20/2012 01:00:03 - Warning bpbrm (pid=27996) from client tus1ttnwebpeb03: WRN - error writing file: C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\2.Settings.LiveUpdate
Connect Forums | HTML

Status Code Chart

2820 2826 2828
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

error in restore in another media server | Symantec Connect

error in restore in another media server apending request has been geberated for this resource request after 15 minutes (the time that we defined as timeout interval) we get the message invalid error number ( 2826 ) REGARDS : HAIM
Connect Forums | HTML

Status 183 - Tar received an invalid archive | Symantec Connect

Status 183 - Tar received an invalid archive 07/09/2012 03:12:31 - end Restore; elapsed time 2:31:00 Failed to get status code information ( 2826 ) Kindly request your commnets on the same
Connect Forums | HTML

Storage lifecycle polices and Snapshot Client troubleshooting

[2826] 32 rebuild_fim_list: FTL - timefinder_rebuild: Cannot get lock on device: /dev/rdsk/c3t5006048c4a85a400d1s2 00:26:19.025 [2826] 32 splthost_rebuild: FTL - rebuild_fim_list() failed 00:26:19.037 [ 2826 ] 4 bpfis Exit: INF - EXIT STATUS 156: snapshot error encountered
HOWTO88361 | 2013-09-30
How To | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?