Thanks for the info. I think I figured out my issue. I was trying to configure as a PureDisk storage server as opposed to MSDP. When configuring as an MSDP server, the volume was found and was configurable.
Thanks again for the help.
Your steps seem fine and NBU should therefore no longer have any record of the previous diskpool.
Can you confirm that the media server sees the drive as locally attached and the volume totally empty?
Have you created a subfolder that can be configured as dedupe volume?
When logged directly in the media server, I can see the drive and had created a folder that is meant to be configured as the dedup volume. I have also verified that I am able to read/write to this folder as well. Is there a command set that I can use to verify that NB is seeing the drive?
The main requirement is that the volume must be local (not network drive) and mounted as a drive letter.
See this section in NBU Dedupe Guide (taken from 7.7 manual):
Because the storage requires a directory path, do not use only the root node (/) or drive
letter (G:\) as the storage path. (That is, do not mount the storage as a root node (/) or a
drive letter (G:\).
You can use the following characters in the storage path name:
■ Any of the 26 letters of the International Standards Organization (ISO) Latin-script
alphabet, both uppercase (capital) letters and lowercase (small) letters. These are the
same letters as the English alphabet.
■ Any integer from 0 to 9, inclusive.
■ A space character.
■ Any of the following characters:
UNIX: _-:./\
Windows: _-:.\ (a colon (:) is allowed only after a drive letter (for example,
G:\MSDP_Storage)
NetBackup requirements for the deduplication storage paths may affect how you expose
the storage.
See “About MSDP storage and connectivity requirements” on page 40.
Thanks for the info. I think I figured out my issue. I was trying to configure as a PureDisk storage server as opposed to MSDP. When configuring as an MSDP server, the volume was found and was configurable.
Thanks again for the help.
