/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


Empty Deployments and Library Folder on the RSA

08/07/2018 445 views
We have recently set up our RSA in Germany, while the SDA is up and running in America. My actual problem is, the both appliances are linked ( ssl) and the test of connections are successful, but still the RSA got nothing in the Library and Deployments. In the overview i see, about 30 Gb are already synced and i am able to deploy from the SDA through the RSA.
Additionally the samba share of the SDA got different Folder like Drivers and so on, while the RSA Samba share just got restored which is empty.
Maybe someone got an idea.

Best regards

Robert
0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

1
I believe the RSAs are meant to be basic replication Appliances from the main one... so they will have less features compared to your main SDA

This will make sense for licensing purposes:
e.g.
We are big company, and there are BIG sites out there where having RSAs is not enough for us, so we bought 3 main SDAs, and we have like 20 something RSAs across the world, but there are sites where Full SDA functionalities are needed.

That is why you are entitled to have an unlimited amount of RSAs just using one main SDA license.

With that being said, according the Administrator's Manual, the RSAs will NOT display Images that were synced from a main SDA, RSA will only list Images that were Harvested\Captured by that RSA....

If you want to know if they were synced, you need to check from the SDA, or boot a KBE make sure is connected to the RSA and attempt to deploy an Image.
Answered 08/07/2018 by: Channeler
Red Belt

  • So we are actually already able to deploy through the RSA, but you have to start the deployment on the SDA side.
    • negative, you need to make sure you are connected to the RSA, before starting the Deployment, the KBE will tell you, look at the IP address on the KBE's footer, make sure is you RSA IP, not the SDA.
      • SDA and RSA are connected and linked. So you usually donĀ“t start deployment through the RSA, just on the SDA side and push it then to the RSA..
    • an RSA is able to Start a Deployment on it's own, as long as there was something previously synced from a main SDA, A system Image or Scripted Install
    • As Chenneler said, when you boot to the KBE make sure at the bottom it lists the IP of the RSA, not the SDA, if it does you may have to use KBE Manipulator, create a KBE that statically points to the RSA, re sync just this KBE, reboot and select that KBE. Another way to check is that you will only see those images that you have synced and not all the images present on the SDA.

All Answers

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