NetBackup 10.4+ DNAS Multi-Mount Capability Greatly Improves Snapshot Backup Performance
In Dynamic NAS (DNAS) backup jobs, getting data quickly off an array snapshot to target backup storage has been a performance challenge. Most array controllers have TCP/IP port limits that throttle throughput. Even worse, snapshot mount hosts didn’t have a graceful way to mount snapshots as a group to speed things up. The NetBackup 10.4 snapshot crawler has been optimized to deal with these challenges. The parent backup job controls the snapshot crawler’s snapshot crawl for each child job. It breaks up the snapshot into slices of work serviced by a child job for each slice. Each job then runs through a different mount host mounted to the snapshot. In this way multiple mount hosts in a DNAS mount host group can speed up the backup of a single snapshot. The best part is that child jobs aren’t necessarily limited to running in parallel. After each child job crawls complete and the file/folder worklist is finalized, that child job will run. The child jobs don’t wait for all child jobs to post ready before backup data is read from the snapshot and written to backup storage. Our testing shows this can greatly increase snapshot backup performance. For example, we saw a 50-hour snapshot backup that used one mount host decrease to a 15-hour job using four mount hosts. This decrease in time only increased array controller port utilization 10-20%. A fair trade indeed. Users doing disk array snapshot backups should be sure to check out and implement this feature of NetBackup 10.4+.581Views1like0CommentsAvoid Exception Error "Remote Agent not detected" when using NAS
Server: Backup Exec 2015 Client: NAS Issue: Successful completion with Exceptions "Remote Agent Not Detected" In our environment, we are taking backups successfully from NAS boxes. But after the sucessfull completion of the Backup job, there are errors thrown with Exceptions as "Remote Agent not detected". Knowing that the NAS boxes added as a client of File Server Type, which does not have remote agent, why is it checking for a remote Agent, and how to avoid this Exception. Exceptions from the job: Backup- nas1V-79-57344-3844 - The Backup Exec server was unable to connect to the Remote Agent on machine nas1. The Backup Exec server will use the local agent to try to complete the operation. V-79-57344-65277 - Snapshot Technology: Initialization failure on: "\\nas1\data". Snapshot technology used: No. Remote Agent not detected on nas1.1.4KViews0likes2CommentsBE 20: Can not select NAS by NDMP
Hello everyone. I have a Unity 300 that stores a NAS server. I want to backup using the NDMP feature to a robotic library. The problem is that I can not select the NAS using Backup Exec. I add the NAS server using its IP address, then I can see the name of the file system. However, I can not selec it. That's how it looks: I double click /Design but nothing, I can't select it and as a result, I can't click OK. "Not selections were made" it says. If I use the windows explorer I can access to the NAS. Am I missing something? Thanks in advance.Solved1.1KViews0likes2Commentse0000f16 - The operation failed to acquire the minimum number of drives and media needed
Backup to NAS is failing with error e0000f16 - The operation failed to acquire the minimum number of drives and media needed.Tried to increase the concurrent write operations in the disk storage but it was stuck in updating for a very long time.Restarted the BE services once still the same.Unable to disable the disk storage(NAS) in the BE 20 console. 1. What are the basic checks (user account permissions) that as to be given in the NAS and the BE console. 2.What else has to be checked as already rebooted the BE server and the NAS device. Thanks Melvin1.8KViews0likes4Commentsthecus N8800PRO NAS is identified as windows computer by backupexec 16
Hello, I'm using an evaluation version of BackupExec 16, trying to do a backup of a cifs share located on a thecus N8800PRO NAS. When i added the NAS to the default "All Servers" group, i've selected the option "Fileserver or NDMP-Dataserver". But when the configuration wizard is finished, the "ServerType" property of the newly added server is "Windows-Computer". I've tried to select the option "Linux-Computer" as well, but i got the same results. When i create a backjob and edit/test the login account information, the connection to the server is successfully established, but the connection to the share fails, though the same login account information is configured. When i run the backupjob, the job fails also. Anyways, i'm wondering why the "ServerType" property is displayed as "Windows Computer", even though the thecus N8800PRO NAS runs a linux operating system. Has someone experienced this behavior before? Might someone tell me, what i might be doing wrong?932Views0likes2Comments