ZFS snapshot and SCP

Hi,
Any one can share the difference between the usage of ZFS snapshot/restoring the data and ordinary SCP to other host.
Regards
Siva

The idea is that when you create a clone, it is lightweight and based on the snapshot. That's what makes it so fast. You're not copying every block in the filesystem. So the snapshot is what ties together the parent filesystem and the clone.
For the clone to be independent, you'd have to copy all the blocks. There's no option to do that within the clone process. So as long as both the parent filesystem and the clone filesystem are around, the snapshot has to exist as well.
Darren

Similar Messages

Zfs snapshots and booting ...

Hello,
In solaris 9, filesystem snapshots did not survive reboots. Do zfs snapshots in solaris 10 persist across reboots ?
Can I boot off of a zfs partition ?
thanks.

Does this mean that when new machines appear with zfs
support, OR when I can update my PROM, that I will be
able to boot a zfs partition ?ZFS isn't out yet, so your question is premature. We'll get a look at it within a few weeks, hopefully.
However, a few months ago it was widely reported by the developers that the initial release would not have boot support. Who knows if this has changed or not.
I don't see any particular reason that PROM or hardware support is required, it should just need a bootloader that understands ZFS. I don't think that there's any UFS support in the existing proms. Just stuff that understands the VTOC label and how to load and execute a few blocks from a particular slice.
Darren

Cloning a ZFS rooted zone does a copy rather than snapshot and clone?

Solaris 10 05/08 and 10/08 on SPARC
When I clone an existing zone that is stored on a ZFS filesystem the system creates a copy rather than take a ZFS snapshot and clone as the documentation suggests;
Using ZFS to Clone Non-Global Zones and Other Enhancements
Solaris 10 6/06 Release: When the source zonepath and the target zonepath both reside on ZFS and are in the same pool,
zoneadm clone now automatically uses the ZFS clone feature to clone a zone. This enhancement means that zoneadm
clone will take a ZFS snapshot of the source zonepath and set up the target zonepathCurrently I have a ZFS root pool for the global zone, the boot environment is s10u6;
rpool 10.4G 56.5G 94K /rpool
rpool/ROOT 7.39G 56.5G 18K legacy
rpool/ROOT/s10u6 7.39G 56.5G 6.57G /
rpool/ROOT/s10u6/zones 844M 56.5G 27K /zones
rpool/ROOT/s10u6/zones/moetutil 844M 56.5G 844M /zones/moetutil
My first zone is called moetutil and is up and running. I create a new zone ready to clone the original one;
-bash-3.00# zonecfg -z newzone 'create; set autoboot=true; set zonepath=/zones/newzone; add net; set address=192.168.0.10; set physical=ce0; end; verify; commit; exit'
-bash-3.00# zoneadm list -vc
ID NAME STATUS PATH BRAND IP
0 global running / native shared
- moetutil installed /zones/moetutil native shared
- newzone configured /zones/newzone native shared
Now I clone it;
-bash-3.00# zoneadm -z newzone clone moetutil
Cloning zonepath /zones/moetutil...
I'm expecting to see;
-bash-3.00# zoneadm -z newzone clone moetutil
Cloning snapshot rpool/ROOT/s10u6/zones/moetutil@SUNWzone1
Instead of copying, a ZFS clone has been created for this zone.
What am I missing?
Thanks
Mark

Hi Mark,
Sorry, I don't have an answer but I'm seeing the exact same behavior - also with S10u6. Please let me know if you get an answer.
Thanks!
Dave

Zfs snapshot of "zoned" ZFS dataset

I have a ZFS (e.g. tank/zone1/data) which is delegated to a zone as a dataset.
As root in the global zone, I can "zfs snapshot" and "zfs send" this ZFS:
zfs snapshot tank/zone1/data and zfs send tank/zone1/data without any problem. When I "zfs allow" another user (e.g. amanda) with:
zfs allow -ldu amanda mount,create,rename,snapshot,destroy,send,receivethis user amanda CAN DO zfs snapshot and zfs send on ZFS filesystems in the global zone, but it can not do these commands for the delegated zone (whilst root can do it) and I get a permission denied. A truss shows me:
ioctl(3, ZFS_IOC_SNAPSHOT, 0x080469D0)          Err#1 EPERM [sys_mount]
fstat64(2, 0x08045BF0)                          = 0
cannot create snapshot 'tank/zone1/data@test'write(2, " c a n n o t   c r e a t".., 53) = 53Which setting am I missing to allow to do this for user amanda?
Anyone experiencing the same?
Regards,
Marcel

