(Ayee, my regrets: my former reply was added as HTML where it should have been plain-old text.)
I consider goto (like some before me) obsolete and its use obnoxious.
This function screams for a simple for-loop. I know it is possible to use fewer local variables and a little less arithmetic. Probably there is also a more elegant recursive solution, however tending to be less readable and more error-prone. Coding-quality should prevail above beauty and elegance?
SOLUTION EXAMPLE
int multiply( int a, int b) {
int x=0;// define local variable
int y=1;// define local variable
if (!( a > 0 )) return -1;// short noted version of for-loop (i.e.: for (expression) {statement} ) is against aforementioned JSF coding principles// long noted version of for-loop with whitespace follows below
I consider goto (like some before me) obsolete and its use obnoxious.
This function screams for a simple for-loop. I know it is possible to use fewer local variables and a little less arithmetic. Probably there is also a more elegant recursive solution, however tending to be less readable and more error-prone. Coding-quality should prevail above beauty and elegance?
SOLUTION EXAMPLE
int multiply( int a, int b)
{
int x=0;// define local variable
int y=1;// define local variable
if (!( a > 0 )) return -1;// short noted version of for-loop (i.e.: for (expression) {statement} ) is against aforementioned JSF coding principles// long noted version of for-loop with whitespace follows below
for (y=1; y=a, y++)
{
x+=b
}
return x;
}
This is a lot of extensive work done to make sure your data is safe. But it might not be a solution for the problems mentioned here: - files might be too large to be mailed - two or more computers are likely to be used to work on - for larger amounts of data -as pointed out here- both CDs and DVDs are too small to contain even one file or project. - if your 2 TB cabinet fails, would you ever be able to restore all the data that was on it? Likely you have to try to REMEMBER which data was on your cabinet, and which data not...
Let me point out some reasons why this is not a solution to the problems pointed out by the originator:
1. After some time, your old DV tapes are not accessible anymore with your newer photo/DV hardware as it will use new types of storage.
2. You lose ALL YOUR editing when having to restore from the original DV tape. As far as I know of this profession, this is NOT acceptable, as there is a lot of creative work done in the progress. Which might be impossible to redo the very same way.
3. To keep the data in the FireWire closet is nice, but your data is still not offsite.
4. You would need software to keep track of your versions and to be able to archive end-versions of your work.
What a bogus answer this is.
Just buying hardware like a NAS-box does not manage any of the data nor will it bring the data offsite by way of thought. You need SOFTWARE too and removable media to accomplish this in a sound way.
Please read my own reply for a more serious answer.
Firstly, please notice I'm an IBM employee working with IBM Tivoli Storage Manager (TSM) for eight years now.
Secondly I am a little disappointed in the answers you have gotten so far. Both in seriousness and in quality.
And as a remembrance to the first point, whenever you read TSM in my reply below, keep in mind there might be other software or solutions that could be of help...but I think myself TSM might be the best solution for you.
At first a small setting of the environment: you and your wife work with large files, and with a fair amount of total data. So in the end, you need high quality software and hardware that enables you to move all your data on all your computers offsite and/or to newer storage hardware. This hardware will be costly, but as you and your wife are professionals, you should take into account any extra costs for backing up and archiving as occupational costs.
If you do not have the amount of money needed...then you will always end up with solutions that are not answering all the needs you pointed out.
TSM will manage the data of multiple computers. These will need a network connection to the TSM server, which might be located on any one of your computers (it doesn't uses much CPU, but it will eat up 1 GB of memory though). So likely you could use any available old/spare computer you likely possess, as a DV professional I expect you to buy faster computers on a regular basis.
You likely want to keep track of your backups which is about storing different versions (that is, when editing a file you create a new version) of the same file over a certain period. A restore should likely be possible for say some version of some time ago. And sometimes you would like to be able to group some files together for backup and versioning, as the one without the other maybe pointless. And whenever a files becomes obsolete (say after ten versions or any old version after a defined period), it should be removed from your precious and expensive storage;-)
You also definitely want to archive which is storing a partical version of a file for a certain period (maybe forever).
This is all possible with TSM and the right hardware. Have TSM perform backups regularly (scheduled daily or moreoften if you want) or manually started in between whenever you need one. You can chose what files to backup, and what not. You can also create archives with TSM, which will be stored for any period you define.
But then it becomes serious: what will you be using for hardware? With TSM you need a storage library which can store all versions in your backups and archives online, so you can access it without hassles. And likely you want to use removable media so TSM can make duplicates of your data which then may be brought offsite (any vault or shelf in another location).
I think you have two possibilities: either a tape library or a optical library. There is really not much against optical libraries if only that tapes like LTO3 may store 400 GB uncompressed (800 GB compressed), which exceeds any optical device by far. But do not compare filesize to device storage as TSM will split any large file over any amount of opticals or tapes if needed.
Lastly, you and your wife are a DV/photo professionals, not specialists into business continuity. So you likely want a one-stop solution that is easy to work with, uses TSM and a library, and is pre-setup. You then might take a look at www.storserver.com. They have solutions with disk-based storage only, or additional tpae libraries etc. etc.
There might be others I do not know of, please consider an IBM Business Partner for more help in this.
In the end: such storage is much more expensive compared to USB-HDs. But these won't last forever, do not keep track of different versions in your backup, manage your archives and it won't keep all your backup and archive versions online.
Still, you could use maybe a single USB disk for each of the seven days for backup, and use additional USB-HDs for archives. As soon as your daily data exceeds the USB-HD capacity, you come into trouble again.
Anyone should first understand why we need passwords. Enforced passwords are used as a means to deliver an environment in which:
- it should be reasonably ensured that any service is used by only the correct person
- and any person should be reasonably ensured that what its owns in this infrastructure is only validly used by him (and/or others if expressly arranged for)
Passwords get useless if they are easily guessed (by programs or by looking over the shoulder). But passwords are also useless if people are 'enforced' to write them down in order to remember.
The IT Security dept. should thus set rules for the password engine which the user enforces to create SAFE passwords. But leave it to the user!
Here my educational guesses for a secure password environment:
- a dictionary check should be or might be part of the password engine
- any user-created password should be at least 12 characters
- any user-created password should contain at least one digit
- any user-created password should contain at least one non-alphabetic character
And if the engine allows for it:
- any user-created password should contain at least one space, allowing for passphrases
But anyway, the user should still be able to create its own passwords. And of course, anyone should have preferably only one password for its complete corporate envronment (single sign-on).
Slashdot Mirror
(Ayee, my regrets: my former reply was added as HTML where it should have been plain-old text.)
I consider goto (like some before me) obsolete and its use obnoxious.
This function screams for a simple for-loop. I know it is possible to use fewer local variables and a little less arithmetic. Probably there is also a more elegant recursive solution, however tending to be less readable and more error-prone. Coding-quality should prevail above beauty and elegance?
SOLUTION EXAMPLE
int multiply( int a, int b) // define local variable // define local variable // short noted version of for-loop (i.e.: for (expression) {statement} ) is against aforementioned JSF coding principles // long noted version of for-loop with whitespace follows below
{
int x=0;
int y=1;
if (!( a > 0 )) return -1;
for (y=1; y=a, y++)
{
x+=b
}
return x;
}
I consider goto (like some before me) obsolete and its use obnoxious. This function screams for a simple for-loop. I know it is possible to use fewer local variables and a little less arithmetic. Probably there is also a more elegant recursive solution, however tending to be less readable and more error-prone. Coding-quality should prevail above beauty and elegance? SOLUTION EXAMPLE int multiply( int a, int b) { int x=0; // define local variable
int y=1; // define local variable
if (!( a > 0 )) return -1; // short noted version of for-loop (i.e.: for (expression) {statement} ) is against aforementioned JSF coding principles // long noted version of for-loop with whitespace follows below
for (y=1; y=a, y++)
{
x+=b
}
return x;
}
This is a lot of extensive work done to make sure your data is safe. But it might not be a solution for the problems mentioned here:
- files might be too large to be mailed
- two or more computers are likely to be used to work on
- for larger amounts of data -as pointed out here- both CDs and DVDs are too small to contain even one file or project.
- if your 2 TB cabinet fails, would you ever be able to restore all the data that was on it? Likely you have to try to REMEMBER which data was on your cabinet, and which data not...
Let me point out some reasons why this is not a solution to the problems pointed out by the originator:
1. After some time, your old DV tapes are not accessible anymore with your newer photo/DV hardware as it will use new types of storage.
2. You lose ALL YOUR editing when having to restore from the original DV tape. As far as I know of this profession, this is NOT acceptable, as there is a lot of creative work done in the progress. Which might be impossible to redo the very same way.
3. To keep the data in the FireWire closet is nice, but your data is still not offsite.
4. You would need software to keep track of your versions and to be able to archive end-versions of your work.
What a bogus answer this is. Just buying hardware like a NAS-box does not manage any of the data nor will it bring the data offsite by way of thought. You need SOFTWARE too and removable media to accomplish this in a sound way. Please read my own reply for a more serious answer.
Firstly, please notice I'm an IBM employee working with IBM Tivoli Storage Manager (TSM) for eight years now.
;-)
Secondly I am a little disappointed in the answers you have gotten so far. Both in seriousness and in quality.
And as a remembrance to the first point, whenever you read TSM in my reply below, keep in mind there might be other software or solutions that could be of help...but I think myself TSM might be the best solution for you.
At first a small setting of the environment: you and your wife work with large files, and with a fair amount of total data. So in the end, you need high quality software and hardware that enables you to move all your data on all your computers offsite and/or to newer storage hardware. This hardware will be costly, but as you and your wife are professionals, you should take into account any extra costs for backing up and archiving as occupational costs.
If you do not have the amount of money needed...then you will always end up with solutions that are not answering all the needs you pointed out.
TSM will manage the data of multiple computers. These will need a network connection to the TSM server, which might be located on any one of your computers (it doesn't uses much CPU, but it will eat up 1 GB of memory though). So likely you could use any available old/spare computer you likely possess, as a DV professional I expect you to buy faster computers on a regular basis.
You likely want to keep track of your backups which is about storing different versions (that is, when editing a file you create a new version) of the same file over a certain period. A restore should likely be possible for say some version of some time ago. And sometimes you would like to be able to group some files together for backup and versioning, as the one without the other maybe pointless. And whenever a files becomes obsolete (say after ten versions or any old version after a defined period), it should be removed from your precious and expensive storage
You also definitely want to archive which is storing a partical version of a file for a certain period (maybe forever).
This is all possible with TSM and the right hardware. Have TSM perform backups regularly (scheduled daily or moreoften if you want) or manually started in between whenever you need one. You can chose what files to backup, and what not. You can also create archives with TSM, which will be stored for any period you define.
But then it becomes serious: what will you be using for hardware? With TSM you need a storage library which can store all versions in your backups and archives online, so you can access it without hassles. And likely you want to use removable media so TSM can make duplicates of your data which then may be brought offsite (any vault or shelf in another location).
I think you have two possibilities: either a tape library or a optical library. There is really not much against optical libraries if only that tapes like LTO3 may store 400 GB uncompressed (800 GB compressed), which exceeds any optical device by far. But do not compare filesize to device storage as TSM will split any large file over any amount of opticals or tapes if needed.
Lastly, you and your wife are a DV/photo professionals, not specialists into business continuity. So you likely want a one-stop solution that is easy to work with, uses TSM and a library, and is pre-setup. You then might take a look at www.storserver.com. They have solutions with disk-based storage only, or additional tpae libraries etc. etc.
There might be others I do not know of, please consider an IBM Business Partner for more help in this.
In the end: such storage is much more expensive compared to USB-HDs. But these won't last forever, do not keep track of different versions in your backup, manage your archives and it won't keep all your backup and archive versions online.
Still, you could use maybe a single USB disk for each of the seven days for backup, and use additional USB-HDs for archives. As soon as your daily data exceeds the USB-HD capacity, you come into trouble again.
Anyone should first understand why we need passwords. Enforced passwords are used as a means to deliver an environment in which: - it should be reasonably ensured that any service is used by only the correct person - and any person should be reasonably ensured that what its owns in this infrastructure is only validly used by him (and/or others if expressly arranged for) Passwords get useless if they are easily guessed (by programs or by looking over the shoulder). But passwords are also useless if people are 'enforced' to write them down in order to remember. The IT Security dept. should thus set rules for the password engine which the user enforces to create SAFE passwords. But leave it to the user! Here my educational guesses for a secure password environment: - a dictionary check should be or might be part of the password engine - any user-created password should be at least 12 characters - any user-created password should contain at least one digit - any user-created password should contain at least one non-alphabetic character And if the engine allows for it: - any user-created password should contain at least one space, allowing for passphrases But anyway, the user should still be able to create its own passwords. And of course, anyone should have preferably only one password for its complete corporate envronment (single sign-on).