Backup / Recovery of J.D. Edwards

[Michael L.]

Hello List,

We are an iseries 400 shop and we have seven partitions. Prod, Prod Web, Prod Failover/ Prod failover Web (both used for Disaster Recovery) PY, DV and QA. The reason for this post is we want to re-evaluate what we back up, how often we back, and the partitions we backup.

Currently we backup *ALLUSR (100% of all user data) on all partitions 6 days a week. We backup *SAVSYS, *IBM, *ALLUSR, *ALLDLO and *LINK once a week on all partitions (Full backup).

Not considering what platform you run J.D. Edwards on, what is your strategy for backing up many ‘boxes’? Do you care about ‘backing up’ PY and/or any custom environments/path codes and if so do you ‘back them up’ daily, weekly or other or do you not back them up at all and just prefer to manually recreate them in a failover situation?

Were thinking that we don’t need to backup all ‘boxes’ seven days a week.

Thanks in advance for sharing.

Michael
J.D. Edwards 8.11 SP1, TR 8.98.3.3, OS/400 V7R1

 

[MagarG]

Wow, that's a lot of partitions. We're a smaller shop so we have PS, DV, PY, and PD on our Production LPAR. Our Webserver/JAS is not separated out. Our Test LPAR has the same but is the starting point for laying down new tools releases. Our Production box gets a full backup every night. Our Test LPAR will get a backup once it gets a major system update, say CUM, ESUs, other PTFs or an EnterpriseOne Tools Release.

 

[jean_driscoll]

It depends on how often information is changed within an environment and how costly it would be to recover a lost item. A development environment is probably changing daily. How many developers do you have? It is a good idea to make agreements with management and users as to how often data and path code needs to be backed up.