DR for Crystal Enterprise and Business Objects

Have to build DR solution and subj is a part of it.

Maybe some one has done it already… share the experience please.

Dr in my case will between 2 different data centers, replication is san 2 san so on other side I have a warm standby that does not see san disks and will become active if and only if the primary data center is down, windows domain is the same, ip addresses, names of the servers are different. How a cluster will behave is interesting as well (I mean CE is on cluster, not geo distributed cluster).

I have CE90. I’m talking to their tech support that seems to be outsourced, they didn’t really produce in 5 days anything more then a part of their own documentation in pdf format for CE version I do not use J…

So I’m wondering maybe somebody had to walk similar path already…

I see you were already involved on the previous thread that discussed some of the general considerations for such SAN replication (it was titled SAN Replication and is at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=465113&SiteID=1). Unfortunately I'm not aware of any specific considerations for CE.

Don't Want to Script Replication Objects

I have a customized scripting procedure that will script all objects in a
given db.
My problem is, on a db set up for replication, I don't want to script all of
the objects that the system creates to manage replication -- just the
original db objects.
I there way to isolate replication objects?
Are they flagged somewhere in the system as objects that were not actually
created by the user, but by the server system?
Thanks
The best way is to remove them from the scripting interface. Its a pain to
do.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"rmg66" <rgwathney__xXx__primepro.com> wrote in message
news:%23OkAsxLAGHA.3924@.TK2MSFTNGP10.phx.gbl...
>I have a customized scripting procedure that will script all objects in a
> given db.
> My problem is, on a db set up for replication, I don't want to script all
> of
> the objects that the system creates to manage replication -- just the
> original db objects.
> I there way to isolate replication objects?
> Are they flagged somewhere in the system as objects that were not actually
> created by the user, but by the server system?
> Thanks
>
|||You might have to base this largely on the object name prefixes eg
MSmerge_conflict_<PublicationName>_<ArticleName> for the conflict tables. I
mentioned this to Redgate because it becomes a pain there (SQLCompare) also,
but they didn't seem to find an easy solution either.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||What do you mean?
What scripting interface?
How do I remove them without isolating them?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OxPHzGMAGHA.3924@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> The best way is to remove them from the scripting interface. Its a pain to
> do.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "rmg66" <rgwathney__xXx__primepro.com> wrote in message
> news:%23OkAsxLAGHA.3924@.TK2MSFTNGP10.phx.gbl...
all[vbcol=seagreen]
actually
>