Stefan, what you say is correct, but Rodney was asking for the CLI
equivalent of "hand-picking" folders from the GUI. My suggestion is the
closest analogy without the complexities of include/exclude. Yes, you
could use exclude.dir to avoid traversing undesired directories, and there
is nothing wrong with that; I was merely offering an alternative. But
using exclude statements is no less risky. Consider that ANY time you use
exclude (or exclude.dir) on ANY file system (NAS or otherwise) on ANY
operating system, you run the same risk, which is that someone could put
critical data in a directory that is excluded from backup. Whether you are
changing a backup script or changing an include/exclude list, the
possibilities for error still exist. Procedures and policies for data
placement and data backup must be in place to minimize that risk.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 05/13/2004
07:21:23:
> Andi, you have always to change your scripts if there are new
directories on
> the NAS system...
> So the risk is high to miss one.
> Kind Regards, Stefan Holzwarth
>
> > -----Ursprüngliche Nachricht-----
> > Von: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
> > Gesendet: Donnerstag, 13. Mai 2004 15:51
> > An: ADSM-L AT VM.MARIST DOT EDU
> > Betreff: Re: AW: Command line equivalent for GUI
> >
> >
> > If I understand this correctly, include/exclude isn't really the issue
> > since from the GUI you were picking the specific
> > subdirectories that you
> > wanted to process. Why not simply do the same thing from the CLI?
> >
> > For example, if from the GUI you were selecting directories
> > C:\Some Dir,
> > D:\MyDir, and D:\work\datafiles, then why not just do this?
> >
> > dsmc i "c:\some dir\*" d:\mydir\ d:\work\datafiles\ -subdir=yes
> >
> > Note that the asterisk is required in the first example because the
> > embedded space in the file specification necessitates using quotation
> > marks. If you don't care why, then you can skip the rest of this. For
> > those who want to know, it has to do with how the Windows command
> > processor parses quotes, backslashes, and escape characters.
> >
> > If I had used a command like this, without the asterisk:
> >
> > dsmc i "c:\some dir\" d:\mydir\ d:\work\datafiles\ -subdir=yes
> >
> > Then the Windows command processor would have treated the ending
> > slash-quote combination in "c:\some dir\" as an embedded
> > quotation mark
> > rather than a delimiter, passing the following arguments to the TSM
> > client:
> >
> > arg1: i
> > arg2: c:\some dir" d:\mydir\ d:\work\datafiles\ -subdir=yes
> >
> > which would make the client think that arg2 was the entire file
> > specifications, rather than three file specs and an option.
> > What we really
> > want to pass to the client is:
> >
> > arg1: i
> > arg2: c:\some dir
> > arg3: d:\mydir\
> > arg4: d:\work\datafiles\
> > arg5: -subdir=yes
> >
> > If this doesn't make sense, don't worry about it.... just use
> > the asterisk
> > as I showed above and it should work fine.
> >
> > Regards,
> >
> > Andy
> >
> > Andy Raibeck
> > IBM Software Group
> > Tivoli Storage Manager Client Development
> > Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
> > Internet e-mail: storman AT us.ibm DOT com
> >
> > The only dumb question is the one that goes unasked.
> > The command line is your friend.
> > "Good enough" is the enemy of excellence.
> >
> > > > > Hi,
> > > > >
> > > > > I'm backing up a NAS device with 1M+ files. As
> > > > other
> > > > > posts indicate, the only way to get any
> > > > performance in
> > > > > this setup is to split the file backups across
> > > > > multiple sessions. In my case I have two backup
> > > > hosts,
> > > > > each running two backup streams. I can start each
> > > > of
> > > > > the four backup streams using the GUI and
> > > > selecting
> > > > > appropriate folders. A kind of load balancing is
> > > > > achieved by picking an appropriate mix of folders
> > > > for
> > > > > each backup stream. Each backup runs in a few
> > > > hours
> > > > > each stream processing a subset of the 1M files.
> > > > >
> > > > > My problem is I can't figure out how to accomplish
> > > > the
> > > > > same thing using the command line and associated
> > > > > include/excludes. I'd like to schedule the four
> > > > > streams to run the same way, each with an
> > > > appropriate
> > > > > set of folders/files to process. It would be
> > > > wonderful
> > > > > if I could somehow see how this is accomplished
> > > > via
> > > > > the GUI, as I can't seem to get the same behavior
> > > > > using commands. Each combination I have tried
> > > > always
> > > > > results in each backup stream processing/scanning
> > > > all
> > > > > of the 1M files! This takes way too many hours and
> > > > > doesn't provide the same parallel behavior I get
> > > > when
> > > > > running the GUI. How can I limit each stream to
> > > > > processes only the files/folders I desire without
> > > > > scanning everything; the same way as the GUI seems
> > > > to
> > > > > function?
> > > > >
> > > > > Thanks for your help,
> > > > > Rodney Hroblak
> > > > > ADP
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > __________________________________
> > > > > Do you Yahoo!?
> > > > > Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> > > > >
> > > >
> > > http://movies.yahoo.com/showtimes/movie?mid=1808405861
> > > > >
> > >
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> > > http://movies.yahoo.com/showtimes/movie?mid=1808405861
> >
|
