× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Backing up the IFS - what actually gets backed up?
  • From: "R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>
  • Date: Thu, 28 Jun 2001 08:25:06 -0400

-----Original Message-----
From: Peter Dow <pcdow@yahoo.com>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Wednesday, June 27, 2001 6:52 PM
Subject: Backing up the IFS - what actually gets backed up?


>My question is, what about other servers that are accessible via the IFS?
>Does the command
>
>SAV DEV('/QSYS.LIB/media-device-name.DEVD') |
> | |       |                |       OBJ(('/*') ('/QSYS.LIB' *OMIT) +
>|
> | |       |                |           ('/QDLS' *OMIT)(1) +
>|
> | |       |                |           ('/QIBM/ProdData' *OMIT) +
>|
> | |       |                |           ('/QOpenSys/QIBM/ProdData' *OMIT))
>+|
> | |       |                |       UPDHST(*YES)
>
>which is run by option 23 of the SAVE menu, backup any attached NT servers?
>What about servers connected via QFileSvr.400?  The Backup/Recovery Guide
is
>less than forthcoming about this.
>

Yes, so long as the server is varied off during the save. The space
(physically) in QNTC is not really what you are after.  The QFPNWSSTG is the
space your after. In either event, the omits above a specifically omit QSYS
(saved by normal library saves) QDLS (saved by SAVDLO) and IBM  product
information in the directories (don't store anything there thinking it's
PRODUCTION instead of PRODUCT <vbg>)


>I would guess that they're automagically omitted instead of having to be
>explicitly omitted as /QDLS is in the above command, but I don't know and I
>don't see any documentation that says so.
>

No, they are automatically included.


>When I tried to backup an object from a QNTC NT server, I got an error
>stating that QSECOFR was not authorized to the NT server. Presumably if she
>had been, it would've worked. How about with QFileSvr.400?

Again, why QNTC? It's just a lump, a heap. And what about QFileSvr.400?
Without OS/2, I don't think (pretty sure) anything goes in here. That was
the space for OS/2. But the data actually showed on QFPNWSSTG, like the NT.




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.