Let's see if I got the whole picture right...

To summarize,

ie on a practical example using the following template:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "
   DO NOT EDIT THIS FILE.  Use zonecfg(1M) instead.
<zone name="dbsz8005" zonepath="/zones/dbsz8005" autoboot="true">
 <network address="" physical="ce0"/>
 <filesystem special="/zones/virtual-filesystems/dbsz8005/var"
directory="/var" type="lofs">

/ would be the only filesystem that we could backup from within the zone but
we would have to use tsm to backup /dev, /var and else thru the global zone
client ... guess after all with our current setup, we should keep backuping
everything thru the global zone and develop a process for users to requests
backup restore thru the unix admins instead of a self service model as we
don't want them to access the global and they would in any case be confuse
with the filesystem structure being completly differently presented within
the global.

dbsz8005 #mount -v
/ on / type ufs
on Thu Nov 30 14:14:01 2006
/dev on /dev type lofs read/write/setuid/devices/zonedevfs/dev=4d40016 on
Thu Jan 25 11:29:34 2007
/var on /var type lofs read/write/setuid/devices/dev=41c59d9 on Thu Jan 25
11:29:34 2007

Mario, how do you present your filesystems to oracle ? Are you using raw
devices ?

On 1/25/07, mario heimel <[EMAIL PROTECTED]> wrote:

TSM client is supported in non-global-zones (only zsf is not supported)

we have in every zone a TSM client, which backuped the entire Zone (FS and
Oracle/SAP with rman ), so you can move zones without a reconfigure of TSM.

lofs mounts are per default excluded.

This message posted from opensolaris.org
zones-discuss mailing list


zones-discuss mailing list

Reply via email to