Hi Robert,
Thanks for your response. I suspected this might be the case, but it seems like I get conflicting information from the Sun website. It still says recommended and security patches are free everywhere I looked except when I went to download them. We got this machine in October and I obtained and installed a recommended patch cluster as well as a bunch of ZFS patches (it might have even been early November, shortly before the update), using only a valid account with no contract.
It would have been nice to know the policy on patch clusters was changing shortly, since now I want to use the snapshots as a backup for users.
For us at least, an upgrade install would be a royal pain in the butt, since this machine is sitting in a data center in the basement and that would entail me signing in there and sitting on the floor while it installs from DVD media.

ZFS clones and snapshot... can't delete snapshot were clone is based on

root@solaris [/] # zfs list -r
NAME   USED AVAIL REFER MOUNTPOINT
home   100K 9,78G    21K /datahome
root@solaris [/] # zpool list
NAME   SIZE   USED AVAIL    CAP HEALTH ALTROOT
home 9,94G   108K 9,94G     0% ONLINE -
root@solaris [/] # zfs create home/test
root@solaris [/] # zfs snapshot home/test@today
root@solaris [/] # zfs clone home/test@today home/myclone
root@solaris [/] # zfs list -r
NAME              USED AVAIL REFER MOUNTPOINT
home              138K 9,78G    23K /datahome
home/myclone         0 9,78G    21K /datahome/myclone
home/test          21K 9,78G    21K /datahome/test
home/test@today      0      -    21K -
root@solaris [/] # zfs promote home/myclone
root@solaris [/] # zfs list -r
NAME                 USED AVAIL REFER MOUNTPOINT
home                 140K 9,78G    24K /datahome
home/myclone          21K 9,78G    21K /datahome/myclone
home/myclone@today      0      -    21K -
home/test               0 9,78G    21K /datahome/test
root@solaris [/] # zfs destroy home/myclone
cannot destroy 'home/myclone': filesystem has children
use '-r' to destroy the following datasets:
home/myclone@today
root@solaris [/] # zfs destroy home/myclone@today
cannot destroy 'home/myclone@today': snapshot has dependent clones
use '-R' to destroy the following datasets:
home/test
root@solaris [/] #Why can't I destroy a snapshot? home/myclone is now a volume that is not linked to home/test.
So I would expect to be able to delete the snapshot from myclone.
Maybe I misunderstand something about how this works or I have the wrong expectations.
I would expect a clone to be something like a copy that is independent of the volume being cloned.

The idea is that when you create a clone, it is lightweight and based on the snapshot. That's what makes it so fast. You're not copying every block in the filesystem. So the snapshot is what ties together the parent filesystem and the clone.
For the clone to be independent, you'd have to copy all the blocks. There's no option to do that within the clone process. So as long as both the parent filesystem and the clone filesystem are around, the snapshot has to exist as well.
Darren

ZFS 7320c and T4-2 server mount points for NFS

