Timothy,
Try to use exactly the same syntax as the one used by the GUI :
GENERATE BACKUPSET DOCAPPS "weekly docapp" 5 DEVCLASS=3592CLASS
NAMETYPE=FSID DESCRIPTION="weekly docapparch" RETENTION=1 WAIT=YES
Note the use of "5" and "NAMETYPE=FSID" : in that case you're working
with FSID to tell TSM which filespace to use
If you'd like to use the full filespace name, it should be
\\DOCAPPS\POA.
Do yourself a favor and type "H GENERATE BACKUPSET" on TSM admin command
line !
Cheers .
Arnaud
************************************************************************
******
Panalpina Management Ltd., Basle, Switzerland,
CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion AT panalpina DOT com
************************************************************************
******
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Timothy Hughes
Sent: Friday, 20 January, 2006 15:25
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Another backup set question
Hello,
I am still trying to set up a Admin Schedule to generate a backup set.
I need to one have a backup set for one filespace/volume for a client.
The other day I was able to generate a backup set that worked, But I did
it manually by going into the GUI. I clicked on the clients File Space
and used the drop down menu. But when I try to schedule the backup set
to run using Admin Schedule Commands it doesn't work. I keep getting no
filespaces to process errors. When I used the GUI Drop down box to
generate a backup set it also put the FSID # in.
Why can't I duplicate that using a Admin Schedule command?
I read that a backup set could be created using the using just the
filespace name. Am I missing something? Is anyone else using a backup
set to archive a volume/filespace for a client's data?
All responses are welcome, Thanks in advance!
This worked (Manually generated backup set by clicking on clients file
space and using the drop down box to create a backup set.
ANR2017I Administrator XXXXXX issued command: GENERATE BACKUPSET
DOCAPPS "weekly docapp" 5 DEVCLASS=3592CLASS
RETENTION=1 SCRATCH=YES DESCRIPTION="weekly docapparch"
WAIT=NO NAMETYPE=FSID (SESSION: 129388)
01/18/06 13:28:41 ANR2017I Administrator xxxxxx issued command:
GENERATE
BACKUPSET DOCAPPS docappweeklyarch 5 DEVCLASS=3592CLASS
RETENTION=1 SCRATCH=YES DESCRIPTION="weekly docapparch"
WAIT=NO NAMETYPE=FSID (SESSION: 129389)
01/18/06 13:28:41 ANR3500I Backup set for node DOCAPPS as
DOCAPPWEEKLYARCH.405269859 being generated.
01/18/06 15:25:48 ANR3501I Backup set for DOCAPPS as
DOCAPPWEEKLYARCH.40526 9859 completed successfully - processed 104362
files.
This did not work (these were generated by setting up a specific time to
run using a Admin Schedule command)
ANR2017I Administrator XXXXX issued command: GENERATE BACKUPSET
DOCAPPS DOCAPPOARCH poa DEVCLASS=3592CLASS
RETENTION=1 SCRATCH=YES DESCRIPTION=docbackupset WAIT=NO
01/18/06 13:13:42 ANR3508W Generation of backup set for DOCAPPS as
DOCAPPOARCH.405269545 failed - no filespaces to process.
(SESSION: 128945, PROCESS: 813)
ANR2017I Administrator OTSHUGH issued command: GENERATE BACKUPSET
DOCAPPS docapparch "DOCAPPS\POA " DEVCLASS=3592CLASS SCRATCH=YES
DESCRIPTION=docarch WAIT=NO (SESSION:
01/18/06 13:17:54 ANR3508W Generation of backup set for DOCAPPS as
DOCAPPARCH.405269549 failed - no filespaces to process.
(SESSION: 129071, PROCESS: 815)
TSM 5.3.2.1
Novell TSM client 5.2.2
Netware OS 6.5
|