Micheal,
You are misunderstading my reply.
AD restore:
I am not asking you to actually do a restore, if you just either run cmd line
restore or gui ( with proper switches), you can browse the restored
saveset\files and see what you backed up.
I know comvault had AD connector that allowed AD object level restore, which
Legato did not ( its been a while i done active backups with legato and i am
concentrating on SAN\NAS) therefor i siad that look into recent Legato
documentation if this type of backup are now possible as restoring entire AD or
portions of it if a small object is deleted is not very conveniance or
practicle.
Generally, AD authorative restores may be used in DR for recovering entire
domain AD not portions of the objects, depedning on your AD enviroment backing
up all or some DC may b e needes as for example each DC may have seperate role
and now they even have read only DC.( Generally speaking saveset ALL on the DC
should cover any restore requirement for the DC and AD )
DFS Namespace:
There is a way to backup mapped drive and so it may be possible to backup dfs
targets accidently or perposefully ( or i should say unknowingly, by
misconfigurations) therefor i say you should not need to backup any DFS links
or mapped drive, only backup the servers actual file system, i.e ( SERVERA)
D:\marketing share may be a DFS link for \\ad\server\marketing, so in your
case you would backup SERVERA's D drive and not worry about
\\ad\server\marketing DFS link.
Hope this is bit more clearer.
Fazil Saiyed
> Date: Mon, 23 Apr 2012 14:58:04 -0400
> From: Michael.Leone AT PHA.PHILA DOT GOV
> Subject: Re: [Networker] DFS backup questions
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>
> > Michael,
> > Your plan should include backing up individual servers rather then
> > the DFS links themselves,
>
> As I said, we already do backup the individual servers (which is where the
> DFS targets are also located). But those backups (saveset ALL) will not
> backup the DFS namespace folder.
>
> Specifically: in my test of saveset ALL, the only thing that didn't get
> backed up at Remote-1 was the DFS namespace folder. The DFS target folder
> (also on Remote-1) was easily backed up by ALL.
>
> * Remote-1:C:\ 69435:save: DFS Junction/Mountpoint detected:
> files/directories under `C:\DFSRoots\Public\' will not be backed up. To
> back up a DFS Junction/Mountpoint, specify the DFS Junction/Mountpoint as
> the saveset value
>
> And there can be files under "C:\DFSRoots\Public", as well as mounted
> targets (I am told). So the only way to backup those files is with a
> separate job, that specifies the DFS Junction/Mountpoint, as the message
> says (which agrees with the 7.6.2 documentation).
>
> > as long as all servers on your domain are
> > backed up, including any nas targets, you should not have to worry
> > or backup DFS links, backing up DFS links may be a bad idea any way
> > , since you may not get reliable backup performance and\or get
> > multiple backups running due to DFS links being present on more then
> > one server you backup.
>
> The documentation states that DFS links are *not* followed, so there
> should never be multiple backups of the same data (target servers/folders)
> happening. The DFS namespace only job would run at like 8PM, and the ALL
> job would run at 8:30. Since the 8PM job wouldn't follow the DFS links,
> none of the target folders would be backed up by that job. Only the 8:30
> ALL job would get the DFS target folders.
>
> > Just look to test restore one of the DC and you will see whats
> beingbacked up.
>
> Doing a test restore of a DC is not something done lightly. :-) Even in an
> isolated test environment ...
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with
> this list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|