Red Gate forums: SQL HyperBac 5

RE: HyperBac backups twice as slow

RajK — Mon, 18 Mar 2013 11:47:56 GMT

I am the support engineer that is responding to this request. I am investigating this case through our ticketing system at the moment as I am going to need you to send me your service.log file for review. Are you able to respond back to my email in this regards.

Sometimes some SAN drives can cause a little different behaviour and this is manifested in slower performance. I will try to work with you in this regards to see if we can improve the performance.

Thanks for your patience and feedback in this matter.

HyperBac backups twice as slow

timnylandjones — Fri, 15 Mar 2013 22:17:20 GMT

Hi,

We have a 400GB database and have recently purchased HyperBac. Our data and backup volumes are all on an EMC SAN, and prior to installing HyperBac our backups took around 75 minutes. I expected, given the size of the backup files, that I/O would be the main bottleneck and we'd be able to get backup times down to about 15 minutes for an 80GB backup file.

The backup files are certainly 80GB, but they take 2-and-a-half hours to run! Looking at the disk stats, this is what we see:

HyperBac disabled: Backup size 400GB, time taken 75 minutes, Read speed 100MBps, Write speed 100 MBps
HyperBac enabled: Backup size 80GB, time taken 150 minutes, Read speed 50 MBps, Write speed 8 Mbps.

The SAN is clearly capable of reading data at at least 100MBps, so I'd expect at worst that performance would remain the same. Servers are new and have plenty of RAM and cores, SAN storage processors are not overloaded when backups run (it's an office system that has a generous backup window).

So, what's going on?

SQL HyperBac has been retired

fionag — Tue, 05 Mar 2013 14:02:51 GMT

After a review of our database administration software, we've decided to focus development on our core database administration tools, and to retire the HyperBac powered products (SQL HyperBac, SQL Storage Compress, and SQL Virtual Restore).

If you already own one of these tools, you can continue to use our forums for help and support � just post your query here.

RE: What no - replacement product?

Tom Harris — Fri, 01 Mar 2013 15:11:32 GMT

Hi,

many thanks for your questions around SQL Hyperbac. Red Gate has no plans to develop this product further.

Red Gate will continue to invest in SQL Backup Pro, and we are offering our customers a free transition to that product for their SQL Server backups. It offers additional functionality to SQL Hyperbac around management and network resilience.

We will continue to offer support for our customers on SQL Hyperbac

Thanks, Tom

Tom Harris, PhD
Red Gate

What no - replacement product?

fgsimon — Fri, 01 Mar 2013 12:57:40 GMT

Hi all,
Now that HyperBack technology is no longer developed, what are your plans? Are there any alternatives out there?

Insufficient system resources exist to complete the requeste

allen05 — Fri, 01 Feb 2013 11:52:51 GMT

Came in this AM to check backup status, found multiple (60+ , one for each database?) messages as follows:

HyperBac Status Manager
---------------------------
Insufficient system resources exist to complete the requested service
---------------------------

I manually restored a database at random and it appears OK, plus all of the backups appear to have run correctly (files are located on the backup disk). The backup disk has plenty of room (backups are using less than 34% of total space available).

Are there any log file(s) I can review to determine the cause of the error? I am suspecting RAM right now (8G total on a 32-bit Windows 2003 server), with Commit Charge Peak that exceeds the physical memory total.

We currently have Hyperbak 5.4.1.5 installed.

RE: New Hyperbac build is twice as slow

edcdba — Mon, 03 Dec 2012 14:41:27 GMT

As I mentioned, our configuration has not changed between the two versions (4.0.31 to 5.9.0.13). That is at least if one can assume that the meainig of UI fields has not changed. We also don't have the cycles to spend on testing earlier 5.x releases.
We will remain on 4.0.31 until we migrate to SQL Server native compression to reduce our configuration footprint in the year ahead.

RE: New Hyperbac build is twice as slow

RajK — Mon, 03 Dec 2012 05:55:23 GMT

Hi,

Are you able to please send an email to support@red-gate.com with your contact details and mention for the attention of rajk in the subject?

Some of the performance issues are configuration specific and I will need to request some logs. Email will be better for this exchange.

On receipt of the email I will contact you back via email to help you with this issue.

Thanks for your patience in this matter.

RE: New Hyperbac build is twice as slow

RajK — Mon, 03 Dec 2012 05:54:26 GMT

Hi ecdba,

Are you able to please send an email to support@red-gate.com with your contact details and mention for the attention of rajk in the subject?

Some of the performance issues are configuration specific and I will need to request some logs. Email will be better for this exchange.

On receipt of the email I will contact you back via email to help you with this issue.

Thanks for your patience in this matter.

RE: Hyperbak Insufficient Resources message(s)

RajK — Wed, 21 Nov 2012 10:24:32 GMT

I am contacting you in regards to this support case.

At this stage I wanted to touch base and check if this issue has happened again? and at what frequency is it occuring?

Is the associated server a VM?

Thanks for your patience and feedback in this matter.

RE: Hyperbak Insufficient Resources message(s)

RajK — Wed, 21 Nov 2012 10:21:31 GMT

I am the support engineer investigating this issue you have raised. I am really sorry that you have run into this issue.

I was hoping to get some clarifications in regards to the activity on the system?

1) Has HyperBac been installed on this server recently or has it been running for a while? I am interested in knowing how long has this server been online for with Hyperbac on it?
2) Are you doing backups to local drives or across the network? For eg. is d:\ a mapped drive?
3) Have there any log files been created in the \hyperbac\logs directory?
4) If possible please send me the service.log file (located at \hyperbac\logs directory).
5) Any other files that exist that correspond to the time this issue happened? Are you able to look in the windows application, event and system logs? Are these file available to be sent across to us?
6) Is HyperBac installed in the default location or in a custom location? For eg. c:\ drive?

Thanks for your patience and feedback in this matter.

RE: Hyperbak Insufficient Resources message(s)

RajK — Thu, 01 Nov 2012 13:37:50 GMT

I am the support engineer investigating this issue you have raised. I am really sorry that you have run into this issue. This is being looked at via our support system.

I was hoping to get some clarifications in regards to the activity on the system?

1) Has HyperBac been installed on this server recently or has it been running for a while? I am interested in knowing how long has this server been online for with Hyperbac on it?
2) Are you doing backups to local drives or across the network? For eg. is d:\ a mapped drive?
3) Have there any log files been created in the \hyperbac\logs directory?
4) If possible please send me the service.log file (located at \hyperbac\logs directory).
5) Any other files that exist that correspond to the time this issue happened? Are you able to look in the windows application, event and system logs? Are these file available to be sent across to us?
6) Is HyperBac installed in the default location or in a custom location? For eg. c:\ drive?

Thanks for your patience and feedback in this matter.

Hyperbak Insufficient Resources message(s)

JReitter — Mon, 29 Oct 2012 12:35:08 GMT

RE: New Hyperbac build is twice as slow

edcdba — Thu, 25 Oct 2012 16:02:34 GMT

Will add that this is a 64-bit OS.

RE: New Hyperbac build is twice as slow

edcdba — Wed, 24 Oct 2012 20:21:25 GMT

Same experience after upgrade from 4.0.31 to 5.9.0.13. Average backup time has increases by a factor of 2.5.
We have not changed the configuration option:
Not using zip compatible or fast compression.
Not using encryption
Dynamic file updates disabled and not formating as virtual restore source or Oracle backup