2 gig file limit on solaris 2.7 IDS 7.3 ontape?

Hi everyone. I have heard nasty rumours (unsubstantiated) that there are 'issues' when writing IDS 7.3 ontape backups to disk and the file gets larger than 2 gig, and the trying to restore from the disk file. This is on a Solaris 2.7 machine. My question is...is this just another one of those urban legends without merit or is it actually a genuine problem? The 7.3 admin manual does not mention any such issue. Thanks, Will

I found by poking around the Internet that this used to be a restriction with versions of IDS 7.24 and earlier. But apparently it is not a restriction anymore. I do know with certainty that there is no 2 GIG limit with 9.4 ontapes to disk because we use them all the time for backups and restores. But I just was wondering about IDS version 7.3 If anyone has a definitive answer I would appreciate it. I really do not have a viable way to test this-I can do the backup but not the restore and I just want to be sure that the restore would work. Thanks

WILL LANDSTROM schrieb: > I found by poking around the Internet that this used to be a restriction with > versions of IDS 7.24 and earlier. But apparently it is not a restriction > anymore. I do know with certainty that there is no 2 GIG limit with 9.4 > ontapes to disk because we use them all the time for backups and restores. But > I just was wondering about IDS version 7.3 If anyone has a definitive answer I > would appreciate it. I really do not have a viable way to test this-I can do > the backup but not the restore and I just want to be sure that the restore > would work. Thanks > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > Hi Will, a lil off topic maybe, but even using version 7.12 on SOL8 we used to write to named pipe. On the other end we had gzip running. We were able to write 6-7GB of compressed archiving data as soon as large file support was turned on. Compression rate was like 1:4. The disk space of these databases was around 25GB (sum of all npused). But it is always better to test, if this is possible! HTH dic_k -- Richard Kofler SOLID STATE EDV Dienstleistungen GmbH Vienna/Austria/Europe

Hi, your information about 2 GB limit for 7.x IDS is true, (at least for 32 bit editions, not sure about 64 bit editions) but you can get around the limit by using either a named pipe as backup device (which is not treated like a file from IDS, more like a tape, where there is no 2GB limit) or using a backup to a remote host (this requires a working setup for rsh (remote shell, with hosts.equiv, needs to work without password, TAPEDEV like hostname:/dir/filename). The latter can be done also for localhost. The named pipe solution gives you the possibility to write a gzipped file directly (as already stated below). Marcus -------- Weitergeleitete Nachricht -------- Von: Richard Kofler <richard.kofler@chello.at> Antwort an: ids@iiug.org An: ids@iiug.org Betreff: Re: 2 gig file limit on solaris 2.7 IDS 7.3 on.... [14232] Datum: Sat, 6 Dec 2008 12:54:30 -0500 WILL LANDSTROM schrieb: > I found by poking around the Internet that this used to be a restriction with > versions of IDS 7.24 and earlier. But apparently it is not a restriction > anymore. I do know with certainty that there is no 2 GIG limit with 9.4 > ontapes to disk because we use them all the time for backups and restores. But > I just was wondering about IDS version 7.3 If anyone has a definitive answer I > would appreciate it. I really do not have a viable way to test this-I can do > the backup but not the restore and I just want to be sure that the restore > would work. Thanks > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > Hi Will, a lil off topic maybe, but even using version 7.12 on SOL8 we used to write to named pipe. On the other end we had gzip running. We were able to write 6-7GB of compressed archiving data as soon as large file support was turned on. Compression rate was like 1:4. The disk space of these databases was around 25GB (sum of all npused). But it is always better to test, if this is possible! HTH dic_k --=-sd3F+lUjb/kNmexXaKn4

marcus. Thanks. I'll give the named pipe a try.