Re: What keeps SAV from backing up /QNTC

As has been indicated within the thread this is intentional. Unless the /QNTC link is referring to an IXS or IXA attached server it treats the objects as if the ALWSAV attribute is *NO. Since those servers are no longer supported on POWER8 that era is over.

Sadly attempts to save other distributed file systems fail in the same way, albeit with slightly different messages issued. For example if you have a remote directory mounted via NFS to a local path in the IFS that will also not be saved. The message issued is a rather presumptuous "These objects are not needed for recovery."

What they mean of course is "not needed for recovery of this server" not that they may not be needed for restoring of your business to operational status. This one sort of irritates me though because there are times when being able to read through that NFS mount and save those objects to locally attached LTO would indeed be a good or at least useful option.

In any case IBM effectively treats backup and recovery on a per server basis. You need to understand all your servers and how to back up all of them. More importantly this rule ALWAYS applies:

"If you have never tested your backup by restoring your system from it, then you do not have a backup."

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 10/22/2015 3:32 PM, Jim Franz wrote:

If it is not specified in the omit of SAV, what stops it?
I've spent a while looking for the definitive statement...
I found where I can back up a /QNTC with SAV with some setup.

SAV DEV('/QSYS.LIB/TAP01.DEVD')
OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT))

Jim