You might consider issuing a sync call in your scripts before splitting off
a mirror. You do not want to miss any dirty block in the I/O buffer cache
that have not made it to the disk storage. If the mirror split process
already contains a sync, then it will take little additional time as there
If you are truly 24x7 then the best way in my opinion would be to mirror
- or better yet - triple mirror the disks.
Then, using dbpause to pause, split one of the mirrors off, dbresume and
then mount the split disk for backup separately.
The triple mirror will then mean you still have two sets
Jeff,
We also are a 24/7 shop and we use Tivoli Storage Manager and just
back up Unidata hot. What happens is that some very active files will have
errors when restored and we simply run fixfile, fixgroup, etc to throw out
the incomplete records. This is not perfect, but gets us 99% of
Your query got me curious so I went to our DBA to ask. We have a live
system, a fallback system and a development system. 3:00 AM was
determined to be the time with the lowest volume of activity. So at that
time we do a Unix system copy of the file systems from the live system to
the
Jeff -
The answer to that question is rooted in the backup methodology you are
employing. If, for example, you are running on EMC, you can pause the
database long enough to split off a BCV, then resume the database, and
perform your backup from the copy you split off. The SHARK offers Flash
Copy,
We are using Veritas NetBackup. What we do is kick off the users, do a
disk to disk with Veritas, process nightly (approx 15 minutes of
exclusive system use), then allow users to login. After that we
duplicated the diskbackup to tape.
Our files that are backed up are only about 4.5gb. So, it
Hi,
For starters, you might check the features of your AIX filesystem. Does it have
any kind of snapshot feature? If it does, you might only need to dbpause
while the snapshot command executes.
On DEC Tru64, we use the Advanced filesystem (AdvFS). It has a awesome
feature called clone
Then, using dbpause to pause, split one of the mirrors off, dbresume and
then mount the split disk for backup separately.
Beware! Unless your application makes full use of transaction processing,
dbpause may well split in the middle of a business transaction. If you were,
for example, moving
] On Behalf Of Robert Paterson
Sent: Friday, January 06, 2006 9:04 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Backup, dbpause 24/7 operation
If you are truly 24x7 then the best way in my opinion would be to mirror
- or better yet - triple mirror the disks.
Then, using dbpause to pause
We do a disk-to-disk-to-tape backup to minimize the amount of quiet time
required from the live data files, and we schedule the backup to coincide
with the workers' scheduled break.
Michael Golden
Unique Fabricating Inc
---
u2-users mailing list
u2-users@listserver.u2ug.org
To
We only DB Pause the system long enough to sync up a parallel copy of the
database on our SAN. The parallel copy then gets unmounted off the
production server. It is mounted on the backup up server and a tape backup
is done. You need enough disk for another copy of your production files. We
mount
snipAnd if you are using a Windows box, dbpause doe NOT close open
files at the O/S level (at least in UniData it does not)/snip
Just a thought, have you tried the sync command available from
http://www.sysinternals.com to see if that helps?
I appreciate that the open files issue may still be a
Hi,
I will be out of the office on the afternoon of 1/6/06. I will return
to the office on Monday 1/9/06.
I will have limited access to e-mail or voice mail during this time. If
a you need an immediate response to your e-mail please e-mail
[EMAIL PROTECTED]
Thanks and have a great day!
Josh
Hi Jeff,
We use the FlashCopy feature of our FAStT disk array. My script does a
dbpause, then runs a script to activate flashcopy on our FAStT (which takes
a kind of snapshot of the disk, and the array is able to maintain this
snapshot even as the underlying data changes) then dbresume. The
14 matches
Mail list logo