Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*NT\s+Backup\/recovery\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*NT\s+Backup\/recovery\s*$/: 15 ]

Total 15 documents matching your query.

1. NT Backup/recovery (score: 1): Author: Eric Tang <tangeric AT HK1.IBM DOT COM>; Date: Wed, 29 Nov 2000 10:44:05 +0800; Hi All, For NT 4.0, I have tested the Bare Metal Restore on a testing PC and the procedures is fine. However, it seems unrealistic to have a NT repair partition in particular for a NT with only one h; /lists/html/ADSM-L/2000-11/msg01333.html (9,227 bytes)
2. Re: NT Backup/recovery (score: 1): Author: "Talafous, John G." <Talafous AT TIMKEN DOT COM>; Date: Wed, 29 Nov 2000 08:57:40 -0500; We do not run any additional backup utilities. Just TSM. We have developed recovery procedures and posted them to our intranet. These procedures cover the recovery to identical hardware and non-ident; /lists/html/ADSM-L/2000-11/msg01346.html (9,751 bytes)
3. NT Backup/recovery (score: 1): Author: Eric Tang [mailto:tangeric AT HK1.IBM DOT COM]; Date: Tue, 28 Jun 2011 17:01:03 -0500; Hi All, For NT 4.0, I have tested the Bare Metal Restore on a testing PC and the procedures is fine. However, it seems unrealistic to have a NT repair partition in particular for a NT with only one h; /lists/html/ADSM-L/2000-11/msg01347.html (9,426 bytes)
4. Re: NT Backup/recovery (score: 1): Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL>; Date: Wed, 29 Nov 2000 13:02:29 +0100; Hi Eric! Assuming your hardware is identical to the one before the crash, ours works like this: We are using a dedicated client (lets call it node A for now) through which recovery is done. 1) Allow; /lists/html/ADSM-L/2000-11/msg01350.html (10,581 bytes)
5. NT Backup/recovery (score: 1): Author: Eric Tang [mailto:tangeric AT HK1.IBM DOT COM]; Date: Tue, 28 Jun 2011 17:01:03 -0500; Hi All, For NT 4.0, I have tested the Bare Metal Restore on a testing PC and the procedures is fine. However, it seems unrealistic to have a NT repair partition in particular for a NT with only one h; /lists/html/ADSM-L/2000-11/msg01351.html (10,338 bytes)
6. Re: NT Backup/recovery (score: 1): Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL>; Date: Wed, 29 Nov 2000 16:17:34 +0100; Hi Stefan! Because our method saves time. You don't have to install TSM on the crashed node which also takes up a couple of minutes (atleast a reboot because of the installation of the Microsoft Inst; /lists/html/ADSM-L/2000-11/msg01368.html (9,311 bytes)
7. Re: NT Backup/recovery (score: 1): Author: "France, Don G (Pace)" <don.france-eds AT EDS DOT COM>; Date: Wed, 29 Nov 2000 12:31:58 -0800; You could, alternatively, do any of the following: * Install a temp NT system in the same partition, using different name from "WINNT"; * Consider using the TDP for Workgroups, to protect C-drive (st; /lists/html/ADSM-L/2000-11/msg01391.html (10,652 bytes)
8. Re: NT Backup/recovery (score: 1): Author: Eric Tang <tangeric AT HK1.IBM DOT COM>; Date: Thu, 30 Nov 2000 12:38:40 +0800; Hi Eric, Am I understand your procedures correctly? 1. The crashed machine is called NodeA. And there is another NT (NodeB) up and running 2. install NT to the crashed machine on c:\winnt.tmp and cal; /lists/html/ADSM-L/2000-11/msg01405.html (9,523 bytes)
9. Re: NT Backup/recovery (score: 1): Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL>; Date: Thu, 30 Nov 2000 09:54:53 +0100; Hi Eric! You can skip step 3, this is done by Windows NT by default. Don't forget to configure all your TSM clients to allow access to node B (Utilities => User Access List...) and also do not forget; /lists/html/ADSM-L/2000-11/msg01412.html (9,502 bytes)
10. Re: NT Backup/recovery (score: 1): Author: Eric Tang [mailto:tangeric AT HK1.IBM DOT COM]; Date: Tue, 28 Jun 2011 17:01:04 -0500; Hi Eric, Am I understand your procedures correctly? 1. The crashed machine is called NodeA. And there is another NT (NodeB) up and running 2. install NT to the crashed machine on c:\winnt.tmp and cal; /lists/html/ADSM-L/2000-11/msg01413.html (10,431 bytes)
11. Re: NT Backup/recovery (score: 1): Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL>; Date: Thu, 30 Nov 2000 10:06:01 +0100; Hi Stefan! That was my first impression too. But we have done several tests, comparing performance between both procedures. The difference in performance was very very small. Only if your C drive is; /lists/html/ADSM-L/2000-11/msg01417.html (9,563 bytes)
12. Re: NT Backup/recovery (score: 1): Author: Eric Tang <tangeric AT HK1.IBM DOT COM>; Date: Thu, 30 Nov 2000 17:50:56 +0800; Hi Eric, Or if you know password of NodeA, issue dsmc restore \\nodeA\c$ to sharedisk$ -nodename=nodeA -password=xxxx on NodeB. Thanks a lot. Regards, Eric Tang; /lists/html/ADSM-L/2000-11/msg01422.html (9,144 bytes)
13. NT Backup/Recovery (score: 1): Author: Paul Schwartz <71421.1614 AT COMPUSERVE DOT COM>; Date: Mon, 9 Dec 1996 22:05:21 EST; To all, We are currently trying to implement ADSM for backing up remote NT servers over a frame-relay network. We have run into a variety of problems including: 1. Long delay querying the ADSM databa; /lists/html/ADSM-L/1996-12/msg00184.html (8,663 bytes)
14. Re: NT Backup/Recovery (score: 1): Author: Simon Foster <simon.foster AT NATWESTUK.CO DOT UK>; Date: Tue, 10 Dec 1996 11:47:03 -0800; Microsoft Mail v3.0 (MAPI 1.0 Transport) IPM.Microsoft Mail.Note From: FOSTER, Simon, SADS To: INTERNET:ADSM-L AT VM.MARIST DOT EDU/ Subject: RE: NT Backup/Recovery Date: 1996-12-10 11:42 Priority: 3; /lists/html/ADSM-L/1996-12/msg00188.html (8,387 bytes)
15. Re: NT Backup/Recovery (score: 1): Author: "Pittson, Timothy ,Corp/US" <tpittson AT HIMAIL.HCC DOT COM>; Date: Tue, 10 Dec 1996 08:01:01 -0500; 2) Look at changing the COMMTIMEOUT value in the ADSM server options file. 3) We've been beta testing the Seagate Backup Exec for NT / ADSM interface. Currently testing it for Microsoft Exchange but; /lists/html/ADSM-L/1996-12/msg00192.html (10,994 bytes)

Current List: 1 - 15
Page: [1]