Auto Galaxy Backup Utility

What does the Galaxy Backup Utility check for prior to running? What services should I make sure our stopped prior to running the Utility?

I have set up a powershell script that the windows task scheduler executes every night and in the script the galaxy backup utility is run if there are no users logged into the IDE. If someone is logged in then the back up is not performed and an email is sent notifying that the backup failed. 

When you do a manual backup with the Galaxy Database Manager you get a warning that says some thing along the lines of: During GR backup operation, no database-write operations are allowed. Please make sure no other applications are writing to the GR node"

What are the Archestra processes/services that would perform database writes? Or What else should be checked prior to performing a backup?

It seems like the backup utility auto fails if a import is happening when the backup utility is scheduled to run, and I want to capture that in my check so it can be included in the notification email. 

Parents
  • You only need to worry about open IDE instances where someone is working, OR if you have some other "tool" that was created with the GR Access Toolkit and it is performing writes to the galaxy database (unlikely).  Most people that I've seen set it up to automatic, just run it at like 2am.  I've not seen anyone check for any running processes.

  • Hi David, thanks for the response. Are you saying there is no way to know if someone actually performing work/performing an action that writes to the database versus just being logged in?

    We run our backups in the middle of the night, but sometimes someone may need to perform a very large CSV import that could go over night. It would be nice to check if the user is doing something like that, or if they just forgot to log out for the night. 

  • I'm not aware of a feature of the product that would allow you to identify that such activity was taking place.  There might be some SQL query you could run, but even then, it would likely only detect what was happening at the same time you tried to look.  Nothing to then say it didn't happen prior or after the query was run.  Since writes would come from IDE, or from a GR Access Toolkit application, ensuring both of those are all closed helps to ensure there are no writes to the galaxy database.

Reply
  • I'm not aware of a feature of the product that would allow you to identify that such activity was taking place.  There might be some SQL query you could run, but even then, it would likely only detect what was happening at the same time you tried to look.  Nothing to then say it didn't happen prior or after the query was run.  Since writes would come from IDE, or from a GR Access Toolkit application, ensuring both of those are all closed helps to ensure there are no writes to the galaxy database.

Children