RM Not seeing all LUNs in EMC Replication Storage Group

just wanted to add to the discussion:

"Setting up a new host", I assume means you are adding a new host to the RM Gui.  I do not know if this is a Production Host or a Mount host.

Storage pools are recomended (as stated above) and will limit the devices that a job can use to the ones added to the pool.  Please get into the habbit of setting up pools for each job.

AppSets when set up are telling RM what data to back up, and RM backs up on a the LUN level.

The luns in the storage pool must match the exact size of the luns that are being backed up. If they are not the right size, then they will not be selected for a clone replica. (not gonna get into snaps  right now!)

Can you give further details on where you are seeing the 28 luns visable to a new host, but are expecting to see 30?

Can you try these steps once and see if the issue is resolved

Steps we performed for refreshed the db files on mount/Production host:

1. 1. Right-click RM Client service > Select Stop.
2. 2. Shutdown all SE daemons. Right-click EMC storapid > Select stop.
3. 3. Rename c:\program files\emc\symapi\db\symapi_db.bin to symapi_db.bin.old
4. 4. Rename c:\program files\emc\rm\client\bin\symapi_db_emcrm_client.bin to symapi_db_emcrm_client.bin.old
5. 5. Start up EMC storapid service.
6. 6. Run symcfg discover and confirm new symapi_db.bin created.
7. 7. Start RM client service and confirm new symapi_db_emcrm_client.bin created.
8. 8. re-discover array from the mount host in RM console.

Hi Bing59,

follow sumanthn's way and your issue will be resolved.

One comment. I hope that you are using Solution enabler for Replication Manager and not the "plain" Solution enabler installed on a management server. This is important.

Thanks for allthe helpful answers.  Part of the problem was when RM was installed the check box for exchange was not selected.  Another issue was with rights to the local admin group.