-
-
Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.
Archive a particular directory
- Thread starter jonas
- Start date
Jonas,
If you want to archive all the directories under "home" .
The following command line would be:
archive -subdir=yes "/home/*"
You can use the Windows scheduler to issue the above command. The downside is that the TSM client ID and password would be expose. Unless you have "passwordaccess generate" set in the dsm.opt file.
If you do use the Windows scheduler, trobleshooting of the schedule will be more difficult since the error message are not log in the dsmsched.log . If you want to see messages in the dsmsched.log, need to use the scheduler in the TSM server.
Since you want to run a schedule.
In the dsm.opt file, need to have the parameter "passwordaccess generate."
The client need to be stop and restarted, this will cause the client to prompt for a password. Once the password is enter, the password is now encrypted and you should not be prompted for a password.
To set up a schedule, simplest way to do this is with the TSM Server Web Admin.
Command line wise:
define schedule standard archive
description="Archive of c:home*"
action=archive
objects="c:home*"
startdate=11/11/2001 starttime=01:00
duration=2 durunits=hours period=1
perunits=months dayofweek=sunday
For more information about the syntax you can, on the TSM server you can type
help define schedule or look up the command in the TSM Reference Manual.
Once the schedul is define. The the schdeule need to be assocate with the node.
This is THE MOST COMMON step skipped!
deefine association <domain name> <schedule name> <node name>
To verify what node is associated with the schedule:
query association <domain name> <schedule name>
This will give a listing of what node(s) are associated with the schedule.
Sorry for being long wind!
Sias :-o
If you want to archive all the directories under "home" .
The following command line would be:
archive -subdir=yes "/home/*"
You can use the Windows scheduler to issue the above command. The downside is that the TSM client ID and password would be expose. Unless you have "passwordaccess generate" set in the dsm.opt file.
If you do use the Windows scheduler, trobleshooting of the schedule will be more difficult since the error message are not log in the dsmsched.log . If you want to see messages in the dsmsched.log, need to use the scheduler in the TSM server.
Since you want to run a schedule.
In the dsm.opt file, need to have the parameter "passwordaccess generate."
The client need to be stop and restarted, this will cause the client to prompt for a password. Once the password is enter, the password is now encrypted and you should not be prompted for a password.
To set up a schedule, simplest way to do this is with the TSM Server Web Admin.
Command line wise:
define schedule standard archive
description="Archive of c:home*"
action=archive
objects="c:home*"
startdate=11/11/2001 starttime=01:00
duration=2 durunits=hours period=1
perunits=months dayofweek=sunday
For more information about the syntax you can, on the TSM server you can type
help define schedule or look up the command in the TSM Reference Manual.
Once the schedul is define. The the schdeule need to be assocate with the node.
This is THE MOST COMMON step skipped!
deefine association <domain name> <schedule name> <node name>
To verify what node is associated with the schedule:
query association <domain name> <schedule name>
This will give a listing of what node(s) are associated with the schedule.
Sorry for being long wind!
Sias :-o
Jonas,
If you want to archive all the directories under "home" .
The following command line would be:
archive -subdir=yes "/home/*"
Since you want to run a schedule.
In the dsm.opt file, need to have the parameter "passwordaccess generate."
The client need to be stop and restarted, this will cause the client to prompt for a password. Once the password is enter, the password is now encrypted and you should not be prompted for a password.
To set up a schedule, simplest way to do this is with the TSM Server Web Admin.
Command line wise:
define schedule standard archive
description="Archive of c:\home\*"
action=archive
objects="c:\home\*"
startdate=11/11/2001 starttime=01:00
duration=2 durunits=hours period=1
perunits=months dayofweek=sunday
For more information about the syntax you can, on the TSM server you can type
help define schedule or look up the command in the TSM Reference Manual.
Once the schedul is define. The the schdeule need to be assocate with the node.
This is THE MOST COMMON step skipped!
deefine association <domain name> <schedule name> <node name>
To verify what node is associated with the schedule:
query association <domain name> <schedule name>
This will give a listing of what node(s) are associated with the schedule.
Sorry for being long wind!
Sias
If you want to archive all the directories under "home" .
The following command line would be:
archive -subdir=yes "/home/*"
Since you want to run a schedule.
In the dsm.opt file, need to have the parameter "passwordaccess generate."
The client need to be stop and restarted, this will cause the client to prompt for a password. Once the password is enter, the password is now encrypted and you should not be prompted for a password.
To set up a schedule, simplest way to do this is with the TSM Server Web Admin.
Command line wise:
define schedule standard archive
description="Archive of c:\home\*"
action=archive
objects="c:\home\*"
startdate=11/11/2001 starttime=01:00
duration=2 durunits=hours period=1
perunits=months dayofweek=sunday
For more information about the syntax you can, on the TSM server you can type
help define schedule or look up the command in the TSM Reference Manual.
Once the schedul is define. The the schdeule need to be assocate with the node.
This is THE MOST COMMON step skipped!
deefine association <domain name> <schedule name> <node name>
To verify what node is associated with the schedule:
query association <domain name> <schedule name>
This will give a listing of what node(s) are associated with the schedule.
Sorry for being long wind!
Sias
Jonas,
If you want to archive all the directories under "home" .
The following command line would be:
archive -subdir=yes "/home/*"
Since you want to run a schedule.
In the dsm.opt file, need to have the parameter "passwordaccess generate."
The client need to be stop and restarted, this will cause the client to prompt for a password. Once the password is enter, the password is now encrypted and you should not be prompted for a password.
To set up a schedule, simplest way to do this is with the TSM Server Web Admin.
Command line wise:
define schedule standard archive
description="Archive of c:\home\*"
action=archive
objects="c:\home\*"
startdate=11/11/2001 starttime=01:00
duration=2 durunits=hours period=1
perunits=months dayofweek=sunday
For more information about the syntax you can, on the TSM server you can type
help define schedule or look up the command in the TSM Reference Manual.
Once the schedul is define. The the schdeule need to be assocate with the node.
This is THE MOST COMMON step skipped!
deefine association <domain name> <schedule name> <node name>
To verify what node is associated with the schedule:
query association <domain name> <schedule name>
This will give a listing of what node(s) are associated with the schedule.
Sorry for being long wind!
Sias
If you want to archive all the directories under "home" .
The following command line would be:
archive -subdir=yes "/home/*"
Since you want to run a schedule.
In the dsm.opt file, need to have the parameter "passwordaccess generate."
The client need to be stop and restarted, this will cause the client to prompt for a password. Once the password is enter, the password is now encrypted and you should not be prompted for a password.
To set up a schedule, simplest way to do this is with the TSM Server Web Admin.
Command line wise:
define schedule standard archive
description="Archive of c:\home\*"
action=archive
objects="c:\home\*"
startdate=11/11/2001 starttime=01:00
duration=2 durunits=hours period=1
perunits=months dayofweek=sunday
For more information about the syntax you can, on the TSM server you can type
help define schedule or look up the command in the TSM Reference Manual.
Once the schedul is define. The the schdeule need to be assocate with the node.
This is THE MOST COMMON step skipped!
deefine association <domain name> <schedule name> <node name>
To verify what node is associated with the schedule:
query association <domain name> <schedule name>
This will give a listing of what node(s) are associated with the schedule.
Sorry for being long wind!
Sias
Jonas,
If you want to archive all the directories under "home" .
The following command line would be:
archive -subdir=yes "/home/*"
Since you want to run a schedule.
In the dsm.opt file, need to have the parameter "passwordaccess generate."
The client need to be stop and restarted, this will cause the client to prompt for a password. Once the password is enter, the password is now encrypted and you should not be prompted for a password.
To set up a schedule, simplest way to do this is with the TSM Server Web Admin.
Command line wise:
define schedule standard archive
description="Archive of c:\home\*"
action=archive
objects="c:\home\*"
startdate=11/11/2001 starttime=01:00
duration=2 durunits=hours period=1
perunits=months dayofweek=sunday
For more information about the syntax you can, on the TSM server you can type
help define schedule or look up the command in the TSM Reference Manual.
Once the schedul is define. The the schdeule need to be assocate with the node.
This is THE MOST COMMON step skipped!
deefine association <domain name> <schedule name> <node name>
To verify what node is associated with the schedule:
query association <domain name> <schedule name>
This will give a listing of what node(s) are associated with the schedule.
Sorry for being long wind!
Sias
If you want to archive all the directories under "home" .
The following command line would be:
archive -subdir=yes "/home/*"
Since you want to run a schedule.
In the dsm.opt file, need to have the parameter "passwordaccess generate."
The client need to be stop and restarted, this will cause the client to prompt for a password. Once the password is enter, the password is now encrypted and you should not be prompted for a password.
To set up a schedule, simplest way to do this is with the TSM Server Web Admin.
Command line wise:
define schedule standard archive
description="Archive of c:\home\*"
action=archive
objects="c:\home\*"
startdate=11/11/2001 starttime=01:00
duration=2 durunits=hours period=1
perunits=months dayofweek=sunday
For more information about the syntax you can, on the TSM server you can type
help define schedule or look up the command in the TSM Reference Manual.
Once the schedul is define. The the schdeule need to be assocate with the node.
This is THE MOST COMMON step skipped!
deefine association <domain name> <schedule name> <node name>
To verify what node is associated with the schedule:
query association <domain name> <schedule name>
This will give a listing of what node(s) are associated with the schedule.
Sorry for being long wind!
Sias
Jonas,
If you want to archive all the directories under "home" .
The following command line would be:
archive -subdir=yes "/home/*"
Since you want to run a schedule.
In the dsm.opt file, need to have the parameter "passwordaccess generate."
The client need to be stop and restarted, this will cause the client to prompt for a password. Once the password is enter, the password is now encrypted and you should not be prompted for a password.
To set up a schedule, simplest way to do this is with the TSM Server Web Admin.
Command line wise:
define schedule standard archive
description="Archive of c:\home\*"
action=archive
objects="c:\home\*"
startdate=11/11/2001 starttime=01:00
duration=2 durunits=hours period=1
perunits=months dayofweek=sunday
For more information about the syntax you can, on the TSM server you can type
help define schedule or look up the command in the TSM Reference Manual.
Once the schedul is define. The the schdeule need to be assocate with the node.
This is THE MOST COMMON step skipped!
deefine association <domain name> <schedule name> <node name>
To verify what node is associated with the schedule:
query association <domain name> <schedule name>
This will give a listing of what node(s) are associated with the schedule.
Sorry for being long wind!
Sias
If you want to archive all the directories under "home" .
The following command line would be:
archive -subdir=yes "/home/*"
Since you want to run a schedule.
In the dsm.opt file, need to have the parameter "passwordaccess generate."
The client need to be stop and restarted, this will cause the client to prompt for a password. Once the password is enter, the password is now encrypted and you should not be prompted for a password.
To set up a schedule, simplest way to do this is with the TSM Server Web Admin.
Command line wise:
define schedule standard archive
description="Archive of c:\home\*"
action=archive
objects="c:\home\*"
startdate=11/11/2001 starttime=01:00
duration=2 durunits=hours period=1
perunits=months dayofweek=sunday
For more information about the syntax you can, on the TSM server you can type
help define schedule or look up the command in the TSM Reference Manual.
Once the schedul is define. The the schdeule need to be assocate with the node.
This is THE MOST COMMON step skipped!
deefine association <domain name> <schedule name> <node name>
To verify what node is associated with the schedule:
query association <domain name> <schedule name>
This will give a listing of what node(s) are associated with the schedule.
Sorry for being long wind!
Sias
