Defragment NTFS parbreastion 3418
Well, there are examples when backup went wrong and people lost all their data.
The NTFSResize FAQ, what Chris mentioned previously, also says at
On Thu, 21 Apr 2005 16:22:33 +0000, Erix Some of the developers are paid to do so, by companies big and small. I'd say most of them are like...
Question: Is it reliable?
Answer: Yes, it is reliable. Since July of 2002, when ntfsresize became
publicly available, there were countless success reports for both enlarging and shrinking Windows XP-2000-NT4, Windows Server 2003 and Longhorn NTFS filesystems on both workstation and server versions (Home, Professional, Server, Advanced Server). No destroyed filesystem was reported ......
My experiences are the same. However this is how it's done usually (or should be):
Hi, I have a question. I've set up a PPTP server with PoPToP for a VPN server. This server...
1. Make BACKUPS REGULARLY. Daily, weekly, monthly depending on how often you use your computers and how important your data are. 2. Check that you backup is correct. 3. Resize the parbreastion when you have already a good backup. 4. If step 3 goes wrong for whatever reason (e.g. power outage) then recover from the good backup.
Furthermore backing up only files or the parbreastion is not enough. Just in the recent past there were many examples when people couldn't boot from a reinstalled (or restored) Windows after Linux installation because the parbreastion table became corrupted due to the kernel disk geomety detection code, independently if anything was resized or not. Therefore one should SAVE THE PARbreastION TABLE as well.
The filesystem and parbreastion modifying are two different steps and even if the filesystem part goes well, a corrupt parbreastion table can cause boot or filesystem accessibility problems what quite often are interpreted wrongly hence worked around unsuccessfully.
IPTABLES question, multiple rules
Linux groups from Newsgroups