Site kills NOF

[Alan]

Hi, any tips for recovering a site?

Windows ( XP ) crashed whilst I was editing a site. Now I am unable to open
that site as NOF says "recovering NOD ..." but then NOF crashes completely.
I am able to open other sites ok.
I've tried going to a backup ( renamed site.nod.bak ) but NOF still says the
NOD is bad and needs to recover but then crashes.

Its as though the main NOF panel has a different idea of the nod status and
seems to be remembering the crash rather than looking at the actual nod
itself. I've gone back through all my nod backups now and they all exhibit
the same problem. I can't believe that everyone was bad!

Cheers
Alan

[Alan]

Sorted it .... Found that if I deleted the recovery directory then the
backup nod that previously had caused NOF to crash now worked perfectly.
Weird, but happy again and only a weeks work down the pan.

Cheers
Alan


Alan wrote:

> Hi, any tips for recovering a site?
>
> Windows ( XP ) crashed whilst I was editing a site. Now I am unable to
> open that site as NOF says "recovering NOD ..." but then NOF crashes
> completely. I am able to open other sites ok.
> I've tried going to a backup ( renamed site.nod.bak ) but NOF still says
> the NOD is bad and needs to recover but then crashes.
>
> Its as though the main NOF panel has a different idea of the nod status
> and seems to be remembering the crash rather than looking at the actual
> nod itself. I've gone back through all my nod backups now and they all
> exhibit
> the same problem. I can't believe that everyone was bad!
>
> Cheers
> Alan

[Richard Nowak]

This has been said before but people keep coming here for help when they
can't recover their work.

So here are the tips you asked for:

1) Do not rely on the backup NOD file. The NOD file does not contain all the
data you will need to breathe life back into a GONE site. In this case, you
lucked out.

2) Save your work as a Template at work/home and offsite. Save a copy on the
server (most you can lose is a days worth of work in most cases). Backup the
templates on quality write-once DVDs (you will be long gone before they
become unreadable).

3) Do it often. Losing a weeks worth of work isn't acceptable for most
people. No one here will be able to help you find a GONE site.

4) Hard disks fail and they will fail at the worst possible moment in time.
Pretty much guaranteed.

Rich


"Alan" <ajwebonlyNO@googleSPAMmail.com> wrote in message
news:hlbcut$u24$1@DailyPlanet.news.netobjects.com. ..
> Sorted it .... Found that if I deleted the recovery directory then the
> backup nod that previously had caused NOF to crash now worked perfectly.
> Weird, but happy again and only a weeks work down the pan.
>
> Cheers
> Alan
>
>
> Alan wrote:
>
>> Hi, any tips for recovering a site?
>>
>> Windows ( XP ) crashed whilst I was editing a site. Now I am unable to
>> open that site as NOF says "recovering NOD ..." but then NOF crashes
>> completely. I am able to open other sites ok.
>> I've tried going to a backup ( renamed site.nod.bak ) but NOF still says
>> the NOD is bad and needs to recover but then crashes.
>>
>> Its as though the main NOF panel has a different idea of the nod status
>> and seems to be remembering the crash rather than looking at the actual
>> nod itself. I've gone back through all my nod backups now and they all
>> exhibit
>> the same problem. I can't believe that everyone was bad!
>>
>> Cheers
>> Alan
>

[testcenter]

I always backup the whole directory (harddisk) from the site before I
make some (major) changes.

Frank



Op 15-2-2010 19:53, Richard Nowak schreef:
> This has been said before but people keep coming here for help when they
> can't recover their work.
>
> So here are the tips you asked for:
>
> 1) Do not rely on the backup NOD file. The NOD file does not contain all the
> data you will need to breathe life back into a GONE site. In this case, you
> lucked out.
>
> 2) Save your work as a Template at work/home and offsite. Save a copy on the
> server (most you can lose is a days worth of work in most cases). Backup the
> templates on quality write-once DVDs (you will be long gone before they
> become unreadable).
>
> 3) Do it often. Losing a weeks worth of work isn't acceptable for most
> people. No one here will be able to help you find a GONE site.
>
> 4) Hard disks fail and they will fail at the worst possible moment in time.
> Pretty much guaranteed.
>
> Rich