Hi All,
We have an Oracle ZFS 7320c and T4-2 servers. Apart from the on-board 1 GB Ethernet, we also have a 10 Gbe connectivity between the servers and the storage
configured as 10.0.0.0/16 network.
We have created a few NFS shares but unable to mount them automatically after reboot inside Oracle VM Server for SPARC guest domains.
The following document helped us in configuration:
Configure and Mount NFS shares from SUN ZFS Storage 7320 for SPARC SuperCluster [ID 1503867.1]
However, we can manually mount the file systems after reaching run level 3.
The NFS mount points are /orabackup and /stage and the entries in /etc/vfstab are as follows:
10.0.0.50:/export/orabackup - /orabackup nfs - yes rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp,vers=3
10.0.0.50:/export/stage - /stage nfs - yes rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp,vers=3
On the ZFS storage, the following are the properties for shares:
zfsctrl1:shares> select nfs_prj1
zfsctrl1:shares nfs_prj1> show
Properties:
aclinherit = restricted
aclmode = discard
atime = true
checksum = fletcher4
compression = off
dedup = false
compressratio = 100
copies = 1
creation = Sun Jan 27 2013 11:17:17 GMT+0000 (UTC)
logbias = latency
mountpoint = /export
quota = 0
readonly = false
recordsize = 128K
reservation = 0
rstchown = true
secondarycache = all
nbmand = false
sharesmb = off
sharenfs = on
snapdir = hidden
vscan = false
sharedav = off
shareftp = off
sharesftp = off
sharetftp =
pool = oocep_pool
canonical_name = oocep_pool/local/nfs_prj1
default_group = other
default_permissions = 700
default_sparse = false
default_user = nobody
default_volblocksize = 8K
default_volsize = 0
exported = true
nodestroy = false
space_data = 43.2G
space_unused_res = 0
space_unused_res_shares = 0
space_snapshots = 0
space_available = 3.97T
space_total = 43.2G
origin =
Shares:
Filesystems:
NAME SIZE MOUNTPOINT
orabackup 31K /export/orabackup
stage 43.2G /export/stage
Children:
groups => View per-group usage and manage group
quotas
replication => Manage remote replication
snapshots => Manage snapshots
users => View per-user usage and manage user quotas
zfsctrl1:shares nfs_prj1> select orabackup
zfsctrl1:shares nfs_prj1/orabackup> show
Properties:
aclinherit = restricted (inherited)
aclmode = discard (inherited)
atime = true (inherited)
casesensitivity = mixed
checksum = fletcher4 (inherited)
compression = off (inherited)
dedup = false (inherited)
compressratio = 100
copies = 1 (inherited)
creation = Sun Jan 27 2013 11:17:46 GMT+0000 (UTC)
logbias = latency (inherited)
mountpoint = /export/orabackup (inherited)
normalization = none
quota = 200G
quota_snap = true
readonly = false (inherited)
recordsize = 128K (inherited)
reservation = 0
reservation_snap = true
rstchown = true (inherited)
secondarycache = all (inherited)
shadow = none
nbmand = false (inherited)
sharesmb = off (inherited)
sharenfs = sec=sys,rw,[email protected]/16:@10.0.0.218/16:@10.0.0.215/16:@10.0.0.212/16:@10.0.0.209/16:@10.0.0.206/16:@10.0.0.13/16:@10.0.0.200/16:@10.0.0.203/16
snapdir = hidden (inherited)
utf8only = true
vscan = false (inherited)
sharedav = off (inherited)
shareftp = off (inherited)
sharesftp = off (inherited)
sharetftp = (inherited)
pool = oocep_pool
canonical_name = oocep_pool/local/nfs_prj1/orabackup
exported = true (inherited)
nodestroy = false
space_data = 31K
space_unused_res = 0
space_snapshots = 0
space_available = 200G
space_total = 31K
root_group = other
root_permissions = 700
root_user = nobody
origin =
zfsctrl1:shares nfs_prj1> select stage
zfsctrl1:shares nfs_prj1/stage> show
Properties:
aclinherit = restricted (inherited)
aclmode = discard (inherited)
atime = true (inherited)
casesensitivity = mixed
checksum = fletcher4 (inherited)
compression = off (inherited)
dedup = false (inherited)
compressratio = 100
copies = 1 (inherited)
creation = Tue Feb 12 2013 11:28:27 GMT+0000 (UTC)
logbias = latency (inherited)
mountpoint = /export/stage (inherited)
normalization = none
quota = 100G
quota_snap = true
readonly = false (inherited)
recordsize = 128K (inherited)
reservation = 0
reservation_snap = true
rstchown = true (inherited)
secondarycache = all (inherited)
shadow = none
nbmand = false (inherited)
sharesmb = off (inherited)
sharenfs = sec=sys,rw,[email protected]/16:@10.0.0.218/16:@10.0.0.215/16:@10.0.0.212/16:@10.0.0.209/16:@10.0.0.206/16:@10.0.0.203/16:@10.0.0.200/16
snapdir = hidden (inherited)
utf8only = true
vscan = false (inherited)
sharedav = off (inherited)
shareftp = off (inherited)
sharesftp = off (inherited)
sharetftp = (inherited)
pool = oocep_pool
canonical_name = oocep_pool/local/nfs_prj1/stage
exported = true (inherited)
nodestroy = false
space_data = 43.2G
space_unused_res = 0
space_snapshots = 0
space_available = 56.8G
space_total = 43.2G
root_group = root
root_permissions = 755
root_user = root
origin =
Can anybody please help?
Regards.

try this:
svcadm enable nfs/clientcheers
bjoern

Zfs snapshot question

