How can we improve the SMA (K1000)?

Granular Replication (Only Replicate Subsets of data)

103 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Andrew shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

8 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...
  • John commented  ·   ·  Flag as inappropriate

    Instead of saturation our Wan add an option to download these file directly from Dell's ftp.

  • Anthony Dumais commented  ·   ·  Flag as inappropriate

    Sure, we are a world wide compagny and we work with a minimum of 9 différents languages.
    No need to have chinese binaries in Spain and vice versa even id some user can travel from BU to others.

  • Chris Henning commented  ·   ·  Flag as inappropriate

    Excess patches replicated out to replication share server. All subscribed patches are rolled out to all replication servers even if they are not in any detect or patching schedules. This is a major waste of bandwidth. We need to be able to attached Label to the replication schedule for approved patches for replication.

  • BlaiseG commented  ·   ·  Flag as inappropriate

    I concur. We need the ability to be more selective with what gets replicated to each location. We don't need the same software packages used at our corporate locations replicated to all remote locations.

    I'd also like to see a 'replication only' agent. It's very challenging to have a handful of servers in the organization that is predominately intended to contain only our client systems. We use organizations to segregate servers and client computers given the different teams of people supporting each.

  • James Robinson commented  ·   ·  Flag as inappropriate

    This definitely needs looking at, if you only have a limited bandwidth to a specific replication site and you only want patches to be replicated for example; it results in huge volume to sync over a limited bandwidth and 90% is not required so in the previous example it would sync all software installers and scripts etc all of which are not needed.

    This also applies if you create a new managed install, it will then want to push this out to the rep share on the next schedule even though you dont want it shared and you know it will waste time bandwidth to the share to get it in sync.

    The rep share needs to be looked at like the K2000 Remote Site Appliance which gives you the ability to select what features you want syncing across.

Feedback and Knowledge Base