cancel
Showing results for 
Search instead for 
Did you mean: 

CANNOT ADD STORAGE (WD EX4)

bletsas_kostas
Not applicable

Hello,

i am using BE2012 and just bought a WESTERN DIGITAL network drive MYCLOUD EX4.

I am trying to configure the new drive to BE2012 but it always responds this message.

"The path appears to be an invalid path. Please ensure the server name and share name are correct"

I executed the B2DTest.exe and everything PASSED except the 

Reparse Points and Sparse Files (WARNING).

I am accesing the disk easily without login prompts from the same server.

Can anyone help?

 

this is the final analysis

3/16/16 12:40:27 Final Analysis:
03/16/16 12:40:27 ---------------
03/16/16 12:40:27 Path Validation - PASSED
03/16/16 12:40:27 Create Directory - PASSED
03/16/16 12:40:27 Disk Space - PASSED
03/16/16 12:40:27 Volume Information - PASSED
03/16/16 12:40:27 Query DOS Devices - PASSED
03/16/16 12:40:27 Traverse Volume Info - PASSED
03/16/16 12:40:27 Memory Mapped Files - PASSED
03/16/16 12:40:27 Reparse Points - WARNING - Reparse points not supported on appliance: (0x32) The request is not supported.
03/16/16 12:40:27     The appliance does not support reparse points.  Some
03/16/16 12:40:27     of the advanced B2D technologies such as GRT may not
03/16/16 12:40:27     function.
03/16/16 12:40:27 
03/16/16 12:40:27     For GRT to function correctly, either the B2D path
03/16/16 12:40:27     or the temporary path for GRT operations must be an
03/16/16 12:40:27     NTFS partition that supports reparse points.  If this
03/16/16 12:40:27     is not the case, GRT operations will fail.
03/16/16 12:40:27 
03/16/16 12:40:27     For more information on this topic please refer to
03/16/16 12:40:27     the Backup Exec Administrators Guide.
03/16/16 12:40:27 Sparse Files - WARNING - Sparse files not supported on appliance: (0x32) The request is not supported.
03/16/16 12:40:27     * Sparse file support is required for Backup Exec
03/16/16 12:40:27     * versions prior to 12.6 for GRT to function.
03/16/16 12:40:27     * If the Backup Exec installation is 12.6 or greater
03/16/16 12:40:27     * this test can be ignored.
03/16/16 12:40:27 
03/16/16 12:40:27     The appliance does not support sparse files. Some
03/16/16 12:40:27     of the advanced B2D technologies such as GRT may
03/16/16 12:40:27     not function.
03/16/16 12:40:27 
03/16/16 12:40:27     For GRT to function correctly, either the B2D
03/16/16 12:40:27     path or the temporary path for GRT operations
03/16/16 12:40:27     must be an NTFS partition that supports sparse
03/16/16 12:40:27     files.  If this is not the case, GRT operations
03/16/16 12:40:27     fail.
03/16/16 12:40:27 
03/16/16 12:40:27     For more information on this topic please refer
03/16/16 12:40:27     to the Backup Exec Administrators Guide.
03/16/16 12:40:27 B2D Pre-allocation - PASSED
03/16/16 12:40:27 Random IO - PASSED
03/16/16 12:40:27 Default B2D Configuration - PASSED
03/16/16 12:40:27 Read buffer B2D Configuration - PASSED
03/16/16 12:40:27 No write buffering B2D Configuration - PASSED
03/16/16 12:40:27 File Handles - PASSED
03/16/16 12:40:27 Cleanup Directory - PASSED
03/16/16 12:40:27 
03/16/16 12:40:27 One or more of the test have completed with warnings.
03/16/16 12:40:27 Backup Exec should be compatible with the appliance; however,
03/16/16 12:40:27 some features or functions may not be available.

3 REPLIES 3

CraigV
Moderator
Moderator
Partner    VIP    Accredited

If you're trying to access it via a share, rather consider iSCSI. it appears to the media server as a local disk instead of a share, and gets around a lot of authentication issues. The NAS can do iSCSI:

http://www.wdc.com/en/products/products.aspx?id=1170

Read my article below on how I did this with Iomega:

https://www-secure.symantec.com/connect/articles/using-iscsi-backup-your-environment-nas-backup-exec
https://www-secure.symantec.com/connect/articles/using-iscsi-backup-your-environment-nas-backup-exec

 Thanks!

pkh
Moderator
Moderator
   VIP    Certified
Make sure you update your DNS server so that there if a forward and backwards path to the NAS

Larry_Fine
Moderator
Moderator
   VIP   

I am trying to configure the new drive to BE2012 but it always responds this message.

"The path appears to be an invalid path. Please ensure the server name and share name are correct"

How are you trying to connect to the NAS?  \\servername\share?  \\ipaddress\share?  \\FQDN\share?

Can you map a driver letter to it?

Craig's suggestion to explore iSCSI is good & would avoid authentication issues.