Hi guys,
I will really appreciate it if someone can answer this for me.
I do understand that you can use snapshots to back up file systems. But they also use up pool space when their file systems grow.
So, is it necessary to create zfs snapshots even when you already have a full system back up in place?
Thank you very much for your kind explanation.
Arrey

985798 wrote:
So, is it necessary to create zfs snapshots even when you already have a full system back up in place? Nobody will force you to create or keep snapshots and if you are happy with taking "classic" backups then there may be no need for additional snapshots. And since snapshots will also take up space in your pool, it is usually a good idea to keep them only for a short period and delete them periodically. I like to use snapshots for two purposes:
- create a snapshot, then write that snaptshot to take and destroy it afterwards. that way, you can guarantee that this tape backup is consistent
- create snapshot at regular intervals and keep them around for a few days so that if I need to restore a file from just a day ago I don't have to go back to tapes but can rather fetch it from the snapshot. So that would be in addition to regular backups
cheers
bjoern

Receiving zfs snapshots from remote system

Hi guys,
if you create zfs snapshots on systemA and then send them to systemB, how do you recover the snapshots from systemB back to systemA?
Thanks guys .

The same way, just do a send/receive from B to A. But that would create a new filesystem, not get you the snapshot within the original zfs back.
cheers
bjoern

Is there any way to refresh the zfs snapshot other than creating another on

Hi,
I want to use the zfs send / recv replication, after I create the snapshot and do send/ recv to the remote filesystem, is there any way to do send and recv from the same snapshot after making some changes to the original filesystem other than creating another snapshot every time before send / recv
Thanking you
Ushas Symon

No, you'd have to take another snapshot and then send it, but you don't need to save all the snapshots after you are done. If you script it out to take snapshots fairly often during the day, the amount of data would be small. You can also send to a file and then backup that file to tape or whatever, you wouldn't have to save a million snapshots. You can also look into OpenSolaris' Time Slider function.

ZFS Snapshots/ZFS Clones of Database on sun/solaris

Our production database is on Sun/Solaris 10 (SunOS odin 5.10 Generic_127127-11 sun4u sparc SUNW,SPARC-Enterprise) with oracle 10.1.0 . It is about 1TB in size. We have also created our MOCK and DEVELOPMENT databases from the Production database. To save disk space, we created these databases as ZFS Snapshots/ZFS Clones at the OS level and are using less than 10GB each being clones as on now. Now I want to upgrade the production database from oracle 10.1 to 11.2 but I don't want to upgrade the MOCK and DEVELOPMENT databases for the time being and want them to continue to run as clones on 10.1. After upgrade, Prod will run from 11g oracle tree one one machine and MOCK/DEVL on 10g tree on another machine. Will the upgrade of Production from 10.1 to 11.2 INVALIDATE the cloned MOCK and DEVELOPMENT databases?? There might be data types/features in 11g which do not exist in 10g.
Below are the links to the documentation we used to create the snapshots.
http://docs.huihoo.com/opensolaris/solaris.../html/ch06.html
http://docs.huihoo.com/opensolaris/solaris...ml/ch06s02.html

Hi,
The mentioned links in the post is not working.
I would suggest u to raise an Official S.R. with http://support.oracle.com prior upgrading your database.
Also you can try this out with 10g db installation on TEST machine and create databases as ZFS Snapshots/ZFS Clones at the OS level for MOCK. Then upgrade the 10g database and test it.
Refer:
*429825.1 -- Complete Checklist for Manual Upgrades to 11gR1*
*837570.1 -- Complete Checklist for Manual Upgrades to 11gR2*
Regards,
X A H E E R

The future of Snapshot, and similar tools.

My apologies for posting this twice. I posted it first as a follow up
to an old thread in ...
novell.support.zenworks.desktop-management.6x.install-setup
I am quoting some comments made in that forum.
Then after surfing the forums for awhile, I thought the issue might get
more attention, if I posted it here. I am looking for ideas and advice
on the future of snap shot, and any tools that Novell might provide to
replace it.
If I could address some of these comments, in hopes of better
understanding ...
RE: >>>
> Most companies invest in packaging tools such the full version of
> AdminStudio to create deployment packages. They then use their desktop
> management suites to deploy those packages.
Admin Studio is not cheap. After a client has spend thousands of
dollars to implement ZENWorks, now I have to tell them to drop another
couple thousand down for an application packager. I also don't fully
understand Novell's relationship with the product, they don't seem to be
partnering well together, I'd appreciate anyone else's read on this
relationship.
RE: >>
> Novell has for over 5 years now been trying to steer people from
> Snapshot
I've heard that statement made verbally by many engineers, but I don't
always see the practice following that.
Has Novell ever gone on record to state they will no longer support snap
shot???
RE: >> > If your snapshots are failing with the latest versions of
snapshot, then
> most likely your software package falls outside the scope of what
> snapshot should be trying to handle.
Maybe I've just gotten lucky? I've have not had many issues with using
snapshot, and I have been involved in a wide variety of applications.
I have seen the statement made on the forum that ZEN Works is not really
a "Packaging" suite. While that may be a true statement, because
Snapshot has been packaged with the product for so long, the mind set of
customers is that it is expected to work, and be supported.
I look forward to additional comments on this matter.

