is that the actual error? that it states "server" in the error message?
What is you backup target, a data domain?
"direct save" means that with disk based devices, like AFTD (disk device) or Data Domain, that a client would try to send data directly to the disk device in question instead of legacy method by sending the data to a networker storage node (if you don't use a shared networker storage node, than the nw server would act as storage node).
A common reason that this cannot be done, is if a client is unable to correctly resolve the backup device or something wrong with the routing or connectivity.
For a DDboost device on a data domain the NW so-called "device access information" of a backup device states the name and Storage Unit folder under which the backup volume is located. for example :
"ddve01.labbuildr.local:/nwnve01/ddve01_fs"
So the client would need to be able to resolve the DD ddve01.labbuildr.local (in my case a FQDN as defined in DNS) to be able to write into the folder "ddve01_fs" of Storage Unit (which is a DDboost-enabled Mtree) "nwnve01".
Not being able to perform client direct, might still lead to a successful backup, but it would go through the NW storage node, however that might not be what you want, as it causes additional load, as then the client side deduplication will have to be done on the NW storage node) or the NW server if it acts as a NW storage node).
So look at resolving and connectivity, the very basics when using data domain devices...
barry_beckers
393 Posts
0
June 5th, 2023 06:00
is that the actual error? that it states "server" in the error message?
What is you backup target, a data domain?
"direct save" means that with disk based devices, like AFTD (disk device) or Data Domain, that a client would try to send data directly to the disk device in question instead of legacy method by sending the data to a networker storage node (if you don't use a shared networker storage node, than the nw server would act as storage node).
A common reason that this cannot be done, is if a client is unable to correctly resolve the backup device or something wrong with the routing or connectivity.
For a DDboost device on a data domain the NW so-called "device access information" of a backup device states the name and Storage Unit folder under which the backup volume is located. for example :
"ddve01.labbuildr.local:/nwnve01/ddve01_fs"
So the client would need to be able to resolve the DD ddve01.labbuildr.local (in my case a FQDN as defined in DNS) to be able to write into the folder "ddve01_fs" of Storage Unit (which is a DDboost-enabled Mtree) "nwnve01".
Not being able to perform client direct, might still lead to a successful backup, but it would go through the NW storage node, however that might not be what you want, as it causes additional load, as then the client side deduplication will have to be done on the NW storage node) or the NW server if it acts as a NW storage node).
So look at resolving and connectivity, the very basics when using data domain devices...