[Derek]

On 15/02/2010 19:05, testcenter wrote:
> I always backup the whole directory (harddisk) from the site before I
> make some (major) changes.
>
> Frank
>

Yup. But echoing Richard's points, a template is your friend when the
NOD file you've backed up is broken. Only takes a minute or so even on a
big site, plus it's portable to another PC even with different drive
configurations (e.g. boots from a D: drive and has apps & data on F: -
unlikely, but feasible). Your backed up NOD files generally can't cope
when that happens as the asset paths (amongst others) will be wrong...

It's part of what I like to call 'constructively lazy administration';
put a little bit of effort in now to save a lot later on <g>!

[John Lewis]

I suggest looking at Backup Essential or, better yet, Backup Ultimate.
Install a second hard drive in your desktop, or use a portable hard drive,
that you can dedicate to backups. Backup Essential or Ultimate backs up the
operating system and all your files. So if there is a hard disk failure,
virus, or spyware, you can easily just switch and start your computer from
the backup drive--or restore everything to the primary drive. Nothing is
lost. You can even access individual files and folders from the backup
drive. I indtalled a second hard drive inside my desktop. Now when I start
Windows I have the option to start Windows XP or start from the recovery
disk. You can investigate at the following site:
http://www.cmsproducts.com/products/...k/default.html
"Alan" <ajwebonlyNO@googleSPAMmail.com> wrote in message
news:hlb7e6$rmg$1@DailyPlanet.news.netobjects.com. ..
> Hi, any tips for recovering a site?
>
> Windows ( XP ) crashed whilst I was editing a site. Now I am unable to
> open
> that site as NOF says "recovering NOD ..." but then NOF crashes
> completely.
> I am able to open other sites ok.
> I've tried going to a backup ( renamed site.nod.bak ) but NOF still says
> the
> NOD is bad and needs to recover but then crashes.
>
> Its as though the main NOF panel has a different idea of the nod status
> and
> seems to be remembering the crash rather than looking at the actual nod
> itself. I've gone back through all my nod backups now and they all exhibit
> the same problem. I can't believe that everyone was bad!
>
> Cheers
> Alan

[John Lewis]

Of course, I mean Bounceback Essential and Bounceback Ultimate

"John Lewis" <johnarthurlewis@gmail.com> wrote in message
news:hlcpsk$k83$1@DailyPlanet.news.netobjects.com. ..
>I suggest looking at Backup Essential or, better yet, Backup Ultimate.
>Install a second hard drive in your desktop, or use a portable hard drive,
>that you can dedicate to backups. Backup Essential or Ultimate backs up the
>operating system and all your files. So if there is a hard disk failure,
>virus, or spyware, you can easily just switch and start your computer from
>the backup drive--or restore everything to the primary drive. Nothing is
>lost. You can even access individual files and folders from the backup
>drive. I indtalled a second hard drive inside my desktop. Now when I start
>Windows I have the option to start Windows XP or start from the recovery
>disk. You can investigate at the following site:
>http://www.cmsproducts.com/products/...k/default.html
> "Alan" <ajwebonlyNO@googleSPAMmail.com> wrote in message
> news:hlb7e6$rmg$1@DailyPlanet.news.netobjects.com. ..
>> Hi, any tips for recovering a site?
>>
>> Windows ( XP ) crashed whilst I was editing a site. Now I am unable to
>> open
>> that site as NOF says "recovering NOD ..." but then NOF crashes
>> completely.
>> I am able to open other sites ok.
>> I've tried going to a backup ( renamed site.nod.bak ) but NOF still says
>> the
>> NOD is bad and needs to recover but then crashes.
>>
>> Its as though the main NOF panel has a different idea of the nod status
>> and
>> seems to be remembering the crash rather than looking at the actual nod
>> itself. I've gone back through all my nod backups now and they all
>> exhibit
>> the same problem. I can't believe that everyone was bad!
>>
>> Cheers
>> Alan
>
>

[Alan]

