QuicksearchDisclaimerThe individual owning this blog works for Oracle in Germany. The opinions expressed here are his own, are not necessarily reviewed in advance by anyone but the individual author, and neither Oracle nor any other party necessarily agrees with them.
|
< Less known Solaris Features: Point-in-time copy with AVS - Part 8: Working with point-in-time copies | Less known Solaris Features: Point-in-time copy with AVS - Part 10: Administration >
Less known Solaris Features: Point-in-time copy with AVS - Part 9: Disaster recoverySunday, April 27. 2008Comments
Display comments as
(Linear | Threaded)
Hi there, good articles on point in time copy, we use it ourselves on a 1TB database.
I've been experimenting with restores in a test environment recently, updating the master volume, and I'm finding that I have to wait for the operatin to complete (iiadm -g xxx -w) in order to get a good version of the data back. Underlying data is an Oracle database. Your example above does not include a wait for the reverse sync to complete, but then as the volume is tiny perhaps its not an issue. |
+1The LKSF bookThe book with the consolidated Less known Solaris Tutorials is available for download here
Web 2.0Contact
Networking xing.com My photos Buttons![]() This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Germany License
![]() ![]() ![]() Blog AdministrationDonateOkay, okay ... as several people have asked for it ... but you know my opinion.
|
Okay, the next installment of the "Less known Solaris Features" series is online. This time i will discuss the feature Point in time copies with AVS. As i have to go through some theory at first, itīs a quite long tutorial. Itīs the longest so far. Point-
Tracked: Apr 27, 11:10