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

Seed drive without replication

Currently using AA6/RR We're having some major issues getting a base image to apply from a couple of remote sites that are connected over a very low bandwidth pipe.

The base image takes several days just to finish, but hasn't due to server restarts or other network-related issues.  However, I'm being told by our vendor support team that we can use a USB drive to get a seed created from the target machine to copy onto the single core that we have.  All of my research shows that seeding can only take place via replication, and that replication must involve 2 or more cores, thus negating the possibility for our situation, as we only have one single core backup machine.

Am I reading the information wrong, as the only videos/info I've seen for seeding explicitly talks about replication, via source and target cores.  If I'm wrong, and it's possible, can somebody point me to the correct instructions on how to to so?  Remember, we only have one (1) Dell Rapid Recovery unit.

Parents
  • Hi UndergroundIT:
    Seed Drives are created on the source core and contain the recovery points that are to be moved on the target core as a part of "jump starting" (or repairing) the replication process. A slightly different operation is archiving -- creating Recovery points archives acting (in Rapid Recovery) as read only repositories.
    In both cases you need to be able to transfer consistent data to the Core before attempting creating a seed drive or archive.
    If I understand correctly, in your case, the issue is that, due to WAN limitations, you cannot have successful transfers (i.e. recovery points) on the core, thus there is nothing to seed or archive.
    Hope that this helps :)
Reply
  • Hi UndergroundIT:
    Seed Drives are created on the source core and contain the recovery points that are to be moved on the target core as a part of "jump starting" (or repairing) the replication process. A slightly different operation is archiving -- creating Recovery points archives acting (in Rapid Recovery) as read only repositories.
    In both cases you need to be able to transfer consistent data to the Core before attempting creating a seed drive or archive.
    If I understand correctly, in your case, the issue is that, due to WAN limitations, you cannot have successful transfers (i.e. recovery points) on the core, thus there is nothing to seed or archive.
    Hope that this helps :)
Children
No Data