Tom,
I'm not sure what exactly are you searching for? ZdM is already providing
you with snapshot replacement - AdminStudio ZfD edition, included in ZfD
price.
AdminStudio part for preparing snapshot MSI is identical in ZfD and
Professional edition.
All comments you qouted (including this one) are personal opinions - I
suggest you to try AdminStudio ZfD edition and make your own.
Denis
"tom" <[email protected]> wrote in message
news:[email protected]...
> My apologies for posting this twice. I posted it first as a follow up to
> an old thread in ...
>
> novell.support.zenworks.desktop-management.6x.install-setup
>
> I am quoting some comments made in that forum.
>
> Then after surfing the forums for awhile, I thought the issue might get
> more attention, if I posted it here. I am looking for ideas and advice on
> the future of snap shot, and any tools that Novell might provide to
> replace it.
>
>
> If I could address some of these comments, in hopes of better
> understanding ...
>
> RE: >>>
> > Most companies invest in packaging tools such the full version of
> > AdminStudio to create deployment packages. They then use their desktop
> > management suites to deploy those packages.
>
> Admin Studio is not cheap. After a client has spend thousands of dollars
> to implement ZENWorks, now I have to tell them to drop another couple
> thousand down for an application packager. I also don't fully understand
> Novell's relationship with the product, they don't seem to be partnering
> well together, I'd appreciate anyone else's read on this relationship.
>
> RE: >>
> > Novell has for over 5 years now been trying to steer people from
> > Snapshot
>
> I've heard that statement made verbally by many engineers, but I don't
> always see the practice following that.
>
> Has Novell ever gone on record to state they will no longer support snap
> shot???
>
>
> RE: >> > If your snapshots are failing with the latest versions of
> snapshot, then
> > most likely your software package falls outside the scope of what
> > snapshot should be trying to handle.
>
> Maybe I've just gotten lucky? I've have not had many issues with using
> snapshot, and I have been involved in a wide variety of applications.
>
> I have seen the statement made on the forum that ZEN Works is not really a
> "Packaging" suite. While that may be a true statement, because Snapshot
> has been packaged with the product for so long, the mind set of customers
> is that it is expected to work, and be supported.
>
> I look forward to additional comments on this matter.

How to cancel email notification from snapshot and simulation

Hi,
We've activated workflow template WS28700001 so that email notification can be triggered when task release. Meanwhile we are using snapshot and simulation at the same time. But when saving sanpshot or simulation the tasks which have status of released also trigger email nofitication. How to cancel this notification of snapshot and simulation?
Regards.

Hi Ravi
I have added a Container Element(version) in workflow template WS28700001 and set a workflow start condition as follows.
&Task.Version& = ' '
Regards
Yemi

SQL Server 2008 R2 Replication - not applying snapshot and not updating all repliacted columns

