Re: COPYTREE Question

In article <DTiotGxQ0bj6-pn2-mfjkhJUTBUYq@xxxxxxxxxxxxxxxxxxx>, "Dave Weatherall" <djw-nothere@xxxxxxxxxxxx> writes:
On Tue, 1 May 2007 00:38:25 UTC, JF Mezei
<jfmezei.spamnot@xxxxxxxxxxxxx> wrote:

Chuck Aaron wrote:
I want to copy a directory and all it's sub directories and files from one
server to a new server where the directories do not currently exist.
what is the best way to do this with or without copytree?


BACKUP is the tool. But it requires a magic incarnation to get it to
rebuild a new tree that is identical to the original one under the new root.

Use google for comp.os.vms in the last 2 years search for BACKUP and
[...*] and you'll find a coupl;e of posts of the magic incantation that
ended up working.

I do somthing like :-

$ backup drive:[root....] other_server::root_1.bck /sav /log /ver

It assumes you have an account on other_server and root_1.bck will be
placed in SYS$LOGIN there. You can drop the /log but i would keep the
/ver. The /log is there to ensure the command has been taken (entered)
as I intend it...

If you need to specify a username of other server then :-

$ backup drive:[root....] other_server"name password"::root_1.bck
/sav /log /ver


Log on to other_server and then :-

$ backup root_1.bck /sav /sel=[root...] new_drive:[root...] /lo /ver
/by_own=original

This will rebuild the directory tree, maintain file protections, Owner
and any ACL's. If you do have ACL identifiers, it would be a good idea
to ensure they exist on other_server first.

Those commands look right.

Note that BACKUP preserves the numeric values of the rights identifiers
appearing in ACLs. It does not preserve the identifier names.

One needs to ensure not only that the identifiers exist but also that
they have the same numeric value on the target system as the one they had
on the source system.

It does no good to have ORACLE_ADMINISTRATORS on the source machine
with hex code %x80001357 and ORACLE_ADMINISTRATORS on the target
machine with hex code %x80001358.

And it would be especially unfortunate if the target machine had BAD_HACKERS
at %x80001357.

The /INTERCHANGE qualifier to BACKUP will cause it to restore the
new files using default ACLs picked up from the target directory tree.
If the rights database on the source and target machines are not consistent
then this may be of considerable use. Of course you lose the original
ACLs.

If files are owned by UICs or identifiers that do not exist or are
not consistently numbered on the target system then one would obviously
not want to use /BY_OWNER=ORIGINAL.
.

Relevant Pages

  • Re: Unable to Backup on Network
    ... Also we have given FULL CONTROL rights to the target directory. ... "I like to log in to the SQL server console as the service account to test ... Also i am backing up through UNC only and not through Network Mapped Drive. ... >> Now i want to backup my database on a network. ...
    (microsoft.public.sqlserver.security)
  • Re: Complete fail over - with little or no manual changes?
    ... server name, same or different ip addresses to live in the same ... I would probably stop at shadow protect and one of the internet backup plans ... restoring "frequently" to the target. ... terminal server sitting next to the SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Find Big Files or Big Directories
    ... This server is backup using rsync. ... But I have found out that the target ...
    (Ubuntu)
  • Re: Find Big Files or Big Directories
    ... This server is backup using rsync. ... But I have found out that the target ...
    (Ubuntu)
  • Re: 2nd Domain in a 2 domain forest cannot be contacted
    ... Connecting to directory service on server qpidc03. ... Replication Site Latency Check ... * Performing upstream analysis. ... Performing downstream (of target) analysis. ...
    (microsoft.public.windows.server.dns)