Backup during development

Rishi

Member
Hi list,
my daily backup during development activities in development environment includes

a. DV7334 ( folder in deployment server)
b. CODV7334 ( CO in enterprise server)
c. OL7334
d. DD7334

Should i include more libraries/Directories in my daily backup apart from the above??

ES - AS400
CO in ES,
DS - W2K

Thanks in advance
Rishi
 
Rishi...

This depends on many variables. Do all developers check in changes to DV
every day? Do any developers utilize the save location (if you have one
set up)? Do any developers NOT check in their items every day? If items
are checked in, then you need to also back up the specific SPEC directory
on the deployment server. If they check anything into other path codes,
you'll need to backup those libraries and subdirectories on the
deployment server as well. If they check into the save location (which
for all intents and purposes to OneWorld/ERP is another path code) you'll
need to back up its libraries and subdirectories. And if developers
don't check in every day, you'll need to make sure you have a backup of
the SPEC directory on the machine they were doing development on,
otherwise, if that machine crashes, or has a package installed on it, all
changes not checked in will be lost. This reason alone is a very good
reason to look into development on a terminal server...one differential
backup a night and all the developers changes are saved!


Regards,

Jim

________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!
 
Jim,
Thanks for the info.. all objects are checked in everyday and no save location.

should i include DV7333,SYS7333, B7333SYS ,SVM7333 libraries in my daily backup during development stage.

thanks & regards
 
Despite the popular belief, the SPEC folders in the pathcodes on the Deployment Server are NEVER updated. Not during check-ins, not even during package builds.

What makes sense to back up on the dep server, though, are the SOURCE and INCLUDE folders - checkin does update those...

Regards,
Alex.
 
Alex...
While true, the spec aren't updated dynamically during check in, if the
intent, as it was in this case, is to be able to restore lost
development, the SPEC directory on the deployment server, in the affected
Path Code should be backed up as these files will be altered by any
package build. If you need to get the system back to a pre-package
state, you had best have a backup of the SPEC directory. I've also found
that specs are updated on the deployment server due to administrative
usage, for instance, R92TAM or R98CRGTL. If you want to ensure safety,
the SPEC directory is updated and its updates can cause issues getting
the system back to a specific state. I've also seen people perform (or
attempt to anyway) check-outs on the deployment server.

Regards,

Jim

________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!
 
You can never have too much backup, but to backup SPEC folders daily is not necessary. These folders can also be easily re-created from Packages, copied from Clients, Planner, etc.

Package builds do not update these folders. In fact, these folders are not supposed to ever be used. The only SPEC folder used on the D/S is in the PLANNER.

Regards,
Alex.
 
Back
Top