DataStage BackUp process

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
sandeepgs
Participant
Posts: 87
Joined: Wed Jul 02, 2008 12:22 am

DataStage BackUp process

Post by sandeepgs »

Hi All,

I would like to know is there any process that helps to automate the process of taking backup's of the code in datastage and maintain versions.

I started wring a batch script but my installation shows that that there is no command "dscmdexport" to take an export of the code. So I stated exploring option with "IBM Information Server manager".

As I am using "IBM Information Server manager" console to create and manage versions manaually within the repository itself.

I have two questions:
1. Is there any command that datastage supports to take backup's
2. Can we schedule the process od taking the backups with in the tool itself if not batch script.

Thanks for your response.

Regards,
sandeep.
rohitagarwal15
Participant
Posts: 102
Joined: Thu Sep 17, 2009 1:23 am

Re: DataStage BackUp process

Post by rohitagarwal15 »

Try using "dscc.exe" command. You can find it where your Datastage clients are instlaled, location like "C:\IBM\InformationServer\Clients\Classic"
Rohit
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

dscmdexport is available on client machine and not on server machine and should be executed from the machine where client is installed. Since you are on Windows server, you can very well have client installed there as well. Or you can explore istools.
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

The 'new' utility in the 8.x world is istool. Andy posted a nice overview of the syntax here.
-craig

"You can never have too many knives" -- Logan Nine Fingers
asorrell
Posts: 1707
Joined: Fri Apr 04, 2003 2:00 pm
Location: Colleyville, Texas

Post by asorrell »

I'd recommend istool for several reasons.

1) It is a server-based tool so it is significantly faster than using client-based backups.
2) It can backup more than just jobs (important if you are using some of the other products in the suite)
3) It can be automated via shell-script (or batch file), then scheduled

The only drawback is the lack of granularity on an import. It means that you must import the entire project at once. To get a single job you need to import the project into a temporary location then copy the job(s) you need to the correct project.
Andy Sorrell
Certified DataStage Consultant
IBM Analytics Champion 2009 - 2020
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Not to be confused with iStool. And yes, it's perfectly safe to click on the link. I swear. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
sandeepgs
Participant
Posts: 87
Joined: Wed Jul 02, 2008 12:22 am

Post by sandeepgs »

Hi Chulett,

Thanks for your response.

Yes, I have tried the "istool" command line interface and the testing is successful. Andy had defined in very detail the use of command line interface.

One more point is that as I go understood that "IBM Information Server Manager" is designed to be as a deployment tool which can used as a version control tool as well.

I tried digging through all the IBM materials and found that it can only be used as a version control tool only on integration with CVS/ IBM Rational ClearCase even though it maintains versions in Packages.

So can you confirm my below understanding.

1. DataStage doesn't have a configuration management tool as what we have Informatica.
Ex: In Informatica I can check-in and check-out the code and on check-out it will not allow any other users to modify the code until it is checked back in. This is the same functionality as what we have in configuration management tools Ex: CCC harvest etc.
2. Using Information Server Management tool creating different builds will serve the purpose of creating versions but the versions are created Metadata repository which will in turn eat up entire metadata repository space and can result in degraded server performance.
3. There is no way we can automate the backup process apart from creating a script and scheduling it.

So what will be the recommendation to use separate configuration management tool if at all i have to maintain versions and integrate as what IBM document defines.

Thanks & Regards,
Sandeep
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

What exact version are you on?
-craig

"You can never have too many knives" -- Logan Nine Fingers
sandeepgs
Participant
Posts: 87
Joined: Wed Jul 02, 2008 12:22 am

Post by sandeepgs »

Hi chulett,

I am using Version 9.1.

Regards,
Sandeep.
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

I would not want to check in and out a full export of the project. You need to export one job at a time. You can script this on the client but you need dsjob to get a list of job names then export these one at a time. You can easily do a check in. Check in on most of these will ignore it if it has not changed.
Mamu Kim
sandeepgs
Participant
Posts: 87
Joined: Wed Jul 02, 2008 12:22 am

Post by sandeepgs »

Thanks for reply,

For writing a script, I got the answer as to use "istool".

But I would more of like to know whether I can use IBM Information Server Management tool as a configuration management tool.

If so, then do I need any third party tool like IBM Rational ClearCase etc.,

Thanks & Regards,
Sandeep
asorrell
Posts: 1707
Joined: Fri Apr 04, 2003 2:00 pm
Location: Colleyville, Texas

Post by asorrell »

Sandeep, I find this thread a bit confusing because you keep referring to backups and then switching to talk about source code control products.

Though they both are used to keep copies of source code (or jobs in this case), they are usually not treated as interchangeable or inter-operable products.

I am not aware of any company that depends on source-code control systems for their backups. Though sccs can be used to regenerate one or two items, there are too many drawbacks to depend on them for full system or project restores.

If you have questions on both areas, please split out the source code control discussion to a separate thread and continue discussing backups here.
Andy Sorrell
Certified DataStage Consultant
IBM Analytics Champion 2009 - 2020
Post Reply