when dealing with double copy recalls.

Proper fix by defining a new RECALLJOB_SELECTED2NDCOPY state instead
of hijacking the (deprecated) fileTransactionId.

the files that are stuck on their migration to tape.

  - avoid looping too much in the tapegateway when some file is locked for long
  - improved handling of log messages when the DLFLogs table is too full :
    + do not take all of it in one go
    + use an index as the table may be scattered

only run as part of creation scripts, but in case it is run on
existing databases the existing history will be preserved.

Properly take into account the NS stagertime as lastOpenTime for Repack.
This ensures Repack will work in compatibility mode (stagertime==mtime)
and in the new mode, i.e. Repack operations will always loose with respect
to user operations.

Improved implementation of the draining, so that it starts quick. This included added a new DB job : drainRunner that is independant of the drainManager one

Remove autodelete option from the draining comment. This option was useless, as it was kind of enabled even if not set. The trick was that DB triggers are checking the number of copies of files and were anyway dropping the drained copies, even if it was not done by the tool itself

Improved draining by implementing back pressure on the scheduling (no more than 1000 jobs pending per drainingJob) and ordering of files by importance (no tape and fewer copies on disk first)

4 constraints and index:
    FK_DiskCopy_CastorFile
    FK_CastorFile_FileClass
    I_CastorFile_FileClass
    UN_CastorFile_LKFileName
    NN_CastorFile_LKFileName

    NN_SvcClass_LastEditor
    NN_SvcClass_LastEditionTime

I_SvcClass_GcPolicy

FK_SvcClass_GCPolicy.

NN_SvcClass_GcPolicy.

NN_SvcClass_ForcedFileClass.

constraint for a second time which is not possible and caused the schema
creation script to fail.

creation script to fail:

ALTER TABLE SvcClass ADD CONSTRAINT UN_SvcClass_Name UNIQUE (name);

This includes :
  - merge of d2dtransfer into diskmanagerd
  - drop of the WAITDISKTODISKCOPY state in DiskCopy, and of the diskcopies for ongoing replication in general. Now DiskCopies are only created at the end of the replication, when they actually exist on disk
  - drop of the StageReplicaRequest table and concept
  - introduction of the DiskToDiskCopyJob table, holding the list of ongoing disk to disk copies
  - a split of transferToSchedule into userTransferToSchedule and D2dTransferToSchedule
  - an according split in the dispatcher part of the transfer manager to call both methods. Note that with this commit, both methods fill the same FIFO queue of transfers and both take everything they can find without any throttling.

At this stage, the draining facility is broken.

Implemented by caching the count at the beginning and showing it instead of the COUNTs
of SubRequest. The latter is available as a -d, --detailed report with all progresses (# of recalls, # of migrations, etc.).

Bug #95189: Time discrepencies between disk servers and name servers can lead to silent data loss on input.

Made the CastorFile.nsOpenTime column NOT NULL and added code to prefill it
at upgrade time. This will be a long operation...

Bug #95189: Time discrepencies between disk servers and name servers can lead to silent data loss on input

- Properly use cns_file_metadata.stagertime as a single time source for stager open/close operations.
This included modifying a server-side data structure, Cns_file_metadata, and the semantics of
openx() and closex() along with their wire protocol: thus after this change only a new stager can
talk to a new nameserver (i.e. no backwards- nor forwards-compatibility provided).
- Introduced a CastorConfig table in the db with one configuration parameter, openmode, to decide
whether to use the old 'Compatibility' mode as before or the 'New' mode as described above.
- On the way, proper filling of cns_seg_metadata's creationtime, lastmodificationtime and gid fields has
been implemented for logging/statistical purposes.