Stash backup client: what does the tool do waiting the database backup?

[Pierre Zurmely]

I am using the backup tool: stash-backup-client-1.6.0

In my settings, I have

   in backup-config.properties:

      backup.scmdrain.timeout=600

   in stash-config.properties:

      backup.drain.database.timeout=600

      backup.drain.scm.timeout=600

When I run my backup, I have :

A backup could not be created. Reason: The backup on the server has become unresponsive and has not progressed in 300 seconds

I understandd that there is also a global timeout. and even if I have an interest in how I can set it, I am also wondering what my backup tool is trying to do.

In my logs, I can see that I have:

2015-02-04 02:40:30,242 INFO  [main] c.a.s.i.b.client.DefaultBackupClient Waiting on Stash database backup to complete

.......

2015-02-04 03:20:46,908 INFO  [main] c.a.s.i.b.client.DefaultBackupClient Waiting on Stash database backup to complete

So, What are the commands done by the tool to request the content of the database? Can I try to play it manually to check the reaction of my postgreSQL database?

How can I spend so many time waiting database backup with a global timeout of 300 seconds?

[ThiagoBomfim · Accepted solution]

Hi Pierre,

After troubleshooting your situation, we've written the following KB article:

• The backup on the server has become unresponsive and has not progressed in 300 seconds

That's been the solution for completing the backup on your instance with the backup client.

For customers with big instances, we recommend moving off the backup client and use the solution below:

• Using Stash DIY Backup

Best,
Thiago

[Pierre Zurmely]

Thank you, this page cover my questions

[ThiagoBomfim]

Hi Pierre,

I advise you raise an issue at https://support.atlassian.com.

We will be able to help you from there (collect logs etc.)

Best,

Thiago

[ThiagoBomfim]

Please quote this question as well as the other one you were monitoring.

[Pierre Zurmely]

SSP-7244 created

[ThiagoBomfim]

Thanks! I picked it up. Let's discuss it from there.