ERR - Unable to NFS mount the required file system.
Hi, We are trying to do an exchange GRT backup. Exchange 2019, Windows Server 2019 and a Media Server running RHEL with Netbackup 8.2 Clients. In doing so our backups are only partially successful with the following error: 02/11/20202:49:49PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-UnabletoNFSmounttherequiredfilesystem. 02/11/20202:50:59PM-Infobpbrm(pid=3513266)DB_BACKUP_STATUSis0 02/11/20202:51:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-ErrorencounteredwhileattemptingtogetadditionalfilesforMicrosoftInformationStore:\MYDB001\Logs_1604288407\ 02/11/20202:51:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-Exchangegranularrestorefromthisimagemaynotwork. 02/11/20202:53:09PM-Infobpbrm(pid=3513266)DB_BACKUP_STATUSis0 02/11/20202:53:47PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-ErrorencounteredwhileattemptingtogetadditionalfilesforMicrosoftInformationStore:\MYDB002\Logs_1604288407\ 02/11/20202:53:47PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-Exchangegranularrestorefromthisimagemaynotwork. 02/11/20203:00:57PM-Infobpbrm(pid=3513266)DB_BACKUP_STATUSis0 02/11/20203:01:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-ErrorencounteredwhileattemptingtogetadditionalfilesforMicrosoftInformationStore:\MYDB003\Logs_1604288407\ 02/11/20203:01:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-Exchangegranularrestorefromthisimagemaynotwork. 02/11/20203:04:27PM-Infobpbrm(pid=3513266)DB_BACKUP_STATUSis0 02/11/20203:05:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-ErrorencounteredwhileattemptingtogetadditionalfilesforMicrosoftInformationStore:\MYDB004\Logs_1604288407\ 02/11/20203:05:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-Exchangegranularrestorefromthisimagemaynotwork. 02/11/20203:06:08PM-Infobpbrm(pid=3513266)DB_BACKUP_STATUSis0 02/11/20203:06:47PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-ErrorencounteredwhileattemptingtogetadditionalfilesforMicrosoftInformationStore:\MYDB005\Logs_1604288407\ 02/11/20203:06:47PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-Exchangegranularrestorefromthisimagemaynotwork. 02/11/20203:07:18PM-Infobpbrm(pid=3513266)DB_BACKUP_STATUSis0 02/11/20203:07:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-ErrorencounteredwhileattemptingtogetadditionalfilesforMicrosoftInformationStore:\MYDB006\Logs_1604288407\ 02/11/20203:07:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-Exchangegranularrestorefromthisimagemaynotwork. 02/11/20203:08:16PM-Infobpbrm(pid=3513266)DB_BACKUP_STATUSis0 02/11/20203:08:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-ErrorencounteredwhileattemptingtogetadditionalfilesforMicrosoftInformationStore:\MYDB007\Logs_1604288407\ 02/11/20203:08:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-Exchangegranularrestorefromthisimagemaynotwork. 02/11/20203:09:16PM-Infobpbrm(pid=3513266)DB_BACKUP_STATUSis0 02/11/20203:09:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-ErrorencounteredwhileattemptingtogetadditionalfilesforMicrosoftInformationStore:\MYDB008\Logs_1604288407\ 02/11/20203:09:46PM-Errorbpbrm(pid=3513266)fromclient<mydag>:ERR-Exchangegranularrestorefromthisimagemaynotwork. 02/11/20203:09:47PM-Infobptm(pid=3513457)waitedforfullbuffer10933times,delayed32049times 02/11/20203:09:48PM-Infobptm(pid=3513457)EXITINGwithstatus0<---------- 02/11/20203:09:48PM-Infobpbrm(pid=3513266)validatingimageforclient<mydag> 02/11/20203:09:48PM-Infobpbkar(pid=36536)done.status:1:therequestedoperationwaspartiallysuccessful 02/11/20203:09:48PM-endwriting;writetime:0:21:01 Therequestedoperationwaspartiallysuccessful (1) I have followed the instructions in this document:https://www.veritas.com/content/support/en_US/article.100000686 and when doing so receive the following error: C:\Program Files\Veritas\NetBackup\bin>nbfs mount -server mymediaserver-cred <cred> * connect to mymediaserver failed EXIT_STATUS=25 Any ideas?Solved6KViews0likes11CommentsNetBackup 8.3 - Exchange Policy Bugs
Hi All, Just upgraded my NetBackup environment from 8.2 to 8.3 and I noticed the following bugs with Exchange policies. 1. When I try to create a new policy I simply can't finish the procedure because of the following error: Please select a valid snapshot method using 'Snapshot Client Options'. Now when I hit the corresponding "Options" button on the policy screen, nothing happens and I'm not able to see the usual screen where the VSS method is chosen by default with it's corresponding parameters. Everytime I hit the "Options" button literally nothing happens and the only way to save the policy is by unticking the "Perform snapshot backups" checkbox which at least will let you hit the "OK" button at the bottom. When I reopen the same policy, the "Perform snapshot backups" checkbox is once again ticked but still there is no way to modify anything within the "Options" section. 2. When I run the newly created policy, I receive the following error message: ThistypeofbackupisnotsupportedonthisversionofExchange theclienttypeisincorrectintheconfigurationdatabase (72) By my best knowledge both Windows Server 2019 and Exchange 2019 CU6 are fully supported and my policy is set just as per the expected rules according to the NBU documentation. So all in all right now it is impossible to backup Exchange with the new NBU 8.3 version. Any suggestions you may have are highly welcome. For the record I don't have active support contract with Veritas therefore I can't open a support ticket with the vendor.5.3KViews0likes18CommentsWhat are the .NBU files
Hello Team, A search of the NBU Windows client's file system after completing restores show some Windows clients have a large number of .NBU files where the date and size match the completed restores. Attached is a sample from just one Windows client, there are 270 files, some from 2015 through today totaling 120 GB: Q: What are these .NBU files and why are they created ? Q: Although the .NBU files are not backed up or restored, why doesn't NBU clean up these files after restore complete ? Thanks ! NBU 8.3.0.1 - 1 Linux Master / 2 Linux Media servers Restoring to NBU Windows 2019 backup clientsSolved3.2KViews0likes10CommentsEMM_DATA.db - huge size can't be reduced
Dear All, I recently got stuck with an issue where the size of my EMM_DATA.db has grown enormously and I can't find a way to reduce it at all. As a short description of my environment (LAB), I have 2 NBU master servers participating in AIR scenario where the first one (which is the source for AIR) has 3 separate MSDP based media servers connected to it. The second master server also has MSDP pool plus a tape library for offloading purposes. I'm replicating all backed up images between my two NBU master domains regularly as backup images gets produced by the clients. The EMM_DATA.db file on the source master server somehow managed to grow to the enourmous size of 8.9GB while on the target master server it is not larger than 30MB. Although the infrastructure works well enough and I have no major failure out of this DB size except maybe for the increased size of the catalog backups, I wanted to optimize the DB to a somewhat normal size. After trying to validate, reorganize and rebuild the DB section as per the tech. articles via the regular "nbdb_admin" and "nbdb_unload" commands nothing really has changed to the DB size therefore I started digging a bit further. I noticed one particular discrepancy through the NBDBAdmin utility which shown me visually that the EMM_DATA portion is indicating "-1 bytes" for both "Free DBspace" and "Total DBspace" metrics. Also the size of the DB is indicated to be as 4096MB while in reality it's twice as big which makes me think that there is some kind of a corruption throughout NBDB or perhaps just the EMM_DATA portion although all the validation activities I did via CLI indicated that there are no errors at all. Reorganizing the DB via CLI indicated very few fragments and it also didn't indicate any errors. The rebuild command didn't give me any output but just returned to command prompt, however I noticed slight modification to the NBDB log files (got truncated almost immediately) so I assume that it didn't fail but it was doing it's job. On the second master server everything works absolutely fine and the sizes are definitely in order. Even though there is no relationship with this I would like to mention that all backup images in the catalogs for both master servers are exactly the same including the granularity factor for some of the backups where I use this feature (in my case Active Directory). Strangely enough when I tried to do the run the "Reorganize All" command through the GUI utility it returned back "Operation Failed" status message. The result was the same also for the "Rebuild" command. On the contrary "Validation" went through and didn't indicate any issues. My environment is based on Windows Server 2019 + NetBackup v8.2 for all NBU servers. One of my very old catalog backups that I could dig out (from exactly two years ago) clearly indicates that the EMM_DATA.db file at the time being was a little less than 30MB. If I remember right my servers were running NBU v8.1 binaries at the time being which I have upgraded to v8.1.1, v8.1.2 up till the current v8.2 through the years. I suppose this could be some sort of a bug with any of the intermediate or latest binaries, but right now I'm clueless on how this issue can be solved. I would appreciate any thoughts from experts around and I hope to find a solution to this pesky little problem. Cheers2.5KViews0likes9CommentsWindows server 2019 VM guest support
Hi I have just updated to 8.1.2 and have tested running backups on Windows server 2019. Agent based backup worked fine but when I run a VM backup it failed. Netbackup report: anerroroccurredwhilequiescingthevirtualmachine. If I look in eventviewer on the server, there is VSS errors: An expected hidden volume arrival did not complete because this LUN was not detected. There is no problem running a snapshot from vcenter. It is incredible that Netbackup does not support Windows server 2019 yet. First preview release was march 2018, a year ago. AndGA released in october 2018. When willWindows server 2019 be supported in NetBackup? NBU 8.1.2 on Windows 2012 Vcenter 6.7 U12KViews0likes1CommentLTO9 tape performance poor - bottlenecks?
Hi all We've recently completed a staged total replacement of our environment from NBU8.2, writing first to HPE MSA2040 storage and then out to LTO5 drives; to NBU9.1 writing to HPE MSA2060 storage and out to LTO9 drives Write performance on the 2040/LTO5 setup was approximate 50GB/hr/drive * 4 drives (* 2 setups, but each library was writing data from a single MSA); and this jumped to approximately 200GB/hr/drive when we moved to a 2060/LTO5 setup. This improvement was badly needed as I had reduced our tapeouts to a bare minimum to ensure they actually got written out. Turning everything that should be written out back on got us close to exhausting the write-out capacity of the setup again. Now we have LTO9 drives, I am seeing approx 250GB/hr/drive * 3 drives on each site, which is less than we were getting with the four LTO5 drives. Some writes peak to 300GB/hr, but this isn't common. This is causing backlog issues again. This is a fraction of the rated read speeds for the MSA2060, the write speeds on the LTO9 libraries and the fibrechannel throughput with nothing showing saturation at any point. Back when we had the MSA2040s I would frequently see waits recorded in the duplication job logs but this isn't the case anymore Is there something obvious I am missing such as a rate limit set somewhere? Or is there a cap on encryption speed? We use the drive native encryption handed via an ENCR_ media pool and I can confirm that the LTO9 drives are encrypting.1.9KViews0likes8CommentsCatalog Backup fails after OS upgrade
Hello, Veritas Netbackup : V.8.2 Policy Type : NBU-Catalog OS Master and Media Server : W2019 Std Storage : Media Server (Policy storage) and local (Disaster Recovery) This server (Master Netbackup) has been updated to W2019 (previously 2012R2) and since "Catalog Backup" not work anymore. All other backup (VM, physical server) working fine. File are written in local folder (Disaster Recovery : Path) but deleted when job fail. Communication (Netbackup Management -> Host Properties -> Media Servers) with Media Server are ok. Local folder (on master server), who contains all previously catalogue backup, are available with full control for local administrators group and SYSTEM A new policy (for backup catalog) have been created, but same errors. Job : Parent (48254) : File list : "CATALOG_DRIVEN_BACKUP" Status : "1: (2) none of the requested files were backed up" Child 1 (48255) : File list : "CATALOG_DRIVEN_BACKUP" Status : "1: (2) none of the requested files were backed up " Child 2 (48256) : File list : "E:\Program Files\Veritas\NetBackupDB\staging\BMRDB.db" Status : "1: (24) socket write failed " Do you have, please, any idea to solve this problem? Thanks.1.8KViews0likes6CommentsOpenshift backup using Netbackup and the Netapp trident plugin
Hello I am useing Netbackup 10.0.0.1 at the moment. I have configured the kubernetes backup (using the webui) to backup our Openshift cluster. Everything is working fine except the backup of the PVCs. In the backend of openshift we use the Netapp trident plugin. I get the following error in OC:"Failed to find suitable volumesnapshotclass for pvc". I followed thequick start guide. OpenShift version 4.8.36 Netbackup Primary Server: Windows Server 2019 NBU: 10.0.0.1 Netbackup Media Server: RedHat 7.9 NBU: 10.0.0.1 Has anyone configured OC backup using the trident plugin and Netbackup? thanksSolved1.7KViews0likes3Comments