Chaps,
Thanks for all the tips. But the problem wasn't a lack of backups, I had
plenty of those ( albeit no templates - if only there was an api so taking
templates could be automated ). The problem was that NOF didn't like any of
my backups, even old ones I had used before to restore from.

As it turned out the backups weren't bad at all .... it was all down to that
Recovery directory. Now I have no idea what its purpose is, but getting rid
of it made backups that Nof had previously barfed over work again.

Cheers
Alan




Alan wrote:

> Sorted it .... Found that if I deleted the recovery directory then the
> backup nod that previously had caused NOF to crash now worked perfectly.
> Weird, but happy again and only a weeks work down the pan.
>
> Cheers
> Alan
>
>
> Alan wrote:
>
>> Hi, any tips for recovering a site?
>>
>> Windows ( XP ) crashed whilst I was editing a site. Now I am unable to
>> open that site as NOF says "recovering NOD ..." but then NOF crashes
>> completely. I am able to open other sites ok.
>> I've tried going to a backup ( renamed site.nod.bak ) but NOF still says
>> the NOD is bad and needs to recover but then crashes.
>>
>> Its as though the main NOF panel has a different idea of the nod status
>> and seems to be remembering the crash rather than looking at the actual
>> nod itself. I've gone back through all my nod backups now and they all
>> exhibit
>> the same problem. I can't believe that everyone was bad!
>>
>> Cheers
>> Alan

[Twayne]

I'll second this advice.
The backup NODs have their uses but a true backup of the whole website
isn't one of them. It's a bit of a misnomer IMO but in NOF "template" really
means something closer to "package", which means everything, all the files
it needs, to function as a complete site is included in the zip file. A
..nod file is only fully functional if you place it where it was originally
created so that it has access to the rest of the items it needs like Assets,
etc..
For a "gone" site, the misnamed "template" is really what you want to be
able to recreate the site without a lot of work.

HTH,

Twayne





In news:hlc5ga$a7a$1@DailyPlanet.news.netobjects.com,
Richard Nowak <nowak@earthlink.net> typed:
> This has been said before but people keep coming here for help when
> they can't recover their work.
>
> So here are the tips you asked for:
>
> 1) Do not rely on the backup NOD file. The NOD file does not contain
> all the data you will need to breathe life back into a GONE site. In
> this case, you lucked out.
>
> 2) Save your work as a Template at work/home and offsite. Save a copy
> on the server (most you can lose is a days worth of work in most
> cases). Backup the templates on quality write-once DVDs (you will be
> long gone before they become unreadable).
>
> 3) Do it often. Losing a weeks worth of work isn't acceptable for most
> people. No one here will be able to help you find a GONE site.
>
> 4) Hard disks fail and they will fail at the worst possible moment in
> time. Pretty much guaranteed.
>
> Rich
>
>
> "Alan" <ajwebonlyNO@googleSPAMmail.com> wrote in message
> news:hlbcut$u24$1@DailyPlanet.news.netobjects.com. ..
>> Sorted it .... Found that if I deleted the recovery directory then
>> the backup nod that previously had caused NOF to crash now worked
>> perfectly. Weird, but happy again and only a weeks work down the pan.
>>
>> Cheers
>> Alan
>>
>>
>> Alan wrote:
>>
>>> Hi, any tips for recovering a site?
>>>
>>> Windows ( XP ) crashed whilst I was editing a site. Now I am
>>> unable to open that site as NOF says "recovering NOD ..." but then
>>> NOF crashes completely. I am able to open other sites ok.
>>> I've tried going to a backup ( renamed site.nod.bak ) but NOF still
>>> says the NOD is bad and needs to recover but then crashes.
>>>
>>> Its as though the main NOF panel has a different idea of the nod
>>> status and seems to be remembering the crash rather than looking at
>>> the actual nod itself. I've gone back through all my nod backups
>>> now and they all exhibit
>>> the same problem. I can't believe that everyone was bad!
>>>
>>> Cheers
>>> Alan



--
--
Life is the only real counselor; wisdom unfiltered
through personal experience does not become a
part of the moral tissue.