You have the basic premise right. I have done this for multiple customers. One word of caution though, you want your database backup to be in relative sync with the filesystem. If you backup and replicate your filesystem nightly, you want to do the same with the database server. The database will reference the path to items in the filestore, and anytime you upadte the object in BL, the filename may change on the actual physical item. For instance, if I update an nsh script, the file name the database references may change to nsh_script_name.2 since the script was modified. You do not see this take place via the GUI. But if the database referenced this file, and it did not exist, you may have a headache to clean up. So my reccomendation is to determine what the acceptable level of tolerance is, and then set both replications to that interval.
Some thing that might make you life easier with the DR config:
Use aliases in the hosts files of the BL core infrastructure to reference each other. And in your bl configuration use these aliases rather than DNS host names.
then in your DR set of core infrastructure you would have the same aliases, but pointing to different ips
This will allow the BL configurations on both server to not have to be modified, and there would only have to be one difference in their configurations, and that is the IP addresses of the hosts files.
So by using the realtime synchronization within SQL 2005 we should be able to keep things up to date we would just need to focus on a solution like doubletake or something similar to sync the 2 BL servers.
Am I correct on this assumption?
Whichever tool you use is up to you. You just want to make sure the DB and Fileserver are relatively in sync. Everything else should be fine.
yes - that should do it. if the files in the 'file server' are newer that the db that should be ok, it's only bad if the db references files that don't exist.
Just in case anyone ends up on this article: start with the Best Practices Webinar for Deployment Architecture, this covers HA and DR. ( https://communities.bmc.com/communities/docs/DOC-21693 ) After that, head into the Deployment Architecture documentation:https://docs.bmc.com/docs/display/public/bsa83/Deployment+architecture Come back with questions!