It appears that this DWH appliance is based on Linux and that IBM suggests you would do a backup as you would of any other machine which was otherwise Linux based.
Forget what I said... and check THIS. So, you have client only installed and connector towards DB as such is not done by module, but by netezza CLI itself.
No, if DB is there (and after all, it is data warehouse appliance so you have DB), you would need to use Oracle module. save is not an option as save does file system and as such you would not have consistent DB copy. I agree that IBM article is a bit challenging to understand as they state NW version only and no module, bit for DB to be backed up (online that is) you need online module as well.
Would you please explain how would you use NMDA? Because Netazza works in a way that only nzbackup and nzrestore can do backup. And these commands will work TSM, NW, NB and so on given that you specify backup application as valid connector string. That means that nsbazkup/nzrestore are API to DB and stream is passed to client save command. So, how do you see NMDA fitting there? I don't.
ble1
4 Operator
•
14.4K Posts
0
November 19th, 2013 13:00
It appears that this DWH appliance is based on Linux and that IBM suggests you would do a backup as you would of any other machine which was otherwise Linux based.
rjacob1
39 Posts
0
November 19th, 2013 13:00
Hrvoje,
Thanks for confirming that. Do you have any EMC doc that talks about performing Netezza backup?
If I got to backup a DB whats the save command I should be using for Netezza?
ble1
4 Operator
•
14.4K Posts
0
November 19th, 2013 14:00
Forget what I said... and check THIS. So, you have client only installed and connector towards DB as such is not done by module, but by netezza CLI itself.
ble1
4 Operator
•
14.4K Posts
1
November 19th, 2013 14:00
I gave wrong link - see Command-line backup and restore. There is also section for scheduled operations.
ble1
4 Operator
•
14.4K Posts
0
November 19th, 2013 14:00
No, if DB is there (and after all, it is data warehouse appliance so you have DB), you would need to use Oracle module. save is not an option as save does file system and as such you would not have consistent DB copy. I agree that IBM article is a bit challenging to understand as they state NW version only and no module, bit for DB to be backed up (online that is) you need online module as well.
o17Uu33DCF12520
4 Operator
•
1.1K Posts
0
November 19th, 2013 18:00
According to https://support.emc.com/docu34173_NetWorker-Hardware-Compatibility-Guide-.pdf?language=en_US and https://support.emc.com/docu35302_NetWorker-Software-Compatibility-Guide-.pdf?language=en_US and the appliance has been supported by NW directly.
By now the workaround is to back up the database using NMDA. Check the guide for what specific database you are using. https://support.emc.com/docu50645_NetWorker_Module_for_Databases_and_Applications_1.6_Administration_Guide.pdf?language=en_US
ble1
4 Operator
•
14.4K Posts
1
November 19th, 2013 22:00
Hi Kevin,
Would you please explain how would you use NMDA? Because Netazza works in a way that only nzbackup and nzrestore can do backup. And these commands will work TSM, NW, NB and so on given that you specify backup application as valid connector string. That means that nsbazkup/nzrestore are API to DB and stream is passed to client save command. So, how do you see NMDA fitting there? I don't.
Robinson2
10 Posts
1
May 28th, 2014 05:00
I have successfully run Netezza backups using the regular Linux 32 bit client and following the guide that Hrvoje sent a link to from IBM.
Important to follow the steps of configuring the /nz/data/config/backupHostname.txt file
also experienced that the -connectArgs syntax is a bit different to regular NSR syntax, where arguments are separated with ":" instead of ",".
To force backups to go to another backup pool than default the -connectArgs had to be like this:
-connectArgs NSR_SERVER=backuphost1:NSR_DATA_VOLUME_POOL=OtherPool