We are using transactional replicating on SQL Server 2008 R2 (SP1) using a remote distributor. We are replicating from BaanLN, which is an ERP application to up to 5 subscribers, all using push publications.
Tables can range from a couple million rows to 12 million rows and 100's of GBs in size.
And it's due to the size of the tables that it was designed with a one publisher to one table architecture.
Until recently it has been working very smooth (last four years)) but we have come across two issues I have never encountered.
While this has happen a half dozen times before, it last occurred a couple weeks ago when I was adding three new publications, again a one table per publication architecture.
We use standard SS repl proc calls to create the publications, which have been successful for years.
On this occasion replication created the three publications, assigned the subscribers and even generated the new snapshot for all three new publications.
However, while it appeared that replication had created all the publications correctly from end to end, it actually only applied one of the three snapshot and created the new table on both of the new subscribers (two on each of the
publications). It only applied the snapshot to one of the two subscribers for the second publications, and did not apply to any on the third.
I let it run for three hours to see if it was a back log issue.
Replication was showing commands coming across when looking at the sync verification at the publisher and
it would even successfully pass a tracer token through each of the three new publications, despite there not being tables on either subscriber on one of the publishers and missing on one of the subscribers on another.
I ended up attempting to reinitialize roughly a dozen times, spanning a day, and one of the two remaining publications was correctly reinitialized and the snapshot applied, but the second of the two (failed) again had the same mysterious result, and
again looked like it was successful based on all the monitoring.
So I kept reinitializing the last and after multiple attempts spanning a day, it too finally was built correctly.
Now the story only get a little stranger. We just found out yesterday that on Friday the 17th
at 7:45, the approximate time started the aforementioned deployment of the three new publications,
we also had three transaction from a stable and vetted publication send over all changes except for a single status column.
This publication has 12 million rows and is very active, with thousands of changes daily.
, The three rows did not replicate a status change from a 5 to a 6.
We verified that the status was in fact 6 on the publisher, and
5 on both subscribers, yet no messages or errors. All the other rows successfully updated.
We fixed it by updating the publication from 6 back to 5 then back to 6 again on those specific rows and it worked.
The CPU is low and overall latency is minimal on the distributor.
From all accounts the replication is stable and smooth, but very busy.
The issues above have only recently started. I am not sure where to look for a problem, and to that end, a solution.

I suspect the problem with the new publication/subscriptions not initializing may have been a result of timeouts but it is hard to say for sure. The fact that it eventually succeeded after multiple attempts leads me to believe this. If this happens
again, enable verbose agent logging for the Distribution Agent to see if you are getting query timeouts. Add the parameters
-OutputVerboseLevel 2 -Output C:\TEMP\DistributionAgent.log to the Distribution Agent Run Agent job step, rerun the agent, and collect the log.
If you are getting query timeouts, try increasing the Distribution Agent -QueryTimeOut parameter. The default is 1800 seconds. Try bumping this up to 3600 seconds.
Regarding the three transactions not replicating, inspect MSrepl_errors in the distribution database for the time these transactions occurred and see if any errors occurred.
Brandon Williams (blog |
linkedin)

Snapshot and backup

Hello BW Experts,
Current Scenario:
There is a daily snapshot of the BW system in nite for our Production server. During this they have to stop any jobs / loads running at that time.
Secondly they take a backup every weekend. They stop any jobs / loads during that time also.
Wondering if you could provide ur experiences, that would very great of you..
1) Is snapshot necessary every day?
2) what is the alternative to daily snapshot?
3) what is the best procedure for daily snapshot ?
4) is there a procedure not to stop the loads / jobs during snapshot ?
5) Is backup necessary every weekend?
6) what is the alternative to weekly backup?
7) what is the best procedure for weekly backup ?
8) is there a procedure not to stop the loads / jobs during backup ?
9) is there any doc / paper / link / notes for the snapshots and backups for BW production system.
10)what is the typical time taken for snapshot?
11) what is the typical time taken for backup ?
any does please mail to [email protected]
Thanks,
BWer

Thanks for the valuable info Mimosa.
In our company, they call the snapshot: copy of the production box to the box on the SAN network. The copy is made to the disc. Here the snapshot disc is on RAID 0 and production disc is on RAID 5. They do this every night.
In our company backup is : taking copy to the tape. they do this every weekend.
Its interesting that they do the 'split mirror on-line backup' daily during system is available to all users & jobs. Wondering if you have any details of this backup. What is the procedure called. What level is this copy done, on the database level, network functionality or sap functionality.....?
Suggestions appreciated.
Thanks,
BWer

How to Export Snapshots and Materlized View in Oracle 9i

Hi,
How to Export Snapshots and Materlized View in Oracle 9i .
I require to Migrate from 9i to 10g with either Export or Script.
Please help

Using exp-imp for snapshots generally causes problems, at least for me. I would prefer taking their creation scripts and running them on the new database.
By the way, what do you mean by "migrate from 9i to 10g"? Are you trying to create the same snapshots in another (10g) database or are you trying to upgrade your 9i database to 10g? If it is the latter then you can just upgrade the database automatically with the upgrade assistant or manually using upgrade scripts.

ZFS snapshot and SCP

Similar Messages

Maybe you are looking for