Cloud OpenDedupe store DR to alternative Backup Exec server

Description

If the Backup Exec server that was using the OpenDedup cloud storage becomes non operational, follow the below described procedure to connect to the OpenDedup cloud storage from a recovery Backup Exec server.  It is critical that only a single Backup Exec server have access to an OpenDedup storage location at any time - multiple Backup Exec servers accessing a storage location can prevent both servers from accessing backup media present. Be sure the original Backup Exec server is prevented from accessing the storage location while implementing a recovery server.

On the recovery BE server, first create a new OpenDedup/SDFS volume using the Backup Exec OpenDedup configuration tool, OpenDedupeConfigUI.exe (see related documents),  using the same bucket\container with the same capacity settings and access\secret key as original. The password used and BE logon account is only pertaining to the recovery BE server and need not match the original. Do NOT add the OpenDedup storage in Backup Exec at this time.
Once the new OpenDedup volume has been created, open CMD as Administrator and execute the following to mount the volume:

~\program files\sdfs\mountsdfs -v <volumename> -m <driveletter as chosen in the tool>: -e <password>

NOTE: The -m switch is only used for SDFS version 3.4.x and Backup Exec 16.x  Later versions of SDFS, 3.6.x, with Backup Exec 20.x and later do not use a drive letter.

e.g.
mountsdfs -v recover_volume -m Q: -e thepassword

The mount command will show progress similar to:
C:\Program Files\sdfs>mountsdfs -v recover_odd -m U: -e thepassword
Running Program SDFS Version 3.4.7.1
reading config file = C:\Program Files\sdfs\etc\recover_odd-volume-cfg.xml
Loading BloomFilters |))))))))))))))))))))))))))))))))))))))))))))))))))| 100%

Waiting for last bloomfilters to load
Loaded entries 0
volume mounted
   %p  Lu  L

Once the SDSFS volume has mounted, and still in CMD run:

sdfscli --nossl --password <thepassword> --list-cloud-volumes

e.g
sdfscli --nossl --password thepassword --list-cloud-volumes

+------------+---------------------+------------+-----------------+----------+--------------+----------+--------------+--------------+
|  Host Name |                   ID                     |    Size             | Compressed Size      | cli port | local volume |
+------------+---------------------+------------+-----------------+----------+--------------++----------+--------------+--------------+
| <RecoverBE>| 6639249983950729986|          0             |               0                       |     6445   |     true            |
| <SourceBE>  | 8561233474752080254 | 7156047371 |          6846557768                |     6444   |     false          |
+------------+---------------------+------------+-----------------+----------+--------------+----------+--------------+--------------+

In this table SourceBE is the Backup Exec server that is now unavailable and RecoverBE is the Backup Exec server that will be used to reconnect to the Cloud OpenDedup storage. Port displayed here is 6445, you need to use what your configuration is set to.

From this output, copy the ID that is referenced to SourceBE and put it in the cmd as in the example below;

sdfscli --nossl --password <password> --sync-remote-cloud-volume <ID> --port <port#)

e.g

sdfscli --nossl --password thepassword --sync-remote-cloud-volume 8561233474752080254 --port 6445
command completed successfully

Next, within the Backup Exec UI go to the storage tab and run the Configure Storage wizard to add the recovery OpenDedup volume Open Storage device, and then restart the Backup Exec services when prompted. 
After the restart has completed, run an inventory and catalog of the storage location and all the sets from the from the Source Backup Exec is now seen and are usable on the Recover Backup Exec server.