disaster recovery question
Hello everyone! At our disaster recovery site we use all offsite tape volumes and do not use any of the disk storage pools. Our company runs tsm on the mainframe and does a full volume backup of all of the dasd every Sunday, which is what they restore at disaster recovery. I was wondering, if we don't restore any of the volumes for the disk pools and mark them offline after tsm is brought up will everything run smoothly as long as we restore the db, log, volume history and device configuration volumes? Thank you! *** Joni Moyer [EMAIL PROTECTED] ***
Re: disaster recovery question
This should work -- we do much the same with our TSM server on AIX for D/R. When TSM fires up it marks all the disk pools off-line if they cannot be accessed or are not properly formated. Tom Kauffman NIBCO, Inc -Original Message- From: Joni Moyer [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 1:16 PM To: [EMAIL PROTECTED] Subject: disaster recovery question Hello everyone! At our disaster recovery site we use all offsite tape volumes and do not use any of the disk storage pools. Our company runs tsm on the mainframe and does a full volume backup of all of the dasd every Sunday, which is what they restore at disaster recovery. I was wondering, if we don't restore any of the volumes for the disk pools and mark them offline after tsm is brought up will everything run smoothly as long as we restore the db, log, volume history and device configuration volumes? Thank you! *** Joni Moyer [EMAIL PROTECTED] *** CONFIDENTIALITY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
restoring an nt domain controller and disaster recovery question
Hey gang. We are doing to our offsite disaster recovery in a couple of months and I am in the middle of testing. These are a couple of questions I have that hopefully someone might have some input on: 1. Is there anything special we need to do in restoring our domain controller. Last year we restored the domain controller and we could see the domain groups and user id's but the permissions on the client shares did not work. The only way we could get users to connect is to maked everyone a domain admin (not good). 2. After installing tsm on the server I set up my database volumes (60gb). Usually I define the volumes which takes about 2 seconds per volume and then I expand the database (45-60 min) before I restore the tsm database. Is there I quicker way of doing this so I don't have to waist the 45-60min expanding the database. 3. If anyone has any disaster recovery tips and advise that would be great. I am running TSM version 5.1.6.3 on win2000. Eddie Jones 770-953-1959 ext.2824 The greatest lesson in life is to know that even fools are right sometimes. - Sir Winston Spencer Churchill ---***---
Re: restoring an nt domain controller and disaster recovery question
From: Eddie Jones [mailto:[EMAIL PROTECTED] 1. Is there anything special we need to do in restoring our domain controller. Last year we restored the domain controller and we could see the domain groups and user id's but the permissions on the client shares did not work. The only way we could get users to connect is to maked everyone a domain admin (not good). 2. After installing tsm on the server I set up my database volumes (60gb). Usually I define the volumes which takes about 2 seconds per volume and then I expand the database (45-60 min) before I restore the tsm database. Is there I quicker way of doing this so I don't have to waist the 45-60min expanding the database. 3. If anyone has any disaster recovery tips and advise that would be great. Items 1 and 3 have a single source for your answers: http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodt echnol/ad/windows2000/support/adrecov.asp?frame=truehidetoc=true Restoring a fully operational Windows 2000 domain controller is not a trivial pursuit, particularly if your original domain has multiple DCs. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: restoring an nt domain controller and disaster recovery question
And the reply to your second question is: There is no need to expand your db and dbvols. Follow the sequence: - install the server - configure tape library, drives and devclass. checkin the DB backup volume. - halt the bare TSM server (with default small DB) - using dsmfmt create adequately big DB and Log volumes - prepare the DB with dsmserv loadformat - restore the DB the dsmserv loadformat step is the one replacing your DBLog expansion. Zlatko Krastev IT Consultant Eddie Jones [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 28.05.2003 20:20 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:restoring an nt domain controller and disaster recovery question Hey gang. We are doing to our offsite disaster recovery in a couple of months and I am in the middle of testing. These are a couple of questions I have that hopefully someone might have some input on: 1. Is there anything special we need to do in restoring our domain controller. Last year we restored the domain controller and we could see the domain groups and user id's but the permissions on the client shares did not work. The only way we could get users to connect is to maked everyone a domain admin (not good). 2. After installing tsm on the server I set up my database volumes (60gb). Usually I define the volumes which takes about 2 seconds per volume and then I expand the database (45-60 min) before I restore the tsm database. Is there I quicker way of doing this so I don't have to waist the 45-60min expanding the database. 3. If anyone has any disaster recovery tips and advise that would be great. I am running TSM version 5.1.6.3 on win2000. Eddie Jones 770-953-1959 ext.2824 The greatest lesson in life is to know that even fools are right sometimes. - Sir Winston Spencer Churchill ---***---
Re: Disaster Recovery Question
Hi Mark, Just ideas, I haven't tried this, but ... How about defining your default DB backup to be on virtual volumes at the offsite location. Run a full backup at a convenient time when there's not much activity, and then daily incrementals. Run a db snapshot daily to local media. Alternatively, Run db backup or snapshot to local disk, then compress - gzip compresses db backups about 10 to 1, then move offsite by ftp or whatever Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia Remeta, Mark [EMAIL PROTECTED] 19/10/2001 4:00:26 Hello everyone. We are in the position to possibly have a T-1 between our offices and our hot site and the question has come up how to utilize the T-1 to make disaster recovery quicker. The easy answer is to backup the database to the hot site but the size of our database ~~24gb makes that impractible. I was wondering if anyone else out there has a similar setup and how they are using it. Any information would be appreciated. Thanks in advance, Mark Remeta Seligman Data Corp. 100 Park Avenue New York, NY 10017 Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately. ** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. **
Re: Disaster Recovery - Question
Not entirely true - you can start multiple restore sessions for a client. Doesn't make sense for small clients with only one disk, but for your larger NT clients with multiple disks, or your AIX clients with multiple file systems, there is no reason at all not to open multiple TSM windows and start multiple restores, up until you exceed your throughput capacity. That's one of the reasons some people collocate by file space...you can restore the file spaces in parallel. -Original Message- From: Maurice van 't Loo [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 15, 2001 5:52 PM To: [EMAIL PROTECTED] Subject: Re: Disaster Recovery - Question Don't forget that you restore serial, for one client there is only one restore session, so also 1 tapedrive is needed. You can save time when you can use collocation, but it takes more tapes; up to 90 tapes in your case. So, you can only save time when you need to restore more than 6 clients at the same time. An other help could be to use the money for the 14 drives to buy disks and make a very large diskpool, so you can use caching. All data goes to tape, but stays also in the diskpool, when you need a restore, this will save A LOT of time when you have enough network bandwidth. Good luck, Maurice van 't Loo The Netherlands - Original Message - From: Pearson, Dave [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, August 15, 2001 10:32 PM Subject: Disaster Recovery - Question Hi , I have a couple of questions about your Disaster Recovery Plan, How much parallelism does TSM recovery have. How many tape drives do you use for this plan? We have 6 tape drives (3494 tape library with 3590 tape drive). We have about 90 clients on TSM (AIX, NT, SUN) Could we use 20 tape drive to recover all the clients in a shorter time then just have 6 tape drive and take a looong time to do the recovery? Is anyone using Lanless backup on a server with the fibre network? How is this working for you? Thanks for you help Dave Pearson
Disaster Recovery - Question
Hi , I have a couple of questions about your Disaster Recovery Plan, How much parallelism does TSM recovery have. How many tape drives do you use for this plan? We have 6 tape drives (3494 tape library with 3590 tape drive). We have about 90 clients on TSM (AIX, NT, SUN) Could we use 20 tape drive to recover all the clients in a shorter time then just have 6 tape drive and take a looong time to do the recovery? Is anyone using Lanless backup on a server with the fibre network? How is this working for you? Thanks for you help Dave Pearson
Re: Disaster Recovery - Question
If you have 20 tape drives, and you're trying to recover many clients, you'll probably run into this: Restore of system A has tape volume 0001 mounted; Restore of System B ALSO needs volume 0001, so it hangs. If you collocate your copy pool, this shouldn't happen. But collocating your copy pool is not recommmended. Anyone have a good solution for this problem? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Pearson, Dave Sent: Wednesday, August 15, 2001 4:32 PM To: [EMAIL PROTECTED] Subject: Disaster Recovery - Question Hi , I have a couple of questions about your Disaster Recovery Plan, How much parallelism does TSM recovery have. How many tape drives do you use for this plan? We have 6 tape drives (3494 tape library with 3590 tape drive). We have about 90 clients on TSM (AIX, NT, SUN) Could we use 20 tape drive to recover all the clients in a shorter time then just have 6 tape drive and take a looong time to do the recovery? Is anyone using Lanless backup on a server with the fibre network? How is this working for you? Thanks for you help Dave Pearson
Re: Disaster Recovery - Question
Well, I've never had the resources to try this, but it might work. Contract for bucket loads of disk at your disaster site, enough to restore your critical nodes' primary pool, and restore the copypool to the diskpool using the maxpr switch to get multiple processes to speed the restore. Noncritical nodes can wait on tapes. Your critical nodes can then restore quickly and simultaneously from disk. Note, if anybody has the funds for that, please don't tell me as it would make me too darned jealous. Any thoughts on feasability, other than cost? Alex -Original Message- From: Lindsay Morris [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 15, 2001 1:33 PM To: [EMAIL PROTECTED] Subject: Re: Disaster Recovery - Question If you have 20 tape drives, and you're trying to recover many clients, you'll probably run into this: Restore of system A has tape volume 0001 mounted; Restore of System B ALSO needs volume 0001, so it hangs. If you collocate your copy pool, this shouldn't happen. But collocating your copy pool is not recommmended. Anyone have a good solution for this problem? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Pearson, Dave Sent: Wednesday, August 15, 2001 4:32 PM To: [EMAIL PROTECTED] Subject: Disaster Recovery - Question Hi , I have a couple of questions about your Disaster Recovery Plan, How much parallelism does TSM recovery have. How many tape drives do you use for this plan? We have 6 tape drives (3494 tape library with 3590 tape drive). We have about 90 clients on TSM (AIX, NT, SUN) Could we use 20 tape drive to recover all the clients in a shorter time then just have 6 tape drive and take a looong time to do the recovery? Is anyone using Lanless backup on a server with the fibre network? How is this working for you? Thanks for you help Dave Pearson WorldSecure Freightliner.com made the following annotations on 08/15/01 14:28:10 -- [INFO] -- Content Manager: The information contained in this communication is confidential and intended solely for the use of the individual to whom it is addressed and others authorized to receive it. If you are not the intended recipient, any disclosure, copying, distribution or taking of any action in reliance on the contents of this information is prohibited. If you have received this communication in error, please immediately notify the sender by phone if possible or via email message. ==
Re: Disaster Recovery - Question
Don't forget that you restore serial, for one client there is only one restore session, so also 1 tapedrive is needed. You can save time when you can use collocation, but it takes more tapes; up to 90 tapes in your case. So, you can only save time when you need to restore more than 6 clients at the same time. An other help could be to use the money for the 14 drives to buy disks and make a very large diskpool, so you can use caching. All data goes to tape, but stays also in the diskpool, when you need a restore, this will save A LOT of time when you have enough network bandwidth. Good luck, Maurice van 't Loo The Netherlands - Original Message - From: Pearson, Dave [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, August 15, 2001 10:32 PM Subject: Disaster Recovery - Question Hi , I have a couple of questions about your Disaster Recovery Plan, How much parallelism does TSM recovery have. How many tape drives do you use for this plan? We have 6 tape drives (3494 tape library with 3590 tape drive). We have about 90 clients on TSM (AIX, NT, SUN) Could we use 20 tape drive to recover all the clients in a shorter time then just have 6 tape drive and take a looong time to do the recovery? Is anyone using Lanless backup on a server with the fibre network? How is this working for you? Thanks for you help Dave Pearson
Re: SQL Server Disaster Recovery question
Ruddy, The piece that I didn't see you mention was restoring the msdb database. That is necessary. See Appendix B of the TDP for SQL V1 User's Guide. Also, take a look at the new TDP for SQL Redbook for more details on using TDP for SQL for disaster recovery. The redbook examples show the restore using TDP for SQL 2.2 but, you can at least follow the general process used. You can find it at: www.redbooks.ibm.com Or... here is a direct link: http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246148.pdf Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] It's a beautiful day. Don't let it get away. -- Bono Ruddy STOUDER Ruddy.Stouder@IRI To: [EMAIL PROTECTED] SLINK.COM cc: Sent by: ADSM: Subject: SQL Server Disaster Recovery question Dist Stor Manager [EMAIL PROTECTED] EDU 06/27/2001 07:38 AM Please respond to ADSM: Dist Stor Manager Hello, I made a full NT Server Disaster Recovery. According to the documentation, after the recovery: - I made a rebuild of the SQL tables - I restarted the SQL Server in single user mode - With TDP for SQL 1.1.1, I restored the master.dat file - I tried to restart the SQL server and it fails ... The same table beeing used for master.dat and model.dat, I tried : - I made a rebuild of the SQL tables - I restarted the SQL Server in single user mode - With TDP for SQL 1.1.1, I restored the master.dat and model.dat files - I tried to restart the SQL server and it fails with the following error messages ... ... 01/06/14 13:47:58.48 spid1Activating disk 'AMX_Data' 01/06/14 13:47:58.51 kernel udopen: operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device G:\MsSql\SQLserver Data Devices\AMX_Data.DAT 01/06/14 13:47:58.57 kernel udactivate (primary): failed to open device G:\MsSql\SQLserver Data Devices\AMX_Data.DAT for vdn 10 01/06/14 13:47:58.62 spid1Activating disk 'AMX_Log' 01/06/14 13:47:58.64 kernel udopen: operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device E:\MsSql\SQLserver Log Devices\AMX_Log.DAT 01/06/14 13:47:58.71 kernel udactivate (primary): failed to open device E:\MsSql\SQLserver Log Devices\AMX_Log.DAT for vdn 11 01/06/14 13:47:58.74 spid1Activating disk 'Dev_Device_Data' 01/06/14 13:47:58.78 kernel udopen: operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device G:\MsSql\SQLserver Data Devices\Dev_Device_Data.DAT ... Many thanks in advance for your help ... Ruddy Stouder Senior System Engineer TSM Certified Consultant I.R.I.S. Rue du Bosquet 10 - Parc Scientifique de Louvain-La-Neuve B-1348 Mont-Saint-Guibert [EMAIL PROTECTED] http://www.irislink.com Tel: +32 (0)10 48 75 10 - Fax: +32 (0)10 48 75 40
Re: SQL Server Disaster Recovery question
Del, Indeed, the msdb database has to be restored but, according to the redbook, it has to be done after : - With TDP for SQL 1.1.1, I restored the master.dat file - I tried to restart the SQL server and it fails ... So, after restarting the SQL server, I am supposed to restore the msdb database but the SQL server does not restart ... Ruddy Ruddy Stouder System Engineer TSM Certified Consultant I.R.I.S. Rue du Bosquet 10 - Parc Scientifique de Louvain-La-Neuve B- 1435 Mont-Saint-Guibert [EMAIL PROTECTED] http://www.irislink.com http://www.irislink.com Tel: +32 (0)10 48 75 10 - Fax: +32 (0)10 48 75 40 -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED]] Sent: mercredi 27 juin 2001 14:39 To: [EMAIL PROTECTED] Subject: Re: SQL Server Disaster Recovery question Ruddy, The piece that I didn't see you mention was restoring the msdb database. That is necessary. See Appendix B of the TDP for SQL V1 User's Guide. Also, take a look at the new TDP for SQL Redbook for more details on using TDP for SQL for disaster recovery. The redbook examples show the restore using TDP for SQL 2.2 but, you can at least follow the general process used. You can find it at: www.redbooks.ibm.com Or... here is a direct link: http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246148.pdf Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] It's a beautiful day. Don't let it get away. -- Bono Ruddy STOUDER Ruddy.Stouder@IRI To: [EMAIL PROTECTED] SLINK.COM cc: Sent by: ADSM: Subject: SQL Server Disaster Recovery question Dist Stor Manager [EMAIL PROTECTED] EDU 06/27/2001 07:38 AM Please respond to ADSM: Dist Stor Manager Hello, I made a full NT Server Disaster Recovery. According to the documentation, after the recovery: - I made a rebuild of the SQL tables - I restarted the SQL Server in single user mode - With TDP for SQL 1.1.1, I restored the master.dat file - I tried to restart the SQL server and it fails ... The same table beeing used for master.dat and model.dat, I tried : - I made a rebuild of the SQL tables - I restarted the SQL Server in single user mode - With TDP for SQL 1.1.1, I restored the master.dat and model.dat files - I tried to restart the SQL server and it fails with the following error messages ... ... 01/06/14 13:47:58.48 spid1Activating disk 'AMX_Data' 01/06/14 13:47:58.51 kernel udopen: operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device G:\MsSql\SQLserver Data Devices\AMX_Data.DAT 01/06/14 13:47:58.57 kernel udactivate (primary): failed to open device G:\MsSql\SQLserver Data Devices\AMX_Data.DAT for vdn 10 01/06/14 13:47:58.62 spid1Activating disk 'AMX_Log' 01/06/14 13:47:58.64 kernel udopen: operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device E:\MsSql\SQLserver Log Devices\AMX_Log.DAT 01/06/14 13:47:58.71 kernel udactivate (primary): failed to open device E:\MsSql\SQLserver Log Devices\AMX_Log.DAT for vdn 11 01/06/14 13:47:58.74 spid1Activating disk 'Dev_Device_Data' 01/06/14 13:47:58.78 kernel udopen: operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device G:\MsSql\SQLserver Data Devices\Dev_Device_Data.DAT ... Many thanks in advance for your help ... Ruddy Stouder Senior System Engineer TSM Certified Consultant I.R.I.S. Rue du Bosquet 10 - Parc Scientifique de Louvain-La-Neuve B-1348 Mont-Saint-Guibert [EMAIL PROTECTED] http://www.irislink.com Tel: +32 (0)10 48 75 10 - Fax: +32 (0)10 48 75 40
Re: SQL Server Disaster Recovery question
Did you rebuild the master database using the same character set and sort order as the master database backup being restored? After restoring the master database, are you restarting the sql server in multi-user mode ( Ie. Not in single user mode) ? What errors are you getting when you restart the server? Any event log messages? Thanks, Bill William Degli-Angeli IGS TDP Development Endicott, NY (607) 752-6749 TieLine: 852-6749 Internet: [EMAIL PROTECTED] Ruddy STOUDER Ruddy.Stouder@IRI To: [EMAIL PROTECTED] SLINK.COM cc: Sent by: ADSM: Subject: Re: SQL Server Disaster Recovery question Dist Stor Manager [EMAIL PROTECTED] EDU 06/27/2001 11:44 Please respond to ADSM: Dist Stor Manager Del, Indeed, the msdb database has to be restored but, according to the redbook, it has to be done after : - With TDP for SQL 1.1.1, I restored the master.dat file - I tried to restart the SQL server and it fails ... So, after restarting the SQL server, I am supposed to restore the msdb database but the SQL server does not restart ... Ruddy Ruddy Stouder System Engineer TSM Certified Consultant I.R.I.S. Rue du Bosquet 10 - Parc Scientifique de Louvain-La-Neuve B- 1435 Mont-Saint-Guibert [EMAIL PROTECTED] http://www.irislink.com http://www.irislink.com Tel: +32 (0)10 48 75 10 - Fax: +32 (0)10 48 75 40 -Original Message- From: Del Hoobler [mailto:[EMAIL PROTECTED]] Sent: mercredi 27 juin 2001 14:39 To: [EMAIL PROTECTED] Subject: Re: SQL Server Disaster Recovery question Ruddy, The piece that I didn't see you mention was restoring the msdb database. That is necessary. See Appendix B of the TDP for SQL V1 User's Guide. Also, take a look at the new TDP for SQL Redbook for more details on using TDP for SQL for disaster recovery. The redbook examples show the restore using TDP for SQL 2.2 but, you can at least follow the general process used. You can find it at: www.redbooks.ibm.com Or... here is a direct link: http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246148.pdf Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] It's a beautiful day. Don't let it get away. -- Bono Ruddy STOUDER Ruddy.Stouder@IRI To: [EMAIL PROTECTED] SLINK.COM cc: Sent by: ADSM: Subject: SQL Server Disaster Recovery question Dist Stor Manager [EMAIL PROTECTED] EDU 06/27/2001 07:38 AM Please respond to ADSM: Dist Stor Manager Hello, I made a full NT Server Disaster Recovery. According to the documentation, after the recovery: - I made a rebuild of the SQL tables - I restarted the SQL Server in single user mode - With TDP for SQL 1.1.1, I restored the master.dat file - I tried to restart the SQL server and it fails ... The same table beeing used for master.dat and model.dat, I tried : - I made a rebuild of the SQL tables - I restarted the SQL Server in single user mode - With TDP for SQL 1.1.1, I restored the master.dat and model.dat files - I tried to restart the SQL server and it fails with the following error messages ... ... 01/06/14 13:47:58.48 spid1Activating disk 'AMX_Data' 01/06/14 13:47:58.51 kernel udopen: operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device G:\MsSql\SQLserver Data Devices\AMX_Data.DAT 01/06/14 13:47:58.57 kernel udactivate (primary): failed to open device G:\MsSql\SQLserver Data Devices\AMX_Data.DAT for vdn 10 01/06/14 13:47:58.62 spid1Activating disk 'AMX_Log' 01/06/14 13:47:58.64 kernel udopen: operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device E:\MsSql\SQLserver Log Devices\AMX_Log.DAT 01/06/14 13:47:58.71 kernel udactivate (primary): failed to open device E:\MsSql\SQLserver Log Devices\AMX_Log.DAT for vdn 11 01/06/14 13:47:58.74 spid1Activating disk 'Dev_Device_Data' 01/06/14 13:47:58.78 kernel udopen: operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device G:\MsSql\SQLserver Data Devices\Dev_Device_Data.DAT ... Many thanks in advance for your help ... Ruddy Stouder Senior System Engineer
