Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

multiple domains in Idera?? Expand / Collapse
Posted Thursday, August 30, 2007 12:54 AM


Group: General Forum Members
Last Login: Thursday, December 17, 2015 4:54 AM
Points: 146, Visits: 375

Can any one help to find whether Idera Sqlsafe will work in different domain...?

In my office we have a sqlsafe respository and we have jobs running from diff instances with same domain...

Now i'm planning do the same to my other server which is in diff domain... do i have to set up a new repository for that server domain or it will work with my old repository itself..??

Thanks in Advance!
- Kerobin
Post #395003
Posted Friday, August 31, 2007 7:27 AM



Group: Administrators
Last Login: Yesterday @ 1:59 PM
Points: 34,363, Visits: 18,582

I sent a note to Idera on this and hopefully they will respond soon.

Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #395522
Posted Friday, August 31, 2007 10:13 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 15, 2013 10:42 AM
Points: 5, Visits: 44

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.


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.

Post #395614
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse