Welcome! » Log In » Create A New Profile

Fw: Rejected posting to EMC-DATAPROTECTION-L@LISTSERV.TEMPLE.EDU

Posted by Michael Leone 
This is odd. I need to recover a SQL DB from 2018-01-07, using the
Networker User for SQL Server (8.2.3.0.1100) . So I found the saveset I
wanted

>mminfo -avot -q "savetime>=01/05/2018,savetime<=01/10/2018,client=pssql3"
-r volume,name,savetime(22),totalsize(2),ssid,cloneid,ssflags

002369 MSSQL: 1/7/2018 11:58:57 PM 502
GB 3612539537 1515405258 vrEF

Then I changed the expiration date, and made it notrecyclable,

>nsrmm -S 3612539537/1515405258 -e 12/31/2025
If this saveset has dependents with longer retention periods, the
dependent savesets will not be browsable after the retention pol
icy expiration date `Wed Dec 31 00:00:00 2025'.
Are you sure you want to change the retention policy expiration of this
saveset to `Wed Dec 31 00:00:00 2025'? (yes/no) [no] yes

>nsrmm -S 3612539537/1515405258 -o notrecyclable
Mark save set copy 3612539537/1515405258 as not recyclable? yes

Then I found the tape with the CFI, and recovered that ...

s>nsrck -L7 -t 01/08/2018 pssql3
nsrck: checking index for 'pssql3'
9343:nsrck: The file index for client 'pssql3' will be
recovered.9433:nsrck: Recovering index savesets of 'pssql3' from
'dctrman00
4.wrk.ads.pha.phila.gov'
Recover start time: 7/19/2018 12:05:55 PM
Requesting 1 recover session(s) from server.
Recover completion time: 7/19/2018 12:07:07 PM
9346:nsrck: completed recovery of index for client 'pssql3'
nsrck: D:\Program Files\Legato\nsr\index\pssql3 contains 725079 records
occupying 100 MB
nsrck: Completed checking 1 client(s)


I should be good to go .... not expired, good browse time, index
recovered.

>mminfo -avot -q "savetime>01/06/2018,savetime<01/08/2018,client=pssql3"
-r volume,client,name,savetime(22),ssbrowse(22),ssretent(22),ssflags
volume client name date time
browse time retention time ssflags

002369 pssql3 MSSQL: 1/7/2018
11:58:57 PM 12/30/2025 12:00:00 AM 7/11/2026 12:19:17 PM vF


So how come, when I go to that SQL server, and tell it I want to recover a
specific instance, and I can't choose any instance prior to June 28, 2018?
Why am I not seeing that Jan 7, 2018 instance?? It has a valid browse
time, valid expiration time, and is not expired.

What gives? Anybody know? Luckily, we make a BAK version of all our
databases, and that BAK version restored fine, using the exact same
procedure as above. The only difference (that I can see) is that one is a
SQL 2012 MDF file, and the other is an ASCI file.
I can't embed a screenshot to show you the error, but it occurs when I try
to choose a specific instance, and browse to the date I want. It tells me
that I have to choose an instance between Jun 28 and Jul 18. And I have no
idea why ...

Thanks
--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
1800 South 32nd Street
Phila, PA 19145
Hours: 8AM - 4PM EST
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone@pha.phila.gov>



--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
We had something similar happen to us, and found a workaround. Hope it works for you.

When you open Networker user for SQL, instead of using the menu to hit recover (I believe it is actually operation, then recover), click on the icon that says recover, and then popup box will then allow you to browse to the date you need. You can't do it via change browse time.

It took us a while to find this workaround, and it was just lucky that we found it. Networker support had no clue.

Let me know if this works for you.

David M. Browning Jr.
IT Project Coordinator Enterprise Backups and Help Desk
(504) 568-4364 (Direct)
(504) 654-7520 (BlackBerry number)
http://www.lsuhsc.edu/ithelpdesk
Twitter: @LSUHSCNO_IT


From: EMC Data Protection Q & A [mailto:EMC-DATAPROTECTION-L@LISTSERV.TEMPLE.EDU] On Behalf Of Michael Leone
Sent: Thursday, July 19, 2018 2:29 PM
To: EMC-DATAPROTECTION-L@LISTSERV.TEMPLE.EDU
Subject: [EMC-DataProtection-L] Fw: Rejected posting to EMC-DATAPROTECTION-L@LISTSERV.TEMPLE.EDU

