- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Here are some of the best practices to take into consideration in any backup & recovery system:
Usually perform system state backups of your servers
frequently. Each computer on a Windows network has a corresponding
computer account in Active Directory. Like a user account, the computer
account has an associated password. The difference is that the password
is assigned, and periodically changed, by Windows. If you try to
restore a system state backup that is too old, the computer account
password that is stored in the backup will no longer match the password
that is bound to the computer account in Active Directory. As a result,
the machine won't be able to participate in the domain. There are
workarounds, but it is usually easier to just make frequent system
state backups of your servers, & use these backups to recover the
servers when needed.
Always backup the data, the server's operating system,
& the applications installed on the server. Although it is true
that, if a server fails and you need to perform a full recovery, you
can reinstall the operating system & the applications & then
restore any data. However, time is of the essence when trying to
recover from a crash. It is much faster to restore everything from
backup than it is to manually install an operating system and a set of
applications. More important, it is often difficult to manually
configure a server so that it matches its previous configuration.
Backing up the entire server ensures that its configuration will be
exactly as it was before the crash.
Periodically test your backups to make sure you are
able to use them for recovery when the disaster strikes. Always
remember that we perform backups in order to be able to restore from
then when we need to. So, we have to make sure our backups are usable.
For some applications (for example, Microsoft SQL
Server, Microsoft Exchange Server, Lotus Domino Server, ... etc), a
file-level backup is insufficient. These applications usually utilize
open databases that need a special backup agent to back them up
consistently while they are being in-use. Usually make sure that you
are using the correct backup agent needed by your application.
While you should keep backups off site, consider
waiting until the end of the business day to remove the previous
night's tapes from the building. This way, if your server fails early
during the day, you will not have to wait for hours till you can get
the tapes on-site again & start the recovery.
Construct your backup architecture in a way that
avoids (at least as much as possible) having a single point of failure.
If possible, have a backup for your backups, or configure 2 independent
backup schedules to run everyday.
Do not rely solely on a disk-to-disk backup solution.
Although disk-to-disk backup solutions offer many advantages over
traditional tape backups, they should not be the only backup solution
to rely upon. In such a scenario, the backup server is prone to the
same risks as the servers it protects. A hurricane, lightning strike,
fire, or flood could wipe out your backup server along with your other
servers. For this reason, it is important to dump the contents of your
disk based backups to tape on a frequent basis, and then store those
tapes in an off-site secure storage.
When deciding to replace your current backup
technology with a newer one, do not get rid of the old tapes, tape
device(s) & backup software. At least, do not do this unless you
are sure that your newer tape device(s) support the older tapes, or
that you have moved the older backups to newer media supported by the
newer tape device(s). This way, when it is required to retrieve data
from the old backups, you will be able easily to retrieve the required
data. This also could apply to the older backup software if the newer
backup application does not support the older tapes or tape device(s).
There is no denying that it is important to secure
your backups, but it is equally important to consider the consequences
of your security measures. If you find yourself having to restore a
backup after a major system failure, the last thing you need is an
ill-conceived security mechanism standing in the way of the recovery.
For example, if you are planning to use hardware-level encryption, do
not forget (when time comes to upgrade your backup hardware) to make
sure that your new hardware supports the previously used encryption.
Always use a long tape rotation scheme, or at least keeping some of your backup tapes as long-term archives.
Hi If a page does not return within a few minutes, many users perceive that a problem has occurred and stop the process. Therefore, design your server processes to return data within 5 minutes so that users do not have to wait for a long time.
You can usually break down long processes into smaller pieces. Or, the server can return status data to update users about the process. In addition, you can create a long server process with a messages-based or asynchronous approach so that it returns immediately to the client after the job is submitted and notifies users when the long process is finished.
First of all backup all of ur data include your database if its stored on server , any encrypted files be sure that you decrypt it first after backup , determine if the server hardware compatible with new OS , don't forget the raid configurations after all of that boot with your new system CD and let the system format the hard for you i don't prefer to use third party application if i use microsoft windows
Backing up data is a simple proposition. You just need to know what the company is about and how the server is structured. Most of the time, if done correctly, there will be a users folder on the server located on anything but the main drive. All user data should be there and should, by default backed up. There will also be another folder, again depending on the company, where all the data would reside. Most of the types of files to be backed up would be email files. If Outlook, these would be their PST files. Any WORD or EXCEL files, extensions DOC (DOCX if Office 2007), and XLS respectively. You also need to know what software they will be using. If you don't know, now's not a good time to learn.
Back UP, its a utility commonly used in all operating system to backing up our personal documents, pictures, videos,outlook mail boxes. It is a very useful tool to prevent the damage of disk drives. we can backing up our data by using hard drives, cd-dvds, flash drives, tape drives,etc..
Raid 6 will tolerate two simulatneous hard disk failures. So the posibility for data loss is very less. But the rebuilting steps defers for different server products like IBM and DELL. But normaly when u change a new hard disk the server will automatically starts the rebuilding process.
Microsoft Windows Server 2003, Web Edition
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise x64 Edition
Microsoft Windows Small Business Server 2003 Premium Edition
This problem occurs when the following conditions are true:
You back up data from a volume that contains a Microsoft SQL Server database.
The recovery model of the SQL Server database is configured to use an option that is different from Simple.
Submit a request here to get a hotfix from Microsoft ( Its free and no product key will be asked )