1 of 1 people found this helpful
It can monitor the following currently:
However, if you are talking about the repository, you can see that we're more limited for RDS deployments (MySQL/Aurora):
Supported database versions:
DATABASE EDITION VERSION Microsoft SQL Server
- 2008 R2 SP3
- 2012 SP3
- 2014 SP2
- 2016 SP1
Azure SQL Standard Service Tier or higher V12 MySQL
- 5.6.10 and later
- 5.7.9 and later
- MySQL RDS
- Aurora 5.6.10a and later
- 12.1 (single tenant and multitenant)
- 12.2 (single tenant and multitenant)
Now, having said all that, if you restore your repo database in an RDS SQL Server instance, I'm not sure DPA would even know (just repoint the repo.properties file to the new instance/database).
This configuration would not be officially supported though and it has not been tested to my knowledge.
I am tempted to try it out. I can't think of any reasons why it would not work. The database is just being used as a collection of tables. No other features are used, so it is pretty simple in terms of what it is expecting of the database.
My thought exactly. You can't set it up initially using RDS as we do a check if creating the repository that it will trip over.
But if the repository already exists and we edit the repo.properties file, don't see why the app would care.
If you do try it, let me know how it goes. Again, bear in mind that this would not be a supported configuration...