*EXTERNAL EMAIL: EVALUATE*This is odd. I need to recover a SQL DB from 2018-01-07, using the Networker User for SQL Server (8.2.3.0.1100) . So I found the saveset I wanted

>mminfo -avot -q "savetime>=01/05/2018,savetime<=01/10/2018,client=pssql3" -r volume,name,savetime(22),totalsize(2),ssid,cloneid,ssflags

002369 MSSQL: 1/7/2018 11:58:57 PM 502 GB 3612539537 1515405258 vrEF

Then I changed the expiration date, and made it notrecyclable,

>nsrmm -S 3612539537/1515405258 -e 12/31/2025
If this saveset has dependents with longer retention periods, the dependent savesets will not be browsable after the retention pol
icy expiration date `Wed Dec 31 00:00:00 2025'.
Are you sure you want to change the retention policy expiration of this saveset to `Wed Dec 31 00:00:00 2025'? (yes/no) [no] yes

>nsrmm -S 3612539537/1515405258 -o notrecyclable
Mark save set copy 3612539537/1515405258 as not recyclable? yes

Then I found the tape with the CFI, and recovered that ...

s>nsrck -L7 -t 01/08/2018 pssql3
nsrck: checking index for 'pssql3'
9343:nsrck: The file index for client 'pssql3' will be recovered.9433:nsrck: Recovering index savesets of 'pssql3' from 'dctrman00
4.wrk.ads.pha.phila.gov'
Recover start time: 7/19/2018 12:05:55 PM
Requesting 1 recover session(s) from server.
Recover completion time: 7/19/2018 12:07:07 PM
9346:nsrck: completed recovery of index for client 'pssql3'
nsrck: D:\Program Files\Legato\nsr\index\pssql3 contains 725079 records occupying 100 MB
nsrck: Completed checking 1 client(s)


I should be good to go .... not expired, good browse time, index recovered.

>mminfo -avot -q "savetime>01/06/2018,savetime<01/08/2018,client=pssql3" -r volume,client,name,savetime(22),ssbrowse(22),ssretent(22),ssflags
volume client name date time browse time retention time ssflags

002369 pssql3 MSSQL: 1/7/2018 11:58:57 PM 12/30/2025 12:00:00 AM 7/11/2026 12:19:17 PM vF


So how come, when I go to that SQL server, and tell it I want to recover a specific instance, and I can't choose any instance prior to June 28, 2018? Why am I not seeing that Jan 7, 2018 instance?? It has a valid browse time, valid expiration time, and is not expired.

What gives? Anybody know? Luckily, we make a BAK version of all our databases, and that BAK version restored fine, using the exact same procedure as above. The only difference (that I can see) is that one is a SQL 2012 MDF file, and the other is an ASCI file.
I can't embed a screenshot to show you the error, but it occurs when I try to choose a specific instance, and browse to the date I want. It tells me that I have to choose an instance between Jun 28 and Jul 18. And I have no idea why ...

Thanks
--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
1800 South 32nd Street
Phila, PA 19145
Hours: 8AM - 4PM EST
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone@pha.phila.gov>

-- This list is hosted as a public service at Temple University by Stan Horwitz If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l..html If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu<mailto:owner-emc-dataprotection-l@listserv.temple.edu>


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
> We had something similar happen to us, and found a workaround. Hope
> it works for you.
>
> When you open Networker user for SQL, instead of using the menu to
> hit recover (I believe it is actually operation, then recover),
> click on the icon that says recover, and then popup box will then
> allow you to browse to the date you need. You can’t do it via
> change browse time.

Huh. Didn't know that existed. Thanks!

> It took us a while to find this workaround, and it was just lucky
> that we found it. Networker support had no clue.
>
> Let me know if this works for you.

