• We run SQLSafe in our environment which has multiple untrusted domains.  The official word I got from Idera is that no, they don't support SQLSafe agents communicating across domains but it's possible to make it work.  Be aware tho that however you register/enter the server name determines how you reference that server down the road.  Meaning if you specify the FQDN then you must use that name at all times in your backup job.  Here's the response I got from Idera a while back regarding backing up db's across domains (if your domains are trusted then it's probably a nonissue).  Hope this helps.

    LC

    The communication between all SQLsafe components uses authentication, which means that each service will only respond to communication coming from Windows user accounts it recognizes. Therefore SQLsafe will not communicate across non-trusted domains. The only SQLsafe connection that does not require Windows authentication is the connection the the SQLsafeRepository SQL database. Both the Management Service and Management Console can be configured to connect to the repository using SQL authentication, which can cross non-trusted domains.

    Because SQLsafe components will only function inside a domain or among trusted domains, we recommend that you generate your licenses using the SQL instance name without the FQDN, such as SERVER\INSTANCE. If necessary, you could connect to the SQL instance hosting the SQLsafeRepository database using a FQDN.

    The licenses are specific to the exact SQL instance name used to generate the license, so attempting to backup SERVER.DOMAIN.COM\INSTANCE when the license applied is for SERVER\INSTANCE will fail, or, if within the first 14 days, will use a trial license.

    The following solution should contain the information necessary to assist you in overcoming this issue:

    Solution Title:

    How can I use SQLsafe to perform operations outside the local domain when there is not a domain trust?

    Solution Details:

    Non-trusted domains are not supported by the current release of SQLsafe, but it is often possible to make SQLsafe work in this situation.

    To do this, install all of the SQLsafe components in the primary domain (The SQLsafe Management Service, Management Console, and Repository). Then install all components except for the repository in the second domain. Set the management service in the second domain to send status events back to the repository database in the primary domain. This allows the user to monitor the status of all jobs from their centralized console. Please note that the SQLsafe Management Console in each domain will be able to trigger ad-hoc backups and restores only to other servers in its own domain.