Hello,
Thanks for the quick reply.
This business could have been a tragedy as you can imagine and I want to understand how it happened so as to avoid it in the future.
Quote:
Originally Posted by nixcraft
I'm not sure if I got your question.. Do you store both data and backup on NAS? Is /tmp mapped to nas?
|
No the data (commercial analysis database is on SUSE 10.3 Enterprise Server, the NAS on the same network is a simple Buffalo TeraStation.
Quote:
Originally Posted by nixcraft
Yes, delete operation over NAS can be very fast. You will only notice difference for large size files and overloaded network. NAS disks rotate at higher speed and works in RAID to improve I/O.
NAS folders are mounted using NFS or SMB or other supported protocol. If you delete a file from mounted directory, it will get deleted. Backup is only solution. Take regular backup.
|
In this case it was an SMB connection, this NAS does not support NFS.
Please explain how cancelling a file or directory in the /tmp directory can wipe out the corresponding NAS backed up file or folder.
What logic does that follow ? I mean I do not understand why an App would make folders in the /tmp directory, the contents of which are of course prone to deletion, and hard link them to the remote area which contains the copied data so that the data could be accidentally eliminated.
In fact I will have problems restoring the data.
Quote:
Originally Posted by nixcraft
No it should not delete files but I can think of few possiblities:
- /tmp is mapped wih nas over NFS or CIFS.
- /tmp is monitored using script and events. A cutomemade script watches the filesystem for specified changes and executes the relevant commands.
- Linux also allows to map same shared nas directory. So you can have it mapped to /tmp and /data.. run mount command to see connection.
HTH |
Thanks for confirming that it should not delete the remote files.
I believe I had 'killed' the app process before the event.
I ran a mount and I saw no reference to /tmp/XXX
On the other hand I did notice processes referring to CIFS.
But here again I did not map anything to /tmp.
I connected to the remote the remote destination folder using a SMB connection and in fact the App used an SMB connection to complete its backup.
Any other ideas or suggestions.
The alarming thing here is that if I reboot and the /tmp subdirs are cancelled while the NAS is online I could find that the NAS is emptied !
Seems absurd that a professional App created a situation like this.
[I will remain online for about 40 minutes Thanks]