• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 27 subscribers
  • Views 4795 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Move Repositories to New Storage

douglas.murphy
over 5 years ago

Environment:

  1. 2 Primary Cores with repositories split between two storage arrays, retention is only 2 week (the storage arrays are Dell Compellent and Dell EqualLogic
  2. 1 Replica Core is a self-contained 240TB Windows Storage Server based upon a SuperMicro platform, used by both sets of repositories, located off-site, retention 3 months
  3. This environment is working well, and is doing timely snapshots and replicas.

Issue:

  1. Purchased new, cheaper disk storage system from SuperMicro, same, or close, configuration to the Replica Core, Windows Storage Server based, reason is to free up expensive disk space on the arrays for other purposes
  2. Want to move Repositories to the new Storage Server, and it is not a problem to lose the Recovery Points with the 2 week retention due to the fact that the replication is working so well.
  3. However, need to retain the paths to the replicas.
  4. How do I do this? 

Thanks.

Parents
  • 0 over 5 years ago

    Easiest method would be stop the core service, copy (do not move) the repositories to their new location, give the volumes the same drive letter as the old repository volumes, and start the core service. The core will never know you moved the repos. 

    Of course that is assuming you are attaching the storage to the cores and using drive letters for your repo volumes. If you are using CIFS, it gets a bit more complicated.

    Let me know if this helps or if you are using CIFS.

  • 0 over 5 years ago in reply to Randy.Jones

    Ok, thanks, that will save the 2 week repository, but what about the replicas? Will the pointer to the replicas come with the copied repositories? Oh, and I'll be using iSCSI targets, which look, of course, like locally connected volumes.

  • 0 over 5 years ago in reply to douglas.murphy

    For the source cores you are only moving the the repositories to new storage correct?
    For the target core, you are replacing the entire core. OS and repo volumes?

    If yes for target core:

    1. break replication on source and target cores
    2. copy (do not move) repo from old server to new target core solution
    3. install core on new server
    4. go to More | Repositories
    5. click Connecting to Existing and add path to the copied repository
    6. on source cores, set replication back to new target core. 
Reply
  • 0 over 5 years ago in reply to douglas.murphy

    For the source cores you are only moving the the repositories to new storage correct?
    For the target core, you are replacing the entire core. OS and repo volumes?

    If yes for target core:

    1. break replication on source and target cores
    2. copy (do not move) repo from old server to new target core solution
    3. install core on new server
    4. go to More | Repositories
    5. click Connecting to Existing and add path to the copied repository
    6. on source cores, set replication back to new target core. 
Children
No Data