Windows 8

553 Topics

Windows 10 System State restore fails
I'm trying to simulate a disaster recovery on a windows 10 system. The only changes to the system beyond a bare Win10 installation were: Skype installed with credentials saved and a registry entry created. I successfully backed up the system two ways: • System state and the c:\ drive with all components saved (Simplified Disaster Recovery enabled was checked) • System state and the c:\drive selected with the c:\temp directory unselected (which prevents SDR from being checked) I restored the system from both backups on top of a bare windows 10 installation. First restore: using the "Complete online restore" + "fully selected backup/disaster recovery". The restore failed with a ton of errors about ProgramFiles\WindowsApps failing due to access denied. This was documented elsewhere as expected because of Win10 permission problems. After restore, both the registry key and Skype were correctly restored. (YAY!) Second restore: using the "Complete online restore" + "System State" I was able to select the c:\ and system state from the 2nd backup (which didn't include c:\temp). The c:\ restore failed with the same access denied issues. The system state restore completed with no errors. After the restore, the file system was properly restore, but the registry WAS NOT restored, and skype would not run properly (because it was not installed). This indicates to me that the System State (at least the registry) DID NOT restore. Any insights? I've run an insane number of simulations and I always get the same results. I've confirmed the group policy for the backup operators is setup properly, I've tried with both "overwrite all files" and "skip if existing files are newer", restoring just the registry separately on top of the other restores, restoring just the registry from the SDR, etc. This is driving me crazy.
Solved
rlittletht
24 days ago Place Backup Exec
2.6KViews
0likes
4Comments
Convert Netbackup Appliance 5250 to Flex Appliance 5250.
Hi everyone, I understand that the NetBackup Appliance 5250 is great, but it lacks WORM (Immutable). I would like to inquire if it's possible to convert the NetBackup Appliance 5250 to a Flex Appliance 5250. Thanks, Rick.
rformas-LOL
2 years ago Place NetBackup
1.2KViews
0likes
2Comments
'shadow copy components'
Hello, When we use ALL_LOCAL_DRIVES, the backup is blocked because of the components 'shadow copy components' with the status code 50 the best collection of new porn available on the net https://newpornsites.pro
midocoma
4 years ago Place NetBackup
1.2KViews
0likes
3Comments
Slow CIFS backups
WE have CIFS shares on a netapp device. Backup of these shares has gotten extremely slow. (From about 8-10 mb/sec to 200-400 kb/sec. I have noticed that when this happens, the snapshot fails also. Am I correct in thinking that If the snapshot (or snapvault) fails, then the backup is taken from the disk itself, and not from the snapshot. If there are others using the netapp (and there are many) this would cause a drastic decrease in the read time on the netapp ?
mdmiles125
5 years ago Place NetBackup
1.1KViews
0likes
2Comments
Off to a bad start with System Recovery 2013 R2 SP4
I was glad to see the long awaited System Recovery 2013 R2 SP4 version out today so I downloaded it and thought I'd get right to testing it on my first system. Unfortunatly, I cannot even install the product. I'm trying to install on a system with the following characteristics: ------------ Intel Core i7 Processor 32GB RAM Boot Drive is a 500GB SSD OS is Windows 10 with the November 2015 update, 64-Bit ------------ I launch the install by running "browser.exe". I get the initial welcome screen with the various elements such as Getting Started, Installation, etc. At this point I click on "Install Now". At this point a screen opens that says "Loading the install. Please wait..." but within about 2 seconds the screen disappears and nothing more happens. Note that there is no error message, the program just seems to go away completely and the "Setup Launcher" disappears from the task list if I'm monitoring it while I attempt the install. As a test, I tried the install on a Windows 7 system and it worked perfectly. Is this possibly a problem with the November Update to Windows 10? I sure hope that we don't have to wait for another update that supports the November Update :-) Anyone else having any better luck than me?
Solved
Hans05
5 years ago Place System Recovery
6.3KViews
2likes
47Comments
SSR2013 - ERROR: Installation failed with error -532462766.
Hey everybody, For some reason the Symantec website does not let me create a new support case (times out), therefor I'm hoping this forum might be of any help. I'm trying to install SSR2013 R2 for one of my clients (W8.1 Pro 64bit). When I run browser.exe or the SSRx64 setup.exe the installation starts with the message 'Loading the install. Please wait... ‘. After a few seconds this message disappears and the setup ends without reporting a clear error. However I checked the SSRINST.html file within the C:\ProgramData\Symantec\SYMANTEC SYSTEM RECOVERY\LOGS folder. It reports the following error: Symantec System Recovery (TM) 2013 R2 Installation Log 02-09-2015,09:39:31 : EnumProcesses Counts: 79 02-09-2015,09:39:31 : OS is Windows 8 or Windows 2012. 02-09-2015,09:39:31 : The OS product type is Workstation. 02-09-2015,09:39:33 : Executing managed _Setup: 02-09-2015,09:39:33 : C:\Users\Voip\Downloads\SSR\Sym_System_Recovery_2013R2_11.1.0.53728_Multilingual_Product\SSR\SSRx64\Install\_Setup.exe 02-09-2015,09:39:35 : ERROR: Installation failed with error -532462766. GetLastError = :0 As test, I also tried to install SSR2013 (so not the R2 version) but it reports a similar error: Symantec System Recovery (TM) 11.0 Installation Log 02-09-2015,11:27:17 : EnumProcesses Counts: 76 02-09-2015,11:27:17 : OS is Windows 8 or Windows 2012. 02-09-2015,11:27:17 : The OS product type is Workstation. 02-09-2015,11:27:19 : Executing managed _Setup: 02-09-2015,11:27:19 : C:\Users\Voip\Downloads\Sym_System_Recovery_2013_11.0.2.49853_Multilingual_Product\SSR\SSRx64\Install\_Setup.exe 02-09-2015,11:27:21 : ERROR: Installation failed with error -532462766. GetLastError = :0 Support would be appreciated. Thank you.
Solved
andydtn
6 years ago Place System Recovery
4.2KViews
0likes
9Comments
Backups are failing with error code 84 after writing 16gb of data in desktop
Hi All , Backup for one of the Lab PC is getting faled with 84 after writing some data .Please help me on this . Dec 15, 2019 12:31:16 PM - Info nbjm (pid=90913) starting backup job (jobid=5862919) for client 07r-malvern02, policy GOLD-FS-07R-LABPC-GRP1, schedule Weekly Dec 15, 2019 12:31:16 PM - Info nbjm (pid=90913) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=5862919, request id:{B27CAD80-1F60-11EA-9361-F55878484892}) Dec 15, 2019 12:31:16 PM - requesting resource MGW_FS_STG Dec 15, 2019 12:31:16 PM - requesting resource u0bpnbuma02.NBU_CLIENT.MAXJOBS.07r-malvern02 Dec 15, 2019 12:31:16 PM - granted resource u0bpnbuma02.NBU_CLIENT.MAXJOBS.07r-malvern02 Dec 15, 2019 12:31:16 PM - granted resource MediaID=@aaaas;DiskVolume=fs_lsu;DiskPool=mgw_fs_pool;Path=fs_lsu;StorageServer=s07dd002;MediaServer=w07pnbume02.myl.com Dec 15, 2019 12:31:16 PM - granted resource w07pnbume07_MGW_FS_STU Dec 15, 2019 12:31:17 PM - estimated 33184826 kbytes needed Dec 15, 2019 12:31:17 PM - Info nbjm (pid=90913) started backup (backupid=07r-malvern02_1576431077) job for client 07r-malvern02, policy GOLD-FS-07R-LABPC-GRP1, schedule Weekly on storage unit w07pnbume07_MGW_FS_STU Dec 15, 2019 12:31:18 PM - started process bpbrm (pid=3368) Dec 15, 2019 12:31:53 PM - Info bpbrm (pid=3368) 07r-malvern02 is the host to backup data from Dec 15, 2019 12:31:53 PM - Info bpbrm (pid=3368) reading file list for client Dec 15, 2019 12:32:01 PM - connecting Dec 15, 2019 12:32:23 PM - connected; connect time: 0:00:00 Dec 15, 2019 12:32:25 PM - Info bpbrm (pid=3368) starting bpbkar32 on client Dec 15, 2019 12:32:57 PM - Info bpbkar32 (pid=6820) Backup started Dec 15, 2019 12:32:57 PM - Info bpbkar32 (pid=6820) change time comparison:<disabled> Dec 15, 2019 12:32:57 PM - Info bpbkar32 (pid=6820) archive bit processing:<enabled> Dec 15, 2019 12:32:57 PM - Info bptm (pid=3108) start Dec 15, 2019 12:32:58 PM - Info bptm (pid=3108) using 262144 data buffer size Dec 15, 2019 12:32:58 PM - Info bptm (pid=3108) setting receive network buffer to 1049600 bytes Dec 15, 2019 12:32:58 PM - Info bptm (pid=3108) using 30 data buffers Dec 15, 2019 12:33:00 PM - begin writing Dec 15, 2019 12:33:01 PM - Info bptm (pid=3108) start backup Dec 15, 2019 12:33:02 PM - Info bptm (pid=3108) backup child process is pid 8364.8424 Dec 15, 2019 12:33:02 PM - Info bptm (pid=8364) start Dec 15, 2019 12:36:14 PM - Info bpbkar32 (pid=6820) not using change journal data for <C:\>: not enabled Dec 15, 2019 10:10:19 PM - Warning bpbrm (pid=3368) from client 07r-malvern02: WRN - can't open file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Bin\service.dat (WIN32 32: The process cannot access the file because it is being used by another process. ) Dec 15, 2019 10:19:05 PM - Warning bpbrm (pid=3368) from client 07r-malvern02: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Data\BASH\ShdSettg.dat (WIN32 32: The process cannot access the file because it is being used by another process. ) Dec 15, 2019 10:19:06 PM - Warning bpbrm (pid=3368) from client 07r-malvern02: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Data\BASH\ShdSettg.dat.log (WIN32 32: The process cannot access the file because it is being used by another process. ) Dec 15, 2019 10:19:08 PM - Warning bpbrm (pid=3368) from client 07r-malvern02: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Data\BASH\SPSettg.dat (WIN32 32: The process cannot access the file because it is being used by another process. ) Dec 15, 2019 10:19:10 PM - Warning bpbrm (pid=3368) from client 07r-malvern02: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Data\BASH\SPSettg.dat.log (WIN32 32: The process cannot access the file because it is being used by another process. ) Dec 15, 2019 10:22:05 PM - Warning bpbrm (pid=3368) from client 07r-malvern02: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Data\CmnClnt\ccGEvt\Global\LM2.dat (WIN32 32: The process cannot access the file because it is being used by another process. ) Dec 15, 2019 10:22:07 PM - Warning bpbrm (pid=3368) from client 07r-malvern02: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Data\CmnClnt\ccGLog\ccGenericLog.dat (WIN32 32: The process cannot access the file because it is being used by another process. ) Dec 15, 2019 10:22:09 PM - Warning bpbrm (pid=3368) from client 07r-malvern02: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Data\CmnClnt\ccJobMgr\JobMgr.dat (WIN32 32: The process cannot access the file because it is being used by another process. ) Dec 15, 2019 10:22:10 PM - Warning bpbrm (pid=3368) from client 07r-malvern02: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Data\CmnClnt\ccJobMgr\JobMgr.dat.log (WIN32 32: The process cannot access the file because it is being used by another process. ) Dec 15, 2019 10:22:12 PM - Warning bpbrm (pid=3368) from client 07r-malvern02: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.5337.5000.105\Data\CmnClnt\ccSetMgr\44bb4a26-6c2a-48a8-a256-8ae3ee56f112.dat (WIN32 32: The process cannot access the file because it is being used by another process. ) Dec 15, 2019 10:22:12 PM - Info bpbrm (pid=3368) from client 07r-malvern02: TRV - last message being suppressed after 10 occurrences Dec 16, 2019 10:59:26 AM - Critical bptm (pid=3108) image write failed: error 2060046: plugin error Dec 16, 2019 10:59:26 AM - Critical bptm (pid=3108) sts_get_image_prop failed: error 2060046: plugin error Dec 16, 2019 10:59:32 AM - Error bptm (pid=3108) cannot write image to disk, Invalid argument Dec 16, 2019 10:59:33 AM - Info bptm (pid=3108) EXITING with status 84 <---------- Dec 16, 2019 11:00:03 AM - end writing; write time: 22:27:03 Dec 16, 2019 11:00:05 AM - Info bpbkar32 (pid=6820) done. status: 84: media write error media write error (84)
Prabhu_Bruce
6 years ago Place NetBackup
966Views
0likes
1Comment
can't connect to client
hello all i have the status 58 in our netbackup (job failed) and look this command when i was maked and how you can advice me to troubleshooting the issue >bptestbpcd.exe -client MPX-VM-NAVINT01 -verbose -debug 14:59:18.771 [12420.13224] <2> bptestbpcd: VERBOSE = 0 14:59:19.802 [12420.13224] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d 14:59:21.443 [12420.13224] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd 14:59:21.474 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x0 14:59:21.474 [12420.13224] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2030] VN_REQUEST_SERVICE_SOCKET 6 0x6 14:59:21.474 [12420.13224] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2044] service bpcd 14:59:21.599 [12420.13224] <2> logconnections: BPCD CONNECT FROM 10.0.100.20.62200 TO 10.0.112.250.13724 fd = 640 14:59:22.630 [12420.13224] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d 14:59:24.521 [12420.13224] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd 14:59:24.552 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x0 14:59:24.552 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2072] connect VNETD CONNECT FROM 10.0.100.20.62203 TO 10.0.112.250.13724 fd = 660 14:59:24.552 [12420.13224] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:455] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa 14:59:24.552 [12420.13224] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:480] ipc_string 23279 14:59:24.599 [12420.13224] <2> ConnectToBPCD: bpcd_connect_and_verify(MPX-VM-NAVINT01, MPX-VM-NAVINT01) failed: 46 14:59:25.630 [12420.13224] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d 14:59:27.568 [12420.13224] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd 14:59:27.630 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x0 14:59:27.630 [12420.13224] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2030] VN_REQUEST_SERVICE_SOCKET 6 0x6 14:59:27.630 [12420.13224] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2044] service bpcd 14:59:27.662 [12420.13224] <2> logconnections: BPCD CONNECT FROM 10.0.100.20.62207 TO 10.0.112.250.13724 fd = 640 14:59:28.693 [12420.13224] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d 14:59:30.615 [12420.13224] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd 14:59:30.646 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x0 14:59:30.646 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2072] connect VNETD CONNECT FROM 10.0.100.20.62211 TO 10.0.112.250.13724 fd = 660 14:59:30.646 [12420.13224] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:455] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa 14:59:30.646 [12420.13224] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:480] ipc_string 23291 14:59:30.693 [12420.13224] <2> local_bpcr_connect: got an exit status error message: <?xml version="1.0" encoding="utf-8"?><StatusMsgDoc><StatusMsg NBUStatus="46" Severity="2" VXULoid="137" VXULtid="114"><P pos="0">mpx-py-bkup02.snmvt.intra</P><P pos="1">10.0.100.20</P><P pos="2">MPX-VM-NAVINT01.snmvt.intra</P><P pos="3">10.0.112.250</P><MsgString>Request from host mpx-py-bkup02.snmvt.intra (10.0.100.20) to host MPX-VM-NAVINT01.snmvt.intra (10.0.112.250) is not allowed access.</MsgString><StatusMsg NBUStatus="46" Severity="0" VXULoid="137" VXULtid="115"><P pos="0">mpx-py-bkup02.snmvt.intra</P><P pos="1">10.0.100.20</P><P pos="2">mpx-vm-navint01.snmvt.intra</P><MsgString>Host mpx-py-bkup02.snmvt.intra (10.0.100.20) is not an authorized server for host mpx-vm-navint01.snmvt.intra.</MsgString></StatusMsg></StatusMsg></StatusMsgDoc> 14:59:30.693 [12420.13224] <2> ConnectToBPCD: bpcd_connect_and_verify(MPX-VM-NAVINT01, MPX-VM-NAVINT01) failed: 46 <16>bptestbpcd main: Function ConnectToBPCD(MPX-VM-NAVINT01) failed: 46 14:59:30.709 [12420.13224] <16> bptestbpcd main: Function ConnectToBPCD(MPX-VM-NAVINT01) failed: 46 <16>bptestbpcd main: Request from host mpx-py-bkup02.snmvt.intra (10.0.100.20) to host MPX-VM-NAVINT01.snmvt.intra (10.0.112.250) is not allowed access. Host mpx-py-bkup02.snmvt.intra (10.0.100.20) is not an authorized server for host mpx-vm-navint01.snmvt.intra. 14:59:30.740 [12420.13224] <16> bptestbpcd main: Request from host mpx-py-bkup02.snmvt.intra (10.0.100.20) to host MPX-VM-NAVINT01.snmvt.intra (10.0.112.250) is not allowed access. Host mpx-py-bkup02.snmvt.intra (10.0.100.20) is not an authorized server for host mpx-vm-navint01.snmvt.intra. <2>bptestbpcd: server not allowed access 14:59:30.771 [12420.13224] <2> bptestbpcd: server not allowed access <2>bptestbpcd: EXIT status = 46 14:59:30.771 [12420.13224] <2> bptestbpcd: EXIT status = 46 server not allowed access I was searched more in the Veritas web can't fix this issue,please help
Solved
netbackup22
6 years ago Place NetBackup
4.5KViews
0likes
12Comments
client process aborted (50)
good morning please i need your help client process aborted (50) how can i troubleshooting what is the cause of this issue it can be not enough time or time out?? thank you so much
Solved
netbackup22
6 years ago Place NetBackup
1.6KViews
0likes
2Comments
client process aborted (50)
Dear all 13 sept. 2019 19:23:35 - Info nbjm (pid=5140) starting backup job (jobid=121197) for client 10.0.100.212, policy Full_Backup, schedule Full 13 sept. 2019 19:23:35 - Info nbjm (pid=5140) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=121197, request id:{CAECE6C4-EE6C-4ABE-B894-25C8C9FEE25B}) 13 sept. 2019 19:23:35 - requesting resource sauv01py112-hcart-robot-tld-0 13 sept. 2019 19:23:35 - requesting resource sauv01py112.snmvt.intra.NBU_CLIENT.MAXJOBS.10.0.100.212 13 sept. 2019 19:23:35 - requesting resource sauv01py112.snmvt.intra.NBU_POLICY.MAXJOBS.Full_Backup 13 sept. 2019 19:23:35 - awaiting resource sauv01py112-hcart-robot-tld-0. No drives are available. client process aborted (50) please i need your answer about this troubleshooting is right or not ? * - This issue it can be caused by not enough time ( need to increase it ) * - I have one drive in our robot use for different VMs ,this later can causes the slow process of saving and to out of the board time. this result of client process aborted (need other drive to avoid of out of time range
netbackup22
6 years ago Place NetBackup
1.3KViews
0likes
2Comments