You just import them, phase 1 (build metadata file) and 2 (build files file); the import depends on nothing. I'm piggybacking on Carlos' correct response that neither policies nor pools matter here
Author: simon.weaver at astrium.eads.net (WEAVER, Simon)
Date: Wed, 7 Jun 2006 08:44:42 +0100
Hi Bob Thanks. I am extremely serious about DR, but wanted to clarify if the phase 1 import process was going to look for the volume pool the tape originally came from. If phase 1 works ok, and phase
Author: Richard.Mansell at ccc.govt.nz (Mansell, Richard)
Date: Wed, 7 Jun 2006 19:49:49 +1200
Out of interest, do you know if this holds true for multiplexed tapes, i.e. can be read using tar? --Original Message-- From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces a
You're welcome. Think about it logically--your data center doesn't exist any more, and perhaps that includes you. Somebody you never met is at a DR site in East Rutabaga with your previously off-sit
Author: simon.weaver at astrium.eads.net (WEAVER, Simon)
Date: Wed, 7 Jun 2006 11:39:56 +0100
Bob Correct, in order to do any import, thte tape MUST be known by NetBackup, however if its expired, my guess is, the tape ends up in SCRATCH, as it treats it as a NEW tape, even though we need to u
That betrays your mindset (not beating up on you, just pointing out that you're thinking in terms of your "current system and 3-year-old tape" scenario; I'm encouraging you to think bigger-picture,
Not without preprocessing, AFAIK. The placement of the multiplex headers is described in the SAG, but not the layout. I figured out part of it a few years ago while working a different issue and hav
Author: simon.weaver at astrium.eads.net (WEAVER, Simon)
Date: Wed, 7 Jun 2006 14:33:01 +0100
Bob I have a scratch pool defined. Any tapes NetBackup does not know about goes into this pool. But in the larger world, there is no harm creating a volume pool called IMPORT_ASTRIUM, moving the tape