Manually copying .bkf files
We are backing up our files every night with Backupexec to a dedicated backup hard drive in the same server. We feel pretty good about being protected from a hard drive failure. However we are not protected from a fire that destroys the whole server. I would like to copy the .bkf files to an offsite storage medium. Is this gonna work? Doing some research, I saw suggestions that this is not going to work, that Backup Exec needs to write the .bkf files to the backup medium directly or it will throw an error when you try to restore a 2nd generation copy of a .bkf. This seems a little strange to me.... let's say if you have a complete disk failure of the C: drive and the whole server OS (including Backup Exec installation) is gone, and you have to do a bare metal restore. So it looks like you can't just diieinstall a fresh OS and then a fresh copy of Backup Exec and then do a restore of the .bkf files because the fresh Backup Exec software won't know what to do with my existing .bkf files? P.S. we do not use encryption because our files are only valuable to us... no one else would find it useful or valuable274Views0likes1CommentTape consume extra space then actual upload size
We were taking Tape backup (LTO) from Windows server folder. After backup was completed, when we compared the size on the Tape was different from the actual size on the windows folder. We could not able to find where the extra space consumed on the tape. Windows Folder size: 58 GB After Tape Back, size on tape is: 90 GB We could not able to identify this extra 32 GB How and where on tape drive we can identify extra utilized space/files/waste ? and how we can remove it ? Thanks&Regards Sachin419Views0likes3CommentsNetbackup error code 1. Any issue in restoring any files due to the errors?
At times, getting error code 1 for some backup and a rerun manually is successful. On some other days, it was able to completed successfully. No errors were seen. Any way to turn on more details logging to assist with troubleshooting?856Views0likes6CommentsMSL2024 Robotic Partition reconfiguration
Hi, I have a Query at a company running Backup Exec version 21.4 using an HP LTO tape library with two drives and 24 tape slots. The previous IT guy is gone but left the partition with 14 partitions. The first 1 -11 is a single partition and the rest of each has one slot, I need to change this configuration but I'm wondering what effect the changes would have on existing data that use the current partitions. will they update automatically? I don't want to make changes with existing 12 to 24 individual partitions if reconfiguring the partitions and changing from 14 to 24 individual could cause problems or data loss. 1-11 don't have drives388Views0likes1Commentthe backup failed to back up the requested files(6)
Hi, Our enviroment we have master server version 8.1.1 in Windows Server 2012 R2 . Last week we are getting a error code 6 form NBU for one snapshot/backup operation with the following error: Nov 25, 2023 12:58:26 PM - Info nbjm (pid=6644) starting backup job (jobid=32857) for client vcs, policy vcs, schedule vcs_full Nov 25, 2023 12:58:26 PM - Info nbjm (pid=6644) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=32857, request id:{12AA4538-D7B1-4091-A24C-7CCEBB5B9ABC}) Nov 25, 2023 12:58:26 PM - requesting resource cifs1-stu Nov 25, 2023 12:58:26 PM - requesting resource srv-nbu01i.msa.com.NBU_CLIENT.MAXJOBS.vcs Nov 25, 2023 12:58:26 PM - requesting resource srv-nbu01i.msa.com.NBU_POLICY.MAXJOBS.vcs Nov 25, 2023 12:58:26 PM - granted resource srv-nbu01i.msa.com.NBU_CLIENT.MAXJOBS.vcs Nov 25, 2023 12:58:26 PM - granted resource srv-nbu01i.msa.com.NBU_POLICY.MAXJOBS.vcs Nov 25, 2023 12:58:26 PM - granted resource MediaID=@aaaah;DiskVolume=\\192.168.140.169\cifs1;DiskPool=cifs1;Path=\\192.168.140.169\cifs1;StorageServer=srv-nbu01i.msa.com;MediaServer=srv-nbu01i.msa.com Nov 25, 2023 12:58:26 PM - granted resource cifs1-stu Nov 25, 2023 12:58:26 PM - estimated 0 kbytes needed Nov 25, 2023 12:58:26 PM - begin Parent Job Nov 25, 2023 12:58:26 PM - begin VMware: Start Notify Script Nov 25, 2023 12:58:27 PM - Info RUNCMD (pid=32432) started Nov 25, 2023 12:58:27 PM - Info RUNCMD (pid=32432) exiting with status: 0 Operation Status: 0 Nov 25, 2023 12:58:27 PM - end VMware: Start Notify Script; elapsed time 0:00:01 Nov 25, 2023 12:58:27 PM - begin VMware: Step By Condition Operation Status: 0 Nov 25, 2023 12:58:27 PM - end VMware: Step By Condition; elapsed time 0:00:00 Nov 25, 2023 12:58:27 PM - begin VMware: Read File List Operation Status: 0 Nov 25, 2023 12:58:27 PM - end VMware: Read File List; elapsed time 0:00:00 Nov 25, 2023 12:58:27 PM - begin VMware: Create Snapshot Nov 25, 2023 12:58:27 PM - Info bpbrm (pid=35140) vcs is the host to backup data from Nov 25, 2023 12:58:27 PM - Info bpbrm (pid=35140) reading file list for client Nov 25, 2023 12:58:27 PM - Info bpbrm (pid=35140) start bpfis on client Nov 25, 2023 12:58:27 PM - Info bpbrm (pid=35140) Starting create snapshot processing Nov 25, 2023 12:58:27 PM - started process bpbrm (pid=35140) Nov 25, 2023 12:58:28 PM - Info bpfis (pid=40904) Backup started Nov 25, 2023 12:58:28 PM - snapshot backup of client vcs using method VMware_v2 Nov 25, 2023 12:58:29 PM - Info bpbrm (pid=35140) INF - vmwareLogger: Creating snapshot for vCenter server srv-vcenter02.dmzmsa.com, ESX host esx51.dmzmsa.com, BIOS UUID 4209005c-4ec2-29a8-b85b-64661575584b, Instance UUID 5009b489-ff24-bdce-eca6-95a8003f543a, Display Name vcs, Hostname trueconf.dmzmsa.com Nov 25, 2023 12:58:29 PM - Info bpbrm (pid=35140) INF - vmwareLogger: Connection state of virtual machine: connected. Nov 25, 2023 12:58:51 PM - end VMware: Create Snapshot; elapsed time 0:00:24 Nov 25, 2023 12:58:51 PM - Info bpfis (pid=40904) done. status: 0 Nov 25, 2023 12:58:51 PM - Info bpfis (pid=40904) done. status: 0: the requested operation was successfully completed Nov 25, 2023 12:58:51 PM - end writing Operation Status: 0 Nov 25, 2023 12:58:51 PM - end Parent Job; elapsed time 0:00:25 Nov 25, 2023 12:58:51 PM - Info nbjm (pid=6644) snapshotid=vcs_1700906306 Nov 25, 2023 12:58:51 PM - begin VMware: Policy Execution Manager Preprocessed Operation Status: 6 Nov 25, 2023 1:25:15 PM - end VMware: Policy Execution Manager Preprocessed; elapsed time 0:26:24 Nov 25, 2023 1:25:15 PM - begin VMware: Stop On Error Operation Status: 0 Nov 25, 2023 1:25:15 PM - end VMware: Stop On Error; elapsed time 0:00:00 Nov 25, 2023 1:25:15 PM - begin VMware: Delete Snapshot Nov 25, 2023 1:25:15 PM - started process bpbrm (pid=40192) Nov 25, 2023 1:25:16 PM - Info bpbrm (pid=40192) Starting delete snapshot processing Nov 25, 2023 1:25:16 PM - Info bpfis (pid=40116) Backup started Nov 25, 2023 1:25:24 PM - Info bpfis (pid=40116) done. status: 0 Nov 25, 2023 1:25:24 PM - end VMware: Delete Snapshot; elapsed time 0:00:09 Nov 25, 2023 1:25:24 PM - Info bpfis (pid=40116) done. status: 0: the requested operation was successfully completed Nov 25, 2023 1:25:24 PM - end writing Operation Status: 0 Nov 25, 2023 1:25:24 PM - begin VMware: End Notify Script Nov 25, 2023 1:25:24 PM - Info RUNCMD (pid=40884) started Nov 25, 2023 1:25:24 PM - Info RUNCMD (pid=40884) exiting with status: 0 Operation Status: 0 Nov 25, 2023 1:25:24 PM - end VMware: End Notify Script; elapsed time 0:00:00 Operation Status: 6 the backup failed to back up the requested files (6) Could you please help me to resolve this? and the error occurs for many time. Thank you, Mike Androsov839Views0likes3CommentsBackup exec backup job failure
I directly ran a full backup, but the backup was always queued, and there was no rate. The rate was 0. After trying to restart all backup services, I ran the backup task again but there was still no rate. Moreover, I found that the backup service would automatically stop, causing the backup to hang inexplicably. The backup task cannot be continued. How to solve this situation?544Views0likes3CommentsThe backup failed to back up the requested files
Hi! I'm running netbackup 8.1.1. This message only appears for one vm backup. I can backup another vm on the same datastore without a problem. Mar 19, 2024 12:52:35 AM - Info nbjm (pid=6784) starting backup job (jobid=38578) for client tp-gmp-budgetpl2, policy Infrostructure_OKVS, schedule Inc_dayly Mar 19, 2024 12:52:35 AM - Info nbjm (pid=6784) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=38578, request id:{1D0A6BA5-5AF6-432B-A6BA-16984ED1DA31}) Mar 19, 2024 12:52:35 AM - requesting resource Robots Mar 19, 2024 12:52:35 AM - requesting resource srv-nbu01i.msa.com.NBU_CLIENT.MAXJOBS.tp-gmp-budgetpl2 Mar 19, 2024 12:52:35 AM - requesting resource srv-nbu01i.msa.com.NBU_POLICY.MAXJOBS.Infrostructure_OKVS Mar 19, 2024 12:52:35 AM - granted resource srv-nbu01i.msa.com.NBU_CLIENT.MAXJOBS.tp-gmp-budgetpl2 Mar 19, 2024 12:52:35 AM - granted resource srv-nbu01i.msa.com.NBU_POLICY.MAXJOBS.Infrostructure_OKVS Mar 19, 2024 12:52:35 AM - granted resource T369L5 Mar 19, 2024 12:52:35 AM - granted resource IBM.ULT3580-TD5.000 Mar 19, 2024 12:52:35 AM - granted resource srv-nbu01i-hcart2-robot-tld-0 Mar 19, 2024 12:52:35 AM - estimated 31849843 kbytes needed Mar 19, 2024 12:52:35 AM - Info nbjm (pid=6784) started backup (backupid=tp-gmp-budgetpl2_1710798755) job for client tp-gmp-budgetpl2, policy Infrostructure_OKVS, schedule Inc_dayly on storage unit srv-nbu01i-hcart2-robot-tld-0 using backup host srv-nbu01i.msa.com Mar 19, 2024 12:52:35 AM - started process bpbrm (pid=10660) Mar 19, 2024 12:52:36 AM - connecting Mar 19, 2024 12:52:36 AM - connected; connect time: 0:00:00 Mar 19, 2024 12:52:36 AM - Info bpbrm (pid=10660) tp-gmp-budgetpl2 is the host to backup data from Mar 19, 2024 12:52:36 AM - Info bpbrm (pid=10660) reading file list for client Mar 19, 2024 12:52:36 AM - Info bpbrm (pid=10660) starting bpbkar32 on client Mar 19, 2024 12:52:39 AM - Info bpbkar32 (pid=11024) Backup started Mar 19, 2024 12:52:39 AM - Info bpbkar32 (pid=11024) archive bit processing:<enabled> Mar 19, 2024 12:52:39 AM - mounting T369L5 Mar 19, 2024 12:52:39 AM - Info bptm (pid=7672) start Mar 19, 2024 12:52:39 AM - Info bptm (pid=7672) using 262144 data buffer size Mar 19, 2024 12:52:39 AM - Info bptm (pid=7672) using 256 data buffers Mar 19, 2024 12:52:39 AM - Info bptm (pid=7672) start backup Mar 19, 2024 12:52:39 AM - Info bptm (pid=7672) Waiting for mount of media id T369L5 (copy 1) on server srv-nbu01i.msa.com. Mar 19, 2024 12:52:42 AM - Info bpbkar32 (pid=11024) INF - Backing up vCenter server srv-vcenter02.dmzmsa.com, ESX host esx54.dmzmsa.com, BIOS UUID 4209da86-5982-57a6-0437-3af5ee488116, Instance UUID 50097925-6f1c-fa6e-507d-d31fdd6efa7b, Display Name tp-gmp-budgetpl2, Hostname tp-gmp-budgetpl.dmzmsa.com Mar 19, 2024 12:53:30 AM - Info bptm (pid=7672) media id T369L5 mounted on drive index 0, drivepath {10,0,0,0}, drivename IBM.ULT3580-TD5.000, copy 1 Mar 19, 2024 12:53:30 AM - mounted T369L5; mount time: 0:00:51 Mar 19, 2024 12:53:30 AM - positioning T369L5 to file 77 Mar 19, 2024 12:54:34 AM - positioned T369L5; position time: 0:01:04 Mar 19, 2024 12:54:34 AM - begin writing Mar 19, 2024 1:01:28 AM - Error bpbrm (pid=10660) from client tp-gmp-budgetpl2: ERR - Error opening the snapshot disks using given transport mode: san:hotadd:nbd:nbdssl Status 23 Mar 19, 2024 1:01:29 AM - Info bpbkar32 (pid=11024) bpbkar waited 0 times for empty buffer, delayed 0 times. Mar 19, 2024 1:01:35 AM - Error bpbrm (pid=10660) could not send server status message to client Mar 19, 2024 1:01:37 AM - Critical bpbrm (pid=10660) unexpected termination of client tp-gmp-budgetpl2 Mar 19, 2024 1:01:37 AM - Info bpbkar32 (pid=0) done. status: 6: the backup failed to back up the requested files Mar 19, 2024 1:01:37 AM - end writing; write time: 0:07:03 the backup failed to back up the requested files (6) Two days ago, the backup of this virtual machine was performed without problems. No changes were made to the policy settings.Solved888Views0likes4Comments