Welcome to your hub for enterprise data protection discussions. Learn more about recent changes to the VOX Community here.
Forum Widgets
Recent Discussions
(69) invalid filelist specification
Buenos días. Me sale el siguiente error cuando se ejecuta una política tipo VMware Apr 22, 2025 6:00:26 PM - begin Application Resolver:Policy Execution Manager Preprocessed Apr 22, 2025 6:00:27 PM - Error nbpem (pid=140959) Two or more backup components with the name masteropenshift were found with conflicting information Apr 22, 2025 6:00:27 PM - Error nbpem (pid=140959) backup of client masterbk02 exited with status 69 (invalid filelist specification) Apr 22, 2025 6:00:27 PM - Error nbpem (pid=140959) Two or more backup components with the name masteropenshift were found with conflicting information Operation Status: 69 Apr 22, 2025 6:00:27 PM - end Application Resolver:Policy Execution Manager Preprocessed; elapsed time 0:00:01 Apr 22, 2025 6:00:27 PM - begin Application Resolver:Stop On Error Operation Status: 0 Apr 22, 2025 6:00:27 PM - end Application Resolver:Stop On Error; elapsed time 0:00:00 Operation Status: 69 Apr 22, 2025 6:00:27 PM - end Parent Job; elapsed time 0:00:04 invalid filelist specification (69) Que validaciones puedo realizar puesto que reviso en Vcenter y no encuentro alguna anomalidad. Muchas gracias, quedo atenta
Local account vs Service account for DNAS protection
Hi, I was interested to hear from the community as to if people tend to use local accounts or service accounts when it comes to configuring snapshot style protection for DNAS backups? Previously when we used ndmp we obviously had to use local accounts that were local to the storage array but we want to test moving away from NDMP to DNAS and as such it seems you can give it either local or domain based user so long as it has sufficient rights on the storage array. So what do people tend to use and for what reasons? Thanks in advance for any opinions/info
DR server for production master server.
We have netbackup 10.1 physical master server and we want to create a DR server for it. Can some one suggest how to create a DR physical server for our master server and it is also acting as media server too. can we restore the catalog using different server name or we need to keep the DR server name also same as production server. if same name should we bring down the prod and then do restore to bring up the DR and then shutdown DR. and use only for DR purpose and currently no backups are running in it and it is kept only for old legacy restores.
Duplication of data to new STU
Hey guys, I have a question how to duplicate all backup images from one MSDP to another. We have one appliance where backups are goin via SLPs and now we want to add new appliance to our environment for duplication purposes. How can we easly duplicate all data? If we add duplication to SLP it will only duplicate new images right? We need to copy also old images as this is requirement from business. Br, Piotr
Netbackup schedule is not running for some of the servers
We have some servers that the backup won't run on the scheduled time according to the policy, but they can be run manually. I already tried the fix in below but it seems it doesn't work: https://www.veritas.com/support/en_US/article.100018741 Not sure is it related, for all these servers there is a failed job in the activity monitor which has a future start date. (see attached picture) Anyway, is there anyway I can reset all these schedules to fix it?
Restore Failure - 2850
Previously, I could queue a restore, have NBU suggest a tape, recall the tape from offsite, and complete the restore days later. Now, if the tape and a drive is not immediately available, the following occurs: Mar 31, 2025 10:15:22 AM - begin Restore Mar 31, 2025 10:15:22 AM - number of images required: 1 Mar 31, 2025 10:15:22 AM - media needed: 6081L9 Mar 31, 2025 10:15:22 AM - Info bprd (pid=937) Restoring from copy 2 of image created Sat Nov 2 00:02:09 2024 from policy PolicyA Mar 31, 2025 10:15:23 AM - restoring from image ServerA_1730530929 Mar 31, 2025 10:15:23 AM - Info bpbrm (pid=1030) ServerA is the host to restore to Mar 31, 2025 10:15:23 AM - Info bpbrm (pid=1030) telling media manager to start restore on client Mar 31, 2025 10:15:23 AM - Info bpbrm (pid=1030) spawning a brm child process Mar 31, 2025 10:15:23 AM - Info bpbrm (pid=1030) child pid: 1044 Mar 31, 2025 10:15:23 AM - connecting Mar 31, 2025 10:15:23 AM - requesting resource 6081L9 Mar 31, 2025 10:15:23 AM - awaiting resource 6081L9. A pending request has been generated for this resource request. Operator action may be required. Pending Action: No action, Media ID: 6081L9, Barcode: EC6081L9, Density: hcart3, Access Mode: Read, Action Drive Name: N/A, Action Media Server: nb5250master, Robot Type(Number): 0(N/A), Volume Group: ---, Action Acs: N/A, Action Lsm: N/A Mar 31, 2025 10:15:24 AM - Info bpbrm (pid=1044) start tar on client Mar 31, 2025 10:15:24 AM - Info tar (pid=1856850) Restore started. Mar 31, 2025 10:15:24 AM - connected; connect time: 0:00:00 Mar 31, 2025 10:16:23 AM - awaiting resource 6081L9. A pending request has been generated for this resource request. Operator action may be required. Pending Action: No action, Media ID: 6081L9, Barcode: EC6081L9, Density: hcart3, Access Mode: Read, Action Drive Name: N/A, Action Media Server: nb5250master, Robot Type(Number): 0(N/A), Volume Group: ---, Action Acs: N/A, Action Lsm: N/A Mar 31, 2025 10:25:23 AM - Info bpbrm (pid=1030) Sending SIGHUP to media manager 1033 Mar 31, 2025 10:25:23 AM - Info bpbrm (pid=1030) terminating bpbrm child 1044 jobid=15017390 Mar 31, 2025 10:25:27 AM - Error bptm (pid=1033) media manager terminated by parent process Mar 31, 2025 10:25:27 AM - Error bptm (pid=1040) The following files/folders were not restored: Mar 31, 2025 10:25:27 AM - Error bptm (pid=1040) UTF - /path/to/restore/local.login Mar 31, 2025 10:25:27 AM - restored from image ServerA_1730530929; restore time: 0:10:04 Mar 31, 2025 10:25:27 AM - Warning bprd (pid=937) Restore must be resumed prior to first image expiration on Mon 02 Nov 2026 12:02:09 AM MST Mar 31, 2025 10:25:27 AM - end Restore; elapsed time 0:10:05 Restore error (2850) 10 minutes after queuing the restore, if fails. This is very consistent behavior. If the required media is available in the tape library and NBU is aware of it (inventoried robot) and a drive is free, the restore will complete. Running NBU 9.1.01 on a Veritas 5250 Appliance, connected to a SpectraLogic Stack LTO9. The tape library is newish, and we had some issues getting it working properly with NBU. These restore failures may be a side-effect of trouble-shooting with Veritas Support.
