Re: "backup stgpool" command
1997-06-11 17:16:21
Bob,
Typically, a tape pool is the type of pool that gets copied by 'backup
stgpool'. If a node is being backed up, the data is probably going to
the disk pool, so, no, the files would not even be considered for
copying. This is not a problem though. Think of 'backup stgpool' as an
ongoing process. Tomorrow, after the files migrate to the tape pool,
they WILL be copied. And even if some files were in-flight to the tape
pool being backed up and (due to internal logic) they were not copied -
rest assured they would be at the next 'backup stgpool'.
Ron Clendenny
Callaway Nuclear Plant
Fulton, Missouri
<rdclendenny AT cal.ue DOT com>
> -----Original Message-----
> From: Siska, Bob [SMTP:BSISKA AT NCS DOT COM]
> Sent: Wednesday, June 11, 1997 4:45 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: "backup stgpool" command
>
> How does the "backup stgpool" command work internally? In what
> sequence does
> it select data for copying? Will it include client backups that are
> done
> while the "backup stgpool" is running?
> For example, if FileA from Node1 has already been copied, and Node1
> backs up
> FileA again while the "backup stgpool" is still running, is FileA
> copied
> again (the newer version)?
> Is it any problem if nodes are backed up while the "backup stgpool" is
> running? It seems to me that the major problem would be if the "backup
> stgpool" finished while a node was being backed up.
> What do you folks think?
>
> Bob Siska
> National Computer Systems
> Iowa City IA
> Bob_Siska AT ncs DOT com
> ----------
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: "backup stgpool" command,
Clendenny, Ronald D. <=
|
|
|