Newb Question

[k00laid]

Hey guys,

New to this board and very new to Progress DB Admin. Got what is most likely a question to show my ignorance but I'm kinda stuck. We've got a old HP-UX 10.20 box running 8.6c that is running what is soon be our history database (migrating to a new server running RHEL 5 and 10.1B) and I need to be able to do database backups from that box directly to FTP. The tape drive has broken on this POS and evidently samba is not supported.

In short is there a way to direct probkup online to a ftp connection?

 

[TomBascom]

Hey guys,

New to this board and very new to Progress DB Admin. Got what is most likely a question to show my ignorance but I'm kinda stuck. We've got a old HP-UX 10.20 box running 8.6c that is running what is soon be our history database (migrating to a new server running RHEL 5 and 10.1B) and I need to be able to do database backups from that box directly to FTP. The tape drive has broken on this POS and evidently samba is not supported.

In short is there a way to direct probkup online to a ftp connection?

There is no such thing as Progress 8.6c. I'd guess that that is your application's version #. It sounds sort of like an mfg/pro release.

HPUX 10.20 implies Progress version 8. If you're relatively lucky it's 8.3. Not that either HPUX 10.20 nor Progress 8.3 qualify as "lucky"

To answer the question... No.

But you can send probkup to a named pipe which might open some doors.

Are you so short on disk space that you cannot backup to disk first and then FTP the backup file(s)? How large is the database? Are you using the -com option?

 

[k00laid]

There is no such thing as Progress 8.6c. I'd guess that that is your application's version #. It sounds sort of like an mfg/pro release.

HPUX 10.20 implies Progress version 8. If you're relatively lucky it's 8.3. Not that either HPUX 10.20 nor Progress 8.3 qualify as "lucky"

To answer the question... No.

But you can send probkup to a named pipe which might open some doors.

Are you so short on disk space that you cannot backup to disk first and then FTP the backup file(s)? How large is the database? Are you using the -com option?

Sorry utter brain fart on that one. We are running 8.2B.

Unfortunately yes we are pretty short on space, at least don't have enough free that we can have a couple copies of a 56 GB DB sitting there. This is a 10 year old server, so don't expect much. Moving away is going to fix our problems but I've got to support this guy for the next couple of months while we finish getting crap off of it.

 

[TomBascom]

Is 56GB the space in use or the high water mark?

Using -com won't compress in the same sense that gzip et al do but it will eliminate empty blocks and such. So your backup will be smaller than the disk footprint. You could then gzip the backup extents and get them even smaller.

You could probably do something fancy using "expect" to coordinate compressing the backup extents as they are completed and prior to feeding the next extent name to probkup (it will just wait). But you would still need a fair amount of disk space and if you could do that you could also automate and FTP of those extents...

You mentioned that you don't have SAMBA support. Can you mount an NFS disk? That's often possible on these old HPUX systems.

I'd also make sure that after-imaging is enabled. These old clunkers are disasters waiting to happen and after-imaging can save your bacon when they go belly-up.