![]() The new NetApp v2 sensors NetApp Aggregate v2, NetApp I/O v2, NetApp LIF v2, NetApp LUN v2, NetApp NIC v2, NetApp Physical Disk v2, NetApp SnapMirror v2 Sensor, NetApp System Health v2 and NetApp Volume v2 support the new ONTAP REST API as of ONTAP 9.6. ![]() We fixed an issue for the Veeam Backup Job Status and Veeam Backup Job Status Advanced sensor where the login on the Veeam Enterprise Manager failed with the message Enterprise Manager Login failed: 401: Unauthorized Veeam Backup Job Status and Veeam Backup Job Status Advanced sensor In previous PRTG versions, the sensor reported an error when a private key with a length other then 2048 bits was used. The OPC UA Server Status sensor now supports Client Keys with a 4096 bit length for OPC Client Certificates. With this fix the sensor returns the average values. We fixed an issue for the Microsoft Azure Storage Account sensor's channel, Used Capacity, which was previously recording 0 values. The sensor displayed the error message regex_error(error_brace): The expression contained mismatched. Sounds almost like another media server would be needed? I'm just not sure.We fixed an issue for the DNS v2 sensor where the character escaping for curly brackets } in the Filter Value did not work properly. I have created a new local account on the media server, logged in with that, and mapped a drive to the data on the Barracuda appliance, but where I get confused is changing accounts used to run the netbackup service, which concerns me, due to possibly killing existing backups. Yes, I've been researching this on my own, I have attached a link below to another similar discussion to this, but I dont fully understand all of the steps involved. Lastly, assuming what I'm dealing with here are some access issues that can get resolved, given this large amount of data that I need to back up, what method would you all prefer to use to back up this data if it were you doing this? Im sure I'm not seeing all options. I have typed in the full path as well, but the job fails. setting the policy to just point to an existing storage unit, and again, trying to back up the mapped drive from the media server.Įither way, where I get stopped is not being able to locate the share in Netbackup, which is why I'm thinking it's all just relating to permissions. ![]() Added this to the policy and tried pointing the backup seletion to it. creating a CIFs share on our DataDomain, and building out a new Storage Unit with an absolute path pointing to \\DataDomain\CIFS_Share. ![]() I'm not sure there is anything special here about it being a Barracuda appliance, or if this should just be approached the same way as backing up any other non-domain data. Of course, when I set up a policy, and go into the backup selection tab, the drive isnt visible or available to select. The issue I'm having is that Netbackup cannot see/access the share, probably because the Barracuda is not on the is in its own workgroup, and mapped to the media server using its local SMB credential. I am able to map a drive to the data from the media server, and see everything in it. ![]() I already have a Symantec case opened, and have been working for 2 days with a Technical Support Engineer, but am so far not moving forward. He's very fixated on the fact that when I test this, it fails with a status 71, which I fully expected and know why. I've been asked to start backing up our Barracuda email archivers. Netbackup 7504 Windows 2008r2 Master and media servers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |