Snapshot security

Hi,

We have a primary server and another server that is the mirror of the
primary server and a snapshot of the mirror on that same server. SS is droped
and recreated everyday. Mirror also copies all the logins and security to use
this as a DR server. So the Snapshot automatically migrates all the logins
and thus those with permission os SS can also access the primary.

Is there is any workaround to avoid this situation? I.e., those with
permission in SS should not have permission in primary.

--
Regards

Priw
.

Relevant Pages

  • RE: Best Practices for Log Shipping
    ... do the Full Database backup which do not disturb your tlog backup on primary. ... log-shipping secondary server. ... Now that the primary server database is set as "full recovery" mode, ... the tran logs are being shipped successfully to the secondary server, ...
    (microsoft.public.sqlserver.replication)
  • Re: Primary + Secondary DNS
    ... obtain the zone data from the primary server. ... I don't however like to see ANY inconstencies in the DNS zones. ...
    (microsoft.public.windows.server.dns)
  • RE: [Released] [Contains offensive content] RE: Building Network Redundancy into a Perl Client
    ... Does anyone know why or where the phrase [Contains o f f e n s i v e ... Building Network Redundancy into a Perl Client ... > writing so that I can have a primary server and a backup server. ...
    (perl.beginners)
  • Re: Primary + Secondary DNS
    ... Also, Within MS DNS on the secondary server, we've used an Internal IP to ... obtain the zone data from the primary server. ...
    (microsoft.public.windows.server.dns)
  • Re: Least Invasive Way to Test SCR
    ... SCR that one and use it for testing. ... server and you're ready to revert back to your primary server, ... either have to reverse the SCR back to the primary server and then recover ... the primary via Windows Backup and then restore it to the secondary and use ...
    (microsoft.public.exchange.setup)
Quantcast