Versions 7.1.4.0 and 8.1.x If we are only using legacy style backups (no vss), is there a way to configure TDP without having to setup proxy relationships? The install docs seem to indicate that proxies are only required for VSS backups, but I keep running into error messages like this when I try not using them: ANS1532E (RC5722) Proxy Rejected: Proxy authority has not been granted to this node.
We have a mix of SQL 2008R2/2012R2 and 2016 versions of OS & SQL, standalone as well as clustered, including some Always-On. Need to be able to run backups/restores from the mmc as well as scripted. Want to store both Standard & Always-On backups under the same node name per server. My strong preference would be to not have to define any proxy relationships, since they add a level of complexity that becomes really problematic when the DBA's need to perform cross-server restores. Example of my current setup: 1. Server name = JONAH 2. BA client dsm.opt file node name = JONAH 3. TDP dsm.opt file node name = JONAH_SQL 4. Tdpsql.cfg settings STRIPes 12 BUFFers 8 BUFFERSIze 8096 FROMSQLserver SQLAUTHentication INTegrated SQLBUFFers 0 SQLBUFFERSIze 4096 SQLSERVer . LOGFile tdpsql.log LOGPrune 14 MOUNTWaitfordata Yes DIFFESTimate 20 LANGuage AMENG BACKUPMethod Legacy BACKUPDestination TSM AlwaysOnNode JONAH_SQL UseAlwaysOnNode Yes When I try a full backup from the mmc with this config, I get this error: ANS1535E (RC5705) Proxy Rejected: The ASNODENAME and NODENAME options have the same value. I tried creating a new node name = JONAH_SQL2 and changing the tdpsql.cfg AlwaysOnNode to it. trying a new backup now I get: ANS1532E (RC5722) Proxy Rejected: Proxy authority has not been granted to this node. If there is a way to do this I would sure appreciate some guidance. Steve Schaub Systems Engineer II, Backup/Recovery Blue Cross Blue Shield of Tennessee ------------------------------------------------------------------------------ Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm