HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- DLT4000 compression and encrypted database
Operating System - HP-UX
1827293
Members
4006
Online
109717
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2007 09:05 AM
02-06-2007 09:05 AM
DLT4000 compression and encrypted database
Hello,
This weekend we upgraded our database application to one that encrypts the data files in the file systems. Now, backups no longer fit on the media. In fact, a 19GB file system no longer fits on a 20/40 tape.
Details:
LVM, vxfs file system, one very large file and a few small ones.
Quiescent file system.
vxdump 0bf 32 /dev/rmt/0mn /dev/vg03/datafs
DLT4000 HVD tape drive.
rp7410 system.
The database is Cache 5.1
The only change has been the database upgrade.
My guess is that the encryption of the database file is foiling the compression algorithm in the tape drive. Anybody encountered this? Do I need to get a different tape system so I don't have to swap tapes for my backup, or is there another solution?
Thanks,
Doug
This weekend we upgraded our database application to one that encrypts the data files in the file systems. Now, backups no longer fit on the media. In fact, a 19GB file system no longer fits on a 20/40 tape.
Details:
LVM, vxfs file system, one very large file and a few small ones.
Quiescent file system.
vxdump 0bf 32 /dev/rmt/0mn /dev/vg03/datafs
DLT4000 HVD tape drive.
rp7410 system.
The database is Cache 5.1
The only change has been the database upgrade.
My guess is that the encryption of the database file is foiling the compression algorithm in the tape drive. Anybody encountered this? Do I need to get a different tape system so I don't have to swap tapes for my backup, or is there another solution?
Thanks,
Doug
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2007 09:17 AM
02-06-2007 09:17 AM
Re: DLT4000 compression and encrypted database
Bear in mind, that a "19GiB" filesystem could actually be bigger than 19GiB if sparse files are in play --- and sparse files are very common in databases. It's a bit surprising that the native 20GiB capacity isn't big enough but depending upon the backup used, the metatdata overhead could account for the extra 1GiB and that doesn't take sparse files into account. In any event, never, ever assume that you have anything more than native capacity. The compressed capacity assumes a marketing 2:1 compression ration. The actual compression ratio is extremely data dependent and encrypted data is generally very difficult to compress.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2007 09:55 AM
02-06-2007 09:55 AM
Re: DLT4000 compression and encrypted database
Shalom,
Ultrium tape drives are the solution. Their starting capacity is 200 GB for Ultrium 1.
Compression ratios on encrypted data are not likely to exceed 1.5 to one.
SEP
Ultrium tape drives are the solution. Their starting capacity is 200 GB for Ultrium 1.
Compression ratios on encrypted data are not likely to exceed 1.5 to one.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2007 03:03 PM
02-06-2007 03:03 PM
Re: DLT4000 compression and encrypted database
> My guess is [...]
Most likely.
Many encryption schemes include some form of
compression, as it helps to scramble the
bits. For example:
http://www.gzip.org/
: [...] PGP already incorporates the gzip
: compression code, so use PGP if you need
: compression plus strong encryption.
If your new encryption system is not doing
this, perhaps it should (depending, of
course, on performance effects and available
CPU cycles).
In any case, encrypted data tend to appear
pretty random, which tends to defeat typical
compression schemes.
Most likely.
Many encryption schemes include some form of
compression, as it helps to scramble the
bits. For example:
http://www.gzip.org/
: [...] PGP already incorporates the gzip
: compression code, so use PGP if you need
: compression plus strong encryption.
If your new encryption system is not doing
this, perhaps it should (depending, of
course, on performance effects and available
CPU cycles).
In any case, encrypted data tend to appear
pretty random, which tends to defeat typical
compression schemes.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP