Thanks for the response Keith. UT seems to be kind of quiet on these question lately. I appreciate your time and information.

Rollin

>>I have posted a couple of questions lately about putting indexes in tables that do not have them (through code). This is in an effort to make all tables replicatable so that a full replication can be sent to the new backup server. The current legacy method is to manually copy the backup files to the 2nd server.
>>
>>In the effort to automate this proccess, I have learned how many things can't be replicated, and I am wondering if this is the best way to keep the backup server up-to-date. While there are no distibuted tables or queries, and there are no encrypted views etc. There may be other things that can't be replicated.
>>
>>So this is my question: Is there a better method to keep the backup server up-to-date??
>
>Rollin,
>
>There are other, more efficient ways to back up your data. You can use log-shipping or create a maintenance plan that includes a regular backup job.
>
>If you want a hot-swap backup server, it is best to use some of the specialized software for that purpose. There are 100 little things that you have to configure to replace a failing server with a new one of the same name.