We would like to know about existing development environments. Do you separate the "Development Server" from the "Production Server"? How do you handle the different IP addresses? After I have created a new database should I create "clones", files that have never been recovered and that are up-to-date to protect the pristine nature of my DB. What works for folks and what doesn't? How isolated should the devlopment environment be from the production environment?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Backup Environment and Cloning
- Thread starter rspringf
- Start date
You will probably get different answers from anyone that answers.
I personally will do minor updates to the FM files while they are live.
Things like new fields and major reports or updates I will work out on my system with the files switched back to single user so that no one else can open them. Then I'll install the updates "after hours" - whenever that is in a place that runs 24 a day.
I always keep a copy of my major updates and during my incremental I'll take a copy of the DB after I have done a lot of little changes.
I try to keep my last 2 major updates and last 3 minors. My "live" files back up 4 times a day.
I don't think I answered your question directly - but it's a matter of preference and how comfortable you feel with your setup.
HTH.
Im Steven B Im Steven B
I personally will do minor updates to the FM files while they are live.
Things like new fields and major reports or updates I will work out on my system with the files switched back to single user so that no one else can open them. Then I'll install the updates "after hours" - whenever that is in a place that runs 24 a day.
I always keep a copy of my major updates and during my incremental I'll take a copy of the DB after I have done a lot of little changes.
I try to keep my last 2 major updates and last 3 minors. My "live" files back up 4 times a day.
I don't think I answered your question directly - but it's a matter of preference and how comfortable you feel with your setup.
HTH.
Im Steven B Im Steven B
- Thread starter
- #3
Thank you StevenB for the info.
We do minor changes on the fly.
All major updates occur when the server is not available to the users.
We backup once a night. You mentioned incrementals, have you ever used FMP servers backup facility? Does it have a huge effect on performance? I understand it will suspend the users requests.
We have about 95 databases some containing tens of thousands of records.
Hope to here from others as well. Thanks again Steven.
RGS
We do minor changes on the fly.
All major updates occur when the server is not available to the users.
We backup once a night. You mentioned incrementals, have you ever used FMP servers backup facility? Does it have a huge effect on performance? I understand it will suspend the users requests.
We have about 95 databases some containing tens of thousands of records.
Hope to here from others as well. Thanks again Steven.
RGS
RGS
I use FMP Server for my incrementals. I have found about 3 times during the "normal" day when usage is is low and I scheduled backups for those times. I run an additional backup during the overnight.
This way I'm never more than about 6 hours old in my backup. I had been toying with the idea of scheduling the backups to go to two different locations then I'd have a 6 hour - a 12 hour and 1 day on tape.
I haven't seen or gotten complaints about performance slowing down - I have 35 databases in my solution and thousands of records also.
Hope this helps.
Im Steven B
I use FMP Server for my incrementals. I have found about 3 times during the "normal" day when usage is is low and I scheduled backups for those times. I run an additional backup during the overnight.
This way I'm never more than about 6 hours old in my backup. I had been toying with the idea of scheduling the backups to go to two different locations then I'd have a 6 hour - a 12 hour and 1 day on tape.
I haven't seen or gotten complaints about performance slowing down - I have 35 databases in my solution and thousands of records also.
Hope this helps.
Im Steven B
- Status
Similar threads
- Locked
- Question