Re: How long for a shadow copy over CI

From: syslost (wm.reynolds_at_gmail.com)
Date: 10/07/05


Date: 7 Oct 2005 07:06:36 -0700


> That said, how do you feel about "unsupported" tricks? It's possible
> (recommendable is another question) to mirror within an array (HSx pair)
> and control that from the host, though the methods of communicating with
> the controller pair are unsupported anymore, though they still work to a
> fair degree.

If this means putting both members of the shadow set on the same set of
controllers, no. We need the applications to keep running even if we
lose both of the controllers serviceing one of the members of the
shadow set.



Relevant Pages

  • Re: How long for a shadow copy over CI
    ... If this means putting both members of the shadow set on the same set of ... lose both of the controllers serviceing one of the members of the ...
    (comp.os.vms)
  • Re: Reboot forces Shadowset Merge
    ... > Neale Hunt wrote: ... >> shadow set) from one of the other cluster nodes using the ... > and that the controllers and the host o.s. ...
    (comp.os.vms)
  • Re: ITS OFFICIAL...... FREEMASONRY IS FINISHED
    ... Members are leaving in their hundreds as most had no idea it was being run ... by an inner core of criminals who use Stasi tactics an unsuspecting public. ... controllers as they have been fed disinformation. ... the victims will sue you for murder, attempted murder, forced suicide, ...
    (uk.local.london)
  • Re: ntbackup will not run as scheduled task using Backup Operators?
    ... regardless of their own individual permissions on ... Backup Operators can also log on to domain controllers and shut them down. ... This group has no default members. ...
    (microsoft.public.windows.server.general)
  • Re: authentication problem
    ... > with regards to ipsec negotiation between domain members and domain ... > officially does not support ipsec negotiation communications between ... > controllers and doman members which is not explained in very much ...
    (microsoft.public.win2000.security)