Using istool, I developed a script that accepts the project name as a parameter and backs up the entire project assets. The istool command is called in the script in the following way:
./istool export -domain $was_domname -u $username -p $passwd -archive $archname -datastage "-incdep -base=$DOMAINNAME/$PROJNAME */*.*"
Things I noticed:
- I use double quotation to quote the -datastage parameters instead of the single quotation (as said in the mannual), because I have to pass the domainname and projectname as shell script variables that cannot be quoted in single quotation. And the double quotation work.
- To backup the entire project assets, specify */*.*. It only takes one * and backs up all sub-folders recursively, */*/*.* or more * won't work.
- Note the istool export can only be imported as a whole, you cannot select individual object to import. To be able to select individual object to import, you need to use dsexport or dscmdexport to export, then using dsimport or dscmdimport to import. dsexport is a interactive tool while dscmdexport is a non-interactive tool that you can schedule job with Windows task manager.
- istool exists on both the client and the server, so you can schedule the export as a cron job if your server is on Linux/Unix. But dsexport and dscmdexport only exist on the client.
- dsexport is an interactive tool while dscmdexport is a non-interactive tool that you can use it to schedule job with Windows task manager.
No comments:
Post a Comment