Nope. When I do that, and specify Jan 7, 2018 ( I see the backup on Jan 7,
2018 11:58PM doing an mminfo), I still can't choose that date. All I see
are previous month ends (Mar 1, 2017, up until Jan 1, 2018. Won't let me
choose any date past Jan 1, 2018 (when choosing this way).



>
> David M. Browning Jr.
> IT Project Coordinator Enterprise Backups and Help Desk
> (504) 568-4364 (Direct)
> (504) 654-7520 (BlackBerry number)
> http://www.lsuhsc.edu/ithelpdesk
> Twitter: @LSUHSCNO_IT
>
>
> From: EMC Data Protection Q & A [mailto:EMC-DATAPROTECTION-
> L@LISTSERV.TEMPLE.EDU] On Behalf Of Michael Leone
> Sent: Thursday, July 19, 2018 2:29 PM
> To: EMC-DATAPROTECTION-L@LISTSERV.TEMPLE.EDU
> Subject: [EMC-DataProtection-L] Fw: Rejected posting to EMC-
> DATAPROTECTION-L@LISTSERV.TEMPLE.EDU
>
> *EXTERNAL EMAIL: EVALUATE*This is odd. I need to recover a SQL DB
> from 2018-01-07, using the Networker User for SQL Server (8.2.3.0.
> 1100) . So I found the saveset I wanted
>
> >mminfo -avot -q "savetime>=01/05/2018,savetime<=01/10/
> 2018,client=pssql3" -r volume,name,savetime(22),totalsize
> (2),ssid,cloneid,ssflags
>
> 002369 MSSQL: 1/7/2018 11:58:57 PM
> 502 GB 3612539537 1515405258 vrEF
>
> Then I changed the expiration date, and made it notrecyclable,
>
> >nsrmm -S 3612539537/1515405258 -e 12/31/2025
> If this saveset has dependents with longer retention periods, the
> dependent savesets will not be browsable after the retention pol
> icy expiration date `Wed Dec 31 00:00:00 2025'.
> Are you sure you want to change the retention policy expiration of
> this saveset to `Wed Dec 31 00:00:00 2025'? (yes/no) [no] yes
>
> >nsrmm -S 3612539537/1515405258 -o notrecyclable
> Mark save set copy 3612539537/1515405258 as not recyclable? yes
>
> Then I found the tape with the CFI, and recovered that ...
>
> s>nsrck -L7 -t 01/08/2018 pssql3
> nsrck: checking index for 'pssql3'
> 9343:nsrck: The file index for client 'pssql3' will be recovered.
> 9433:nsrck: Recovering index savesets of 'pssql3' from 'dctrman00
> 4.wrk.ads.pha.phila.gov'
> Recover start time: 7/19/2018 12:05:55 PM
> Requesting 1 recover session(s) from server.
> Recover completion time: 7/19/2018 12:07:07 PM
> 9346:nsrck: completed recovery of index for client 'pssql3'
> nsrck: D:\Program Files\Legato\nsr\index\pssql3 contains 725079
> records occupying 100 MB
> nsrck: Completed checking 1 client(s)
>
>
> I should be good to go .... not expired, good browse time, index
recovered.
>
> >mminfo -avot -q "savetime>01/06/2018,savetime<01/08/
> 2018,client=pssql3" -r volume,client,name,savetime(22),ssbrowse
> (22),ssretent(22),ssflags
> volume client name date
> time browse time retention time ssflags
>
> 002369 pssql3 MSSQL: 1/7/2018
> 11:58:57 PM 12/30/2025 12:00:00 AM 7/11/2026 12:19:17 PM vF
>
>
> So how come, when I go to that SQL server, and tell it I want to
> recover a specific instance, and I can't choose any instance prior
> to June 28, 2018? Why am I not seeing that Jan 7, 2018 instance?? It
> has a valid browse time, valid expiration time, and is not expired.
>
> What gives? Anybody know? Luckily, we make a BAK version of all our
> databases, and that BAK version restored fine, using the exact same
> procedure as above. The only difference (that I can see) is that
> one is a SQL 2012 MDF file, and the other is an ASCI file.
> I can't embed a screenshot to show you the error, but it occurs when
> I try to choose a specific instance, and browse to the date I want.
> It tells me that I have to choose an instance between Jun 28 and Jul
> 18. And I have no idea why ...
>
> Thanks
> --
> Michael Leone
> Network Administrator, ISM
> Philadelphia Housing Authority
> 1800 South 32nd Street
> Phila, PA 19145
> Hours: 8AM - 4PM EST
> Tel: 215-684-4180
> Cell: 215-252-0143
> <mailto:michael.leone@pha.phila.gov>
> -- This list is hosted as a public service at Temple University by
> Stan Horwitz If you wish to sign off this list or adjust your
> subscription settings, please do so via http://listserv.temple.edu/
> archives/emc-dataprotection-l.html If you have any questions
> regarding management of this list, please send email to owner-emc-
> dataprotection-l@listserv.temple.edu


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
was the saveset recyclable ?

if yes, have a try to run 'nsrmm -o notrecyclable -s <ssis>'

hth
Th

On 20 July 2018 16:38:17 GMT+02:00, Michael Leone <Michael.Leone@PHA.PHILA.GOV> wrote:
>> We had something similar happen to us, and found a workaround. Hope
>> it works for you.
>>
>> When you open Networker user for SQL, instead of using the menu to
>> hit recover (I believe it is actually operation, then recover),
>> click on the icon that says recover, and then popup box will then
>> allow you to browse to the date you need. You can’t do it via
>> change browse time.
>
>Huh. Didn't know that existed. Thanks!
>
>> It took us a while to find this workaround, and it was just lucky
>> that we found it. Networker support had no clue.
>>
>> Let me know if this works for you.
>
>Nope. When I do that, and specify Jan 7, 2018 ( I see the backup on Jan
>7,
>2018 11:58PM doing an mminfo), I still can't choose that date. All I
>see
>are previous month ends (Mar 1, 2017, up until Jan 1, 2018. Won't let
>me
>choose any date past Jan 1, 2018 (when choosing this way).
>
>
>
>>
>> David M. Browning Jr.
>> IT Project Coordinator Enterprise Backups and Help Desk
>> (504) 568-4364 (Direct)
>> (504) 654-7520 (BlackBerry number)
>> http://www.lsuhsc.edu/ithelpdesk
>> Twitter: @LSUHSCNO_IT
>>
>>
>> From: EMC Data Protection Q & A [mailto:EMC-DATAPROTECTION-
>> L@LISTSERV.TEMPLE.EDU] On Behalf Of Michael Leone
>> Sent: Thursday, July 19, 2018 2:29 PM
>> To: EMC-DATAPROTECTION-L@LISTSERV.TEMPLE.EDU
>> Subject: [EMC-DataProtection-L] Fw: Rejected posting to EMC-
>> DATAPROTECTION-L@LISTSERV.TEMPLE.EDU
>>
>> *EXTERNAL EMAIL: EVALUATE*This is odd. I need to recover a SQL DB
>> from 2018-01-07, using the Networker User for SQL Server (8.2.3.0.
>> 1100) . So I found the saveset I wanted
>>
>> >mminfo -avot -q "savetime>=01/05/2018,savetime<=01/10/
>> 2018,client=pssql3" -r volume,name,savetime(22),totalsize
>> (2),ssid,cloneid,ssflags
>>
>> 002369 MSSQL: 1/7/2018 11:58:57 PM
>> 502 GB 3612539537 1515405258 vrEF
>>
>> Then I changed the expiration date, and made it notrecyclable,
>>
>> >nsrmm -S 3612539537/1515405258 -e 12/31/2025
>> If this saveset has dependents with longer retention periods, the
>> dependent savesets will not be browsable after the retention pol
>> icy expiration date `Wed Dec 31 00:00:00 2025'.
>> Are you sure you want to change the retention policy expiration of
>> this saveset to `Wed Dec 31 00:00:00 2025'? (yes/no) [no] yes
>>
>> >nsrmm -S 3612539537/1515405258 -o notrecyclable
>> Mark save set copy 3612539537/1515405258 as not recyclable? yes
>>
>> Then I found the tape with the CFI, and recovered that ...
>>
>> s>nsrck -L7 -t 01/08/2018 pssql3
>> nsrck: checking index for 'pssql3'
>> 9343:nsrck: The file index for client 'pssql3' will be recovered.
>> 9433:nsrck: Recovering index savesets of 'pssql3' from 'dctrman00
>> 4.wrk.ads.pha.phila.gov'
>> Recover start time: 7/19/2018 12:05:55 PM
>> Requesting 1 recover session(s) from server.
>> Recover completion time: 7/19/2018 12:07:07 PM
>> 9346:nsrck: completed recovery of index for client 'pssql3'
>> nsrck: D:\Program Files\Legato\nsr\index\pssql3 contains 725079
>> records occupying 100 MB
>> nsrck: Completed checking 1 client(s)
>>
>>
>> I should be good to go .... not expired, good browse time, index
>recovered.
>>
>> >mminfo -avot -q "savetime>01/06/2018,savetime<01/08/
>> 2018,client=pssql3" -r volume,client,name,savetime(22),ssbrowse
>> (22),ssretent(22),ssflags
>> volume client name date
>> time browse time retention time ssflags
>>
>> 002369 pssql3 MSSQL: 1/7/2018
>> 11:58:57 PM 12/30/2025 12:00:00 AM 7/11/2026 12:19:17 PM vF
>>
>>
>> So how come, when I go to that SQL server, and tell it I want to
>> recover a specific instance, and I can't choose any instance prior
>> to June 28, 2018? Why am I not seeing that Jan 7, 2018 instance?? It
>> has a valid browse time, valid expiration time, and is not expired.
>>
>> What gives? Anybody know? Luckily, we make a BAK version of all our
>> databases, and that BAK version restored fine, using the exact same
>> procedure as above. The only difference (that I can see) is that
>> one is a SQL 2012 MDF file, and the other is an ASCI file.
>> I can't embed a screenshot to show you the error, but it occurs when
>> I try to choose a specific instance, and browse to the date I want.
>> It tells me that I have to choose an instance between Jun 28 and Jul
>> 18. And I have no idea why ...
>>
>> Thanks
>> --
>> Michael Leone
>> Network Administrator, ISM
>> Philadelphia Housing Authority
>> 1800 South 32nd Street
>> Phila, PA 19145
>> Hours: 8AM - 4PM EST
>> Tel: 215-684-4180
>> Cell: 215-252-0143
>> <mailto:michael.leone@pha.phila.gov>
>> -- This list is hosted as a public service at Temple University by
>> Stan Horwitz If you wish to sign off this list or adjust your
>> subscription settings, please do so via http://listserv.temple.edu/
>> archives/emc-dataprotection-l.html If you have any questions
>> regarding management of this list, please send email to owner-emc-
>> dataprotection-l@listserv.temple.edu
>
>
>--
>This list is hosted as a public service at Temple University by Stan
>Horwitz
>If you wish to sign off this list or adjust your subscription settings,
>please do so via
>http://listserv.temple.edu/archives/emc-dataprotection-l.html
>If you have any questions regarding management of this list, please
>send email to owner-emc-dataprotection-l@listserv.temple.edu

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
> was the saveset recyclable ?
>
> if yes, have a try to run 'nsrmm -o notrecyclable -s <ssis>'

ssflags were vrEF. But yes, hat was part of what I did, yes. Didn't help.


And it's certainly not recyclable now; it shows just "vF" as ssflags.


>
> hth
> Th

> On 20 July 2018 16:38:17 GMT+02:00, Michael Leone
> <Michael.Leone@PHA.PHILA.GOV> wrote:
> > We had something similar happen to us, and found a workaround. Hope
> > it works for you.
> >
> > When you open Networker user for SQL, instead of using the menu to
> > hit recover (I believe it is actually operation, then recover),
> > click on the icon that says recover, and then popup box will then
> > allow you to browse to the date you need. You can’t do it via
> > change browse time.
>
> Huh. Didn't know that existed. Thanks!
>
> > It took us a while to find this workaround, and it was just lucky
> > that we found it. Networker support had no clue.
> >
> > Let me know if this works for you.
>
> Nope. When I do that, and specify Jan 7, 2018 ( I see the backup on
> Jan 7, 2018 11:58PM doing an mminfo), I still can't choose that
> date. All I see are previous month ends (Mar 1, 2017, up until Jan
> 1, 2018. Won't let me choose any date past Jan 1, 2018 (when
> choosing this way).
>
>
>
> >
> > David M. Browning Jr.
> > IT Project Coordinator Enterprise Backups and Help Desk
> > (504) 568-4364 (Direct)
> > (504) 654-7520 (BlackBerry number)
> > http://www.lsuhsc.edu/ithelpdesk
> > Twitter: @LSUHSCNO_IT
> >
> >
> > From: EMC Data Protection Q & A [mailto:EMC-DATAPROTECTION-
> > L@LISTSERV.TEMPLE.EDU] On Behalf Of Michael Leone
> > Sent: Thursday, July 19, 2018 2:29 PM
> > To: EMC-DATAPROTECTION-L@LISTSERV.TEMPLE.EDU
> > Subject: [EMC-DataProtection-L] Fw: Rejected posting to EMC-
> > DATAPROTECTION-L@LISTSERV.TEMPLE.EDU
> >
> > *EXTERNAL EMAIL: EVALUATE*This is odd. I need to recover a SQL DB
> > from 2018-01-07, using the Networker User for SQL Server (8.2.3.0.
> > 1100) . So I found the saveset I wanted
> >
> > >mminfo -avot -q "savetime>=01/05/2018,savetime<=01/10/
> > 2018,client=pssql3" -r volume,name,savetime(22),totalsize
> > (2),ssid,cloneid,ssflags
> >
> > 002369 MSSQL: 1/7/2018 11:58:57 PM
> > 502 GB 3612539537 1515405258 vrEF
> >
> > Then I changed the expiration date, and made it notrecyclable,
> >
> > >nsrmm -S 3612539537/1515405258 -e 12/31/2025
> > If this saveset has dependents with longer retention periods, the
> > dependent savesets will not be browsable after the retention pol
> > icy expiration date `Wed Dec 31 00:00:00 2025'.
> > Are you sure you want to change the retention policy expiration of
> > this saveset to `Wed Dec 31 00:00:00 2025'? (yes/no) [no] yes
> >
> > >nsrmm -S 3612539537/1515405258 -o notrecyclable
> > Mark save set copy 3612539537/1515405258 as not recyclable? yes
> >
> > Then I found the tape with the CFI, and recovered that ...
> >
> > s>nsrck -L7 -t 01/08/2018 pssql3
> > nsrck: checking index for 'pssql3'
> > 9343:nsrck: The file index for client 'pssql3' will be recovered.
> > 9433:nsrck: Recovering index savesets of 'pssql3' from 'dctrman00
> > 4.wrk.ads.pha.phila.gov'
> > Recover start time: 7/19/2018 12:05:55 PM
> > Requesting 1 recover session(s) from server.
> > Recover completion time: 7/19/2018 12:07:07 PM
> > 9346:nsrck: completed recovery of index for client 'pssql3'
> > nsrck: D:\Program Files\Legato\nsr\index\pssql3 contains 725079
> > records occupying 100 MB
> > nsrck: Completed checking 1 client(s)
> >
> >
> > I should be good to go .... not expired, good browse time, index
recovered.
> >
> > >mminfo -avot -q "savetime>01/06/2018,savetime<01/08/
> > 2018,client=pssql3" -r volume,client,name,savetime(22),ssbrowse
> > (22),ssretent(22),ssflags
> > volume client name date
> > time browse time retention time ssflags
> >
> > 002369 pssql3 MSSQL: 1/7/2018
> > 11:58:57 PM 12/30/2025 12:00:00 AM 7/11/2026 12:19:17 PM vF
> >
> >
> > So how come, when I go to that SQL server, and tell it I want to
> > recover a specific instance, and I can't choose any instance prior
> > to June 28, 2018? Why am I not seeing that Jan 7, 2018 instance?? It
> > has a valid browse time, valid expiration time, and is not expired.
> >
> > What gives? Anybody know? Luckily, we make a BAK version of all our
> > databases, and that BAK version restored fine, using the exact same
> > procedure as above. The only difference (that I can see) is that
> > one is a SQL 2012 MDF file, and the other is an ASCI file.
> > I can't embed a screenshot to show you the error, but it occurs when
> > I try to choose a specific instance, and browse to the date I want.
> > It tells me that I have to choose an instance between Jun 28 and Jul
> > 18. And I have no idea why ...
> >
> > Thanks
> > --
> > Michael Leone
> > Network Administrator, ISM
> > Philadelphia Housing Authority
> > 1800 South 32nd Street
> > Phila, PA 19145
> > Hours: 8AM - 4PM EST
> > Tel: 215-684-4180
> > Cell: 215-252-0143
> > <mailto:michael.leone@pha.phila.gov>
> > -- This list is hosted as a public service at Temple University by
> > Stan Horwitz If you wish to sign off this list or adjust your
> > subscription settings, please do so via http://listserv.temple.edu/
> > archives/emc-dataprotection-l.html If you have any questions
> > regarding management of this list, please send email to owner-emc-
> > dataprotection-l@listserv.temple.edu
> -- This list is hosted as a public service at Temple University by
> Stan Horwitz If you wish to sign off this list or adjust your
> subscription settings, please do so via http://listserv.temple.edu/
> archives/emc-dataprotection-l.html If you have any questions
> regarding management of this list, please send email to owner-emc-
> dataprotection-l@listserv.temple.edu
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.


--
This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
Sorry, only registered users may post in this forum